Skip to content
Create Ticket
  • There are no suggestions because the search field is empty.

legacyExchangeDN and other mail attributes - Implicit writes

What attributes does PowerSyncPro process by default when Mail-Enable is selected?

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 those attributes are not present on the source object, PowerSyncPro will build them and set the appropriate target attributes — for example, mapping 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

How do you maintain replyability and calendaring during a mailbox migration?

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]

How do attribute mappings interact with default processing?

Attribute mappings defined in the mapping configuration are always processed and take precedence over default processing. For example, a mapping from sAMAccountName to mailNickName, or a complex expression targeting mail, proxyAddresses, or msExch* attributes, will override the default values.

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.