3rd party Archiving

The “3rd party Archiving” feature offers the possibility for our customers to use the Archiving solution of their choice for keeping legal long-term evidence that an email has been sent using the Transactional Email service.

From a technical point of view, it consists in adding a default Bcc: recipient at the EnvelopeTo level for each request processed through a specific account. Therefore, the configured email address can be used to route email into the 3rd party Archiving solution accordingly.

How to use it this Feature?

During the Onboarding phase, or during the Run phase, ask the Implementation Team to configure the “3rd party Archiving” feature:

• Account configuration:

  • Specify on which account you want to configure this feature.

  • Provide at least one valid email address that will be used as a default Bcc: recipient.

• REST APIs:

  • The feature is triggered by default for all JobRequest using a defined account with this feature enabled. There is no parameter to control this at the JobRequest level. If no default Bcc: addresses should be added, another account must be used for which this feature is not configured.

• SMTP Adapter:

  • Some SMTP applications do not offer the possibility to configure any Bcc: email address at the EnvelopeTo level when sending emails out.

  • Therefore, Transactional Email offers the possibility to mitigate such situation by declaring a default Bcc: email address for all JobRequest sent via the configured account.

  • The feature is triggered by default for all JobRequest using a defined account with this feature enabled. There is no parameter to control this at the JobRequest level. If no default Bcc: addresses should be added, another account must be used for which this feature is not configured.

• 3^rd party Archiving solution:

  • This solution must be able to receive SMTP connections from the Internet.

  • The domain name used for the default Bcc: address(es) must have a valid MX Record and verified SPF and DKIM entries into the related DNS zone.

  • For each email sent using Transactional Email with the “3rd party Archiving” feature enabled, one email will be sent to the default Bcc: email address(es).

  • Retarus does not recommend a specific Archiving solution editor for the moment.

Notes

• Retarus Transactional Email does not offer for the moment a built-in storage for long-term legal retention. Transactional Email still does not offer the possibility to read and export full email content from the myEAS Live Search interface.

• For being able to store and resend jobs during 45 days, please read the section Trace & Recover (SMTP only).

• The configured Bcc: addresses are not subject to the restrictions of allowedRecipientDomains and forbiddenReceiverLocalParts. Thus, to avoid misconfiguration and therefore missing to store legal evidence of an email that have been sent out.

• Up to 10 different Bcc: email addresses can be configured.

• Using this feature results in adding at least +1 recipient to every JobRequest processed by Transactional Email:

  • These additional default Bcc: recipients (up to 10) will be counted and automatically charged according to your pricing plan.

  • The overall limitation of 1000 recipients per JobRequest for the REST interface is still applicable when using the “3rd party Archiving” feature.

• In the myEAS Live Search, myEAS Report or Push Notifications, the default Bcc: recipient is considered as a separate recipient.

• The default Bcc: email address is configured at the Account L2 level (see Service administration hierarchy).