This was an issue back with WSP 2.1, where the contact was <GUID>@domain.com. And a lot of people complained about it so it was changed so that the username of the email@example.com was used and then added as a local domain primarySMTPAddress. We ran into a several cases where this caused mail to be forwarded to the contact when the recipient address was the contact. In a few cases this was when an employee had left the company but a contact was created for the user. The new mail contact was the recipient of any mail that had come into the old address.
firstname.lastname@example.org leaves the company
email@example.com is created as a contact.
PrimarySMTPaddress of the contact is created as firstname.lastname@example.org with external address of email@example.com
Mail received for firstname.lastname@example.org now is delivered to the previous employees external address.
Would it be possible to have that primarySMTPAddress be created as something identifiable that should not cause mail routing issues? It appears that if that address already exists that it increments it as a email@example.com
No, because it looks like if the address already exists that the primarySMTPAddress of the contact is automatically incremented so at least in my testing there are no collisions. So if firstname.lastname@example.org already existed the contact for email@example.com would have a primarySMTPAddress of firstname.lastname@example.org. This is sort of a workaround to the problem in that if the contact address would cause a problem creating two contacts and deleting the first would solve the mail routing issue.
But where the issue really lay is that it can cause inadvertent forwarding of messages to contacts, because they are effectively recipient domain members. Even having the forest domain as the primarySMTPAddress should, at least in theory, be a valid solution.
email@example.com is created as a contact. If his primarySMTPaddress were created as the forest domain (in this example hosting.local). So his primarySMTPAddress were created as firstname.lastname@example.org. Would solve the problem because we are only trying to resolve this primarySMTPaddress from the local forest.
- Views5120 times
- Answers7 answers