legacyExchangeDN and other mail attributes - implicit writes
Written by Neil Langston
Updated at May 22nd, 2025
Table of Contents
Default processing
PSP will always process the following attributes when Mail-Enable is selected.
- mail
- mailNickname
- proxyAddresses
- groupType
- reportToOrignator
If those attributes are present on the source object, they will be written to target. The legacyExchangeDN is written to the proxyAddresses attribute as an x500 address.
If they are not present, PSP will build them and set the appropriate target attributes i.e.
sAMAccountName to mailNickName
NOTE: If the mail attribute is not present on the source object, then no mail attribute will be written to the target. This is by design.
Maintain replyability and calendaring
When migrating mailbox data as part of your project you will need to write the Source legacyExchangeDN as an x500 address in the proxyAddresses attribute in the target directory to maintain replyability and calendaring.
legacyExchangeDN is written implicitly by PowerSyncPro Directory Synchronisation as part of default processing when Mail-Enable is selected.
The following attributes are written for mail-enabled users if the target schema is extended for Microsoft Exchange
- legacyExchangeDN This is created as a GUID + sAMAccountName
- msExchRecipientDisplayType set as required for User/Group/Contact
- msExchRecipientTypeDetails set as required for User/Group/Contact
- showInAddressBook set per target if present in the Address Lists Container in the Configuration\Services\Microsoft Exchange\[org]
Attribute Mappings
If there are attribute mappings present in the mapping’s configuration, they will always be processed.
Mappings supersede Default processing. e.g. there is a mapping like sAMAccountName to mailNickName or a complex expression to set mail, proxyAddresses or msExch* attributes - then those mappings will take precedence.
NOTE:
msExchVersion is NOT written by default
If you have a reason to set this then please create a mapping and if necessary, use a Simple Expression to hard code a value.
msExchRemoteRecipientType is not written by default.
If you have a need to set this to control the mailbox in Microsoft 365/EXO, then use Complex Expressions to get / set msExchRecipientDisplayType, msExchRecipientTypeDetails and msRemoteRecipientType as desired.