andyfitz
asked on
MS Exchange error 5.1.4
I want to have two contact records in my Active Directory to have the same SMTP email addresses. I can set them up and use the Global Address List in Outlook to select either of the entries and all works well. But when I type in the raw email address I get the 5.1.4 error (Exchange can't resolve the display name of the address)
OK, I understand how the problem can originate but it seems to me that there must be a way around it.
For example:
I have two contact records in my Active Directory at xyz.com. They share a common SMTP address to an account (say: acct@AOL.COM). These two people appear in my organizations Global Address Book as contacts and when I select one or the other the email gets sent with no problem. But when I type in acct@AOL.COM in the To: message area, Exchange returns this 5.1.4 message and doesn't send the message.
How can I tell exchange to ignore the ambiguity and send it anyway?
OK, I understand how the problem can originate but it seems to me that there must be a way around it.
For example:
I have two contact records in my Active Directory at xyz.com. They share a common SMTP address to an account (say: acct@AOL.COM). These two people appear in my organizations Global Address Book as contacts and when I select one or the other the email gets sent with no problem. But when I type in acct@AOL.COM in the To: message area, Exchange returns this 5.1.4 message and doesn't send the message.
How can I tell exchange to ignore the ambiguity and send it anyway?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Makes sense for Users but not for Contacts.
In Outlook I can set up several contacts with the same email address and all is well. What is the problem with Exchange Contacts? In Active Directory a Contact entry does not give the person logon authority (there is no sAMaccount name and no Exchange mailbox); it should be just an informational entry. If Exchange can't resolve an email address because there are two of them in AD - so what? The entry should validate as at least being known to the organization. It would just use the typed in address instead of a display name - that is what happens when you type in an email address that is not in AD.
In Outlook I can set up several contacts with the same email address and all is well. What is the problem with Exchange Contacts? In Active Directory a Contact entry does not give the person logon authority (there is no sAMaccount name and no Exchange mailbox); it should be just an informational entry. If Exchange can't resolve an email address because there are two of them in AD - so what? The entry should validate as at least being known to the organization. It would just use the typed in address instead of a display name - that is what happens when you type in an email address that is not in AD.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
no good.
AD Contact records do not have delivery options. The Contact names we are adding are not members of our domain and therefore we do not want to add them as User accounts - just have them appear in our Global Address List.
This is getting to sound more and more like a bad design feature of Exchange - or are we so unique that no one has ever run into this before?
AD Contact records do not have delivery options. The Contact names we are adding are not members of our domain and therefore we do not want to add them as User accounts - just have them appear in our Global Address List.
This is getting to sound more and more like a bad design feature of Exchange - or are we so unique that no one has ever run into this before?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
"if you think about it though, in all of the internet there is no two people that have the same email address, which is probably why exchange doesn't allow it either" - Huh? My wife and I share an email address.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The real issue here is for OUTGOING email. That is why these people are set up as Contacts. They do not have an email address within my organization and we don't want to give them one. They are added to our AD with their outside email address as a convenience to other members of my organization.
I can't set them up with different email addresses because they don't have different email addresses. A distribution list would be a way to solve the problem if they had separate addresses.
I am pretty frustrated by what to me should be a simple situation. For OUTGOING email just send the email. If it can't resolve a mailbox for incoming email that is a different issue.
I can't set them up with different email addresses because they don't have different email addresses. A distribution list would be a way to solve the problem if they had separate addresses.
I am pretty frustrated by what to me should be a simple situation. For OUTGOING email just send the email. If it can't resolve a mailbox for incoming email that is a different issue.
ASKER
for example:
Mary Smith = jones@aol.com
John Jones = jones@aol.com
I want both Mary and John to show up in my Global Address List for those who have access to our Exchange server so they can be selected by their individual name by a user who may know them.
I want another user who may not have access to the Global Address List but uses a pop account to our server to be able to type in jones@aol.com and have it sent without a 5.1.4 error.