Authenticate a domain and declare senders
01Add a sending domain #sec_87eb9c9f
Open Settings > Communication > Sending domains, then click Add a domain.
The first screen asks for the domain name and the sending configuration that must authenticate it. A provider can manage multiple domains: the name possibly present in its technical identifiers is not a limit. Here you associate the new domain with an existing active configuration.
The current route is preselected. You can choose another one when several active configurations are available.
02Publish DNS records #sec_ce476628
The second screen presents the records requested by the provider. For each line, an icon allows to copy separately the host and the value.
Publish these records in the service that hosts the domain's DNS zone. This is not necessarily the email provider: it can be OVHcloud, Squarespace, Cloudflare or an internal DNS service.
The records fulfill different roles:
| Type | Role |
|---|---|
| SPF | Authorizes the authorized infrastructures to send for the domain |
| DKIM | Allows the recipient to verify the signature of the message |
| DMARC | Defines the domain's control and reporting policy |
| CNAME | Delegates an authentication or tracking function to the provider |
Do not create two competing SPF records. If the domain already has an SPF, merge the authorized mechanisms into a single value. Also keep the MXs that ensure mail reception, unless explicitly and validated instructed by the team that administers the mail.
03Check after propagation #sec_84f97ae3
DNS propagation can take time. You can close the panel: the pending domain remains visible in the list.
Then return to the Check action. The Subscription Manager checks each value and displays its status. The button should not immobilize the interface indefinitely: if the provider has not yet confirmed the delegation, the panel returns control and invites you to try again later.
When all values are recognized, the domain becomes Verified. It remains voluntarily inactive until you activate it from the list. Technical proof and authorization to use are two distinct decisions.
04Understand delegation #sec_41f50126
The Delegation column summarizes the scope of what is entrusted to REVIEWIT. Its tooltip gives the details:
- Client DNS: the zone remains fully administered by the organization;
- Service domain: a technical identity provided for sending is used;
- Domain and provider: the domain and the delivery account belong to the client.
These labels describe the responsibility; they do not change the owner of the asset.
05Declare a sender #sec_f014bb37
Open Settings > Communication > Senders, then add an identity.
Enter a visible name and the complete address built on a verified domain. A different reply address is optional; when used, REVIEWIT may request its confirmation before directing replies to it.
The list aggregates the name and address in a single Sender column and indicates the associated delivery configuration. Senders linked to inactive configurations are not offered as operational choices.
06Choose the default sender #sec_9f14e63c
Use the icon action on the desired address. If it depends on another active configuration than the current route, the Subscription Manager explains it and asks you to confirm the simultaneous switch of the default provider.
This rule prevents a sender from being presented as a reference while its delivery route is not the one used. An inactive configuration cannot be indirectly activated by this gesture.
07Quick Check #sec_03a96d90
Before moving to the catalog, verify that :
- the domain appears as verified and active;
- the sender uses this domain;
- its sending configuration is active;
- the sender and the default route are consistent;
- the action tooltips confirm the action before clicking.
You can now [test, publish and exploit communications](tuto-communication-factory-catalogue-exploitation).