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 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.
![2024-06-27 15_11_46-PowerPoint Slide Show - DRAFT Review_Graphics_3PartyArchive.pptx.png](../__attachments/97124354/2024-06-27%2015_11_46-PowerPoint%20Slide%20Show%20%20-%20%20DRAFT%20Review_Graphics_3PartyArchive.pptx.png?inst-v=318867b3-0306-493e-8e28-129836f54d5d)
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;
3rd 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 send to the default Bcc: email address(es).
Notes:
Retarus Transactional Email does not offer for the moment a built-in storage for long term legal retention. 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 be 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 the Service administration hierarchy page).