Skip to main content
Skip table of contents

Special considerations

This section discusses special cases where synchronization behaves differently to avoid performance problems or to accommodate protocol limitations by Microsoft. 

Unsafe attachments

Attachments with any of the following file extensions are considered to be unsafe and will not be synchronized.

The unsafe attachments have the following file extensions:

  • .bas
  • .bin
  • .com
  • .cmd
  • .crt
  • .csh
  • .dll
  • .exe
  • .hlp
  • .hta
  • .htm
  • .html
  • .ins
  • .isp
  • .js
  • .mdb
  • .mht
  • .mhtml
  • .nws
  • .sct
  • .sh
  • .stm
  • .vps
  • .wsc
  • .xht
  • .xhtml

Attachment synchronization

NexJ CRM will not pick up any "in-place" changes (i.e., updates to an attachment's content in Exchange) made to already synchronized attachments from the mailbox of the synchronized user. For a non-recurring item, if any of the attachments on the item exceeds the maximum file attachment size, none of the attachments on the item will be synchronized. If the total size of all the attachments exceeds the maximum attachment size, none of the attachments will be synchronized.

For a recurring item, if any of the attachments or the total of all attachments on a customized occurrence or the series exceeds the maximum file attachment size, none of the attachments on that particular occurrence or series will be synchronized. This is not to say that other occurrences belonging to the same series with attachments will not be synchronized due to an offending occurrence or series. As long as the maximum file attachment size is not exceeded for the other occurrences or the series, the attachments on them will be synchronized.

Contact picture synchronization

The profile picture of contacts in NexJ CRM will not be synchronized to Exchange. The Exchange Web Services protocol as provided by Microsoft does not allow such an operation.

Delegate Access mode

When synchronization is configured using Delegate Access mode instead of Impersonation mode, NexJ CRM cannot directly synchronize meeting creations to slave mailboxes. A mailbox is considered a slave if the mailbox owner is a meeting participant other than the meeting owner. Meeting notifications can still be used to synchronize the meeting to such participants.


The delegate user, who is responsible for maintaining records on behalf of other users, must have access to the private items of each user's mailbox to prevent the creation of duplicate records.

Onboarding users through LDAP

When onboarding users, if a user's email is passed through LDAP but is not in Active Directory, then the user will be added without the email address.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.