Hello,

When using the AD synchronisation to import users from AD, it will also add the additional email addresses for that account from Exchange to the Xeams user associations - which is awesome!

HOWEVER, that user is then represented in all other aspects of Xeams by the alphabetical first entry in the association list for that user. It will not carry over the Exchange primary address - which is often the easiest way to match the email to the user.

ie. 

      User Account Name        -    Jason
      Primary Email Address    -    Jason@domain.local
      Other Email Address       -    backups@domain.local
      Other Email Address       -    security@domain.local 

Xeams will identify the AD user Jason in the message repository via the email address backups@domain.local.

Is there a way this can be synchronised from Exchange or updated locally to elect the 'primary association address' for the Ad user?


Thanks in advance!
Jason

Jason,

I am not sure if I understand your request completely. Xeams will send emails to ANY of the associated addresses. The assumption is that all of these addresses will eventually end up in the same INBOX on the Exchange's end. Therefore, it does not matter if the message is sent to jason, backups or security.

Are you saying that a message sent from Xeams to Exchange should always go to jason@domain.local ?

Sorry, I wasn't overly clear with my query :)

You are 100% correct with your statements. I was looking to allow Xeams to identify the primary exchange address - or allow the Xeams admin to select the "association email address" to identify the user in reports so that it becomes clearer who is who.

ie.

Using the example above the user reports will contain:

Jason@domain.local
Chris@domain.local
Peter@domain.local 

instead of

backups@domain.local
accounts@domain.local
ebay_admin@domain.local

Does this clarify my question?

My next question would then be, can a report be created to indicate the volume of emails processed to each individual association address? For example to assist with identifying which email addresses may have been compromised for spam?

Kind regards
Jason