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 firstname.lastname@example.org 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.
email@example.com leaves the company
firstname.lastname@example.org is created as a contact.
PrimarySMTPaddress of the contact is created as email@example.com with external address of firstname.lastname@example.org
Mail received for email@example.com 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 firstname.lastname@example.org
Well the last suggestion doesn’t quite work as advertised. I downloaded the source and tried it out. And writing the contact primarySMTPaddress as a domain.local. While in theory works. The recipient of the message gets the email@example.com as the mailto.
15.00.1178.000; Mon, 8 Aug 2016 17:07:47 -0500
From: Jeremy McNab <firstname.lastname@example.org>
To: Jeremy McNab <email@example.com>
back to the drawing board….
- Views5341 times
- Answers7 answers