Functional scope
Learn about the functional scope - – details, limitations and restrictions.
The following functionality is available:
E-mail synchronization – functional details
| Functionality | Gmail | Open-Xchange | Zarafa | Zimbra |
|---|---|---|---|---|
| Automatic creation of synchronization folder Note: The synchronization folder has to be
a direct child of the <inbox> and therefore only the format /<inbox>/sync_folder_name
is accepted. In case of Gmail there are no folders, but labels.
|
YES | YES | YES | YES |
| Option: Synchronize e-mails received in BCC | YES | YES | YES | YES |
| Option: Synchronize / do not synchronize attachments | YES | YES | YES | YES |
| Option: do not synchronize attachments larger than n KB | YES | YES | YES | YES |
| Option: Store whole message as single document in Aurea.CRM. Note: Generic connector can save a representation of the original e-mail as an EML document
in Aurea.CRM.
|
YES | YES | YES | YES |
| Option: Move successfully synchronized e-mails to Sub-Folder "Success". Note: In case of Gmail there are no folders, but labels.
|
YES | YES | YES | YES |
| Option: Move unsuccessfully synchronized e-mails to Sub-Folder "Failure". Note: In case of Gmail there are no folders, but labels.
|
YES | YES | YES | YES |
| Option: send synchronization failure message to the user. Note: Sending e-mails is done via SMTP, therefore this feature requires that SMTP is
enabled on the messaging system
|
YES | YES | YES | YES |
| Two-legged authentication. | YES | YES | YES | YES |
General features
| General features | Supported |
|---|---|
| Inform and stop on error | YES, see Error Handling. |
| Writing performance data to performance counters | YES, see Writing performance data to performance counters. |
| Server-side installation | YES, no client-side installation required |
| Filtering list of synchronization users. It is possible to define additional criteria on the ID table in order to filter the list of users, which are synchronized by connector, see the WIKI article How connector(s) determine which users to synchronize. |
YES, see the WIKI article How connector(s) determine which users to synchronize. |