Syncs to Exchange 2007 (or newer) set invalid value for mailnickname (alias)

Created: 2012-04-20 08:09:59
Modified: 2017-05-08 20:14:45
Tags: Active Directory Exchange 20xx Troubleshooting UnitySync

In previous versions of our software, connections syncing to an Active Directory (AD) Destination used a default mailNickname mapping, as below:


This mapping uses the Source email address value to set the mailNickname attribute of each contact created on the destination. As of Exchange 2007, the ampersand @ character is no longer allowed in the mailNickname attribute. Previously synced contacts may contain this ‘invalid’ character, since all synced contacts contain an email address in the mail value.

All versions of UnitySync have a modified mailNickname mapping that uses ~smtpname~.~smtphost~ instead of ~mail~. The mapping ~smtpname~.~smtphost~ is essentially the same value as mail, except uses a period instead of an ampersand.

If you are using custom object maps that were built in pre-Exchange 2007 and are having issues with mailNickname now, this may be the culprit.

This problem is easily remedied with a custom mapping to assign a new mailNickname mapping.


Edit your existing custom map file and modify the mailNickname mapping to read as follows:

mailnickname#64= ~smtpname~.~smtphost~

On your next sync run, the change will trigger a modification to all synced objects, changing the mailNickname to the new value.

Share this article:

  1. Directify - Self Service

  2. Mimic - Replication

  3. UnitySync - Sync
  1. emPass - Sync
  1. Profiler
  2. SimpleSync