Advanced Features

CollectedMailboxes.xml

By default connector SE gets the list of users – whose mailboxes are supposed to be synchronized from Aurea CRM (see Creating User Settings in Aurea CRM for further details).

Furthermore connector supports additional filtering of the user list via an XML file (See CollectedMailboxes.xml below). If such a file exists in the installation directory the list of users (mailboxes) is restricted to the users, which are both activated in Aurea CRM via their ID table settings and their e-mail addresses are included in the file.

Note: See the WIKI article How connector(s) determine which users to synchronize for further details.

This mechanism might be quite helpful for testing purposes, because it allows for limiting the number of synchronization users without any need to change the settings in Aurea CRM.

The structure of the CollectedMailboxes.xml is simple, connector SE solely requires is the SMTP address of the mailboxes.

<?xml version="1.0"?>
<Mailboxes>
 <Mailbox Smtp="fred.tester@exlab02.local" />
 <Mailbox Smtp="john.productowner@exlab02.local" />
</Mailboxes>

Example: CollectedMailboxes.xml

Note: connector SE does not provide any means for creating such a CollectedMailboxes.xml file, since EWS does not allow for generating a list of all mailboxes available.

Connector SE "understands" the format of CollectedMailboxes.xml file created with (update.seven) connector for Exchange, too.

This option disables the Automatically update list of mailboxes to synchronize n time(s) a day setting of the connector configuration.

Information and stop on Errors

Note: This feature is deprecated – please use the Error Handling Features instead (see Error Handling for further details).

Sending warning and error messages to users

Connector stores the reason of the last failure on the message or appointment level (mmSyncStatus property) respectively, so that only one message per item is sent unless the reason for an error changes. In other words: in case that the reason for a failure matches the one stored in the mmSyncStatus property, no additional message is sent to the user. Restarting the connector does not change this behavior.

There is one exception from the above rule: if connector fails while reading/decoding a message, this usually means that the connection with Exchange Server was lost/failed. In this case it is not possible to save any changes to the message (cannot store the reason on mmSyncStatus) and it can happen that connector sends multiple error messages to the user, but connector holds this information in memory and not send the error message as long the item stays unchanged and connector is not restarted.

These options are intended to give feedback to the users in case that during the synchronization of items either not the full information could be synchronized (e.g. if an attachment exceeded the configured size limit) or an error occurred (e.g. that due to fact, that the message could not be assigned properly in the CRM system).

Although connector typically – see details above - doesn’t send multiple error / warning messages for the same item, in case of a systematic problem enabling this option could result in lots of messages to the dedicated users.

E.g. if the e-mail address of the synchronizing user is not unique in the CRM system, such an error message would be sent over and over (for every new item), unless this problem is corrected.