Trusted Domains

Feature overview

The Trusted Domains feature supports you into defining a list of recipient domains for which Transactional Email is allowed to deliver messages. If messages are accidentally sent to a domain not part of that list, they will be dropped. This feature is particularly useful in case you want to make sure:

• a critical source Application does not send sensitive information to unintended audience;

• your UAT (User Acceptance Test) environment does not send messages to production recipients during your tests.

Requirements

• Feature configured for at least one Technical Account;

• Up to 50 recipient domains can be defined per sender domain;

• No email address(es) can be set.

How to set up and use this feature?

This feature is configured at the Technical Account L2-level, and can’t be controlled at the JobRequest level (REST API or SMTP Adapter). To set up the Trusted Domains feature, open a Service Request and provide the following information:

• Name of the Technical Account you want to configure this feature;

• Provide at least one valid domain name as a Trusted Domain;

• This feature is optional, you can ask to disabled it later, then all messages will be allowed.

The behaviour is the following, if a JobRequest:

• submits a message to the configured Technical Account;

• and explicitly requesting to deliver a message to a domain not listed into the Trusted Domains list;

Then the JobRequest will be accepted at the entry facade, but will be dropped during processing and therefore will never be sent out.

Domain names listed into the Trusted Domains list are still subject to the Suppression List mechanism.

Tracking Points

Live Search

Messages sent to Domains not listed into the Trusted Domains list will be DROPPED during the PRE_PROCESSING phase with a FINISHED state and SUPPRESSED sub-type.