Written by 4SYSTEMPublished on Updated on

Email and CRM · 7 min reading

SPF, DKIM and DMARC are complementary: SPF checks if a server is authorized to send for a domain, DKIM allows you to check a signature of the message, and DMARC links these checks to the visible domain of the sender. For a small business, the priority is to inventory all the tools that send emails, then verify their authentication before tightening the rules.

Key points

Start with the services that actually send

Identify employee messaging, newsletters, order confirmations, invoicing and site notifications. For each service, note the domain visible in the "From" field, its manager, and the provider's authentication instructions. An old tool can continue to send even if it no longer appears in your usual campaigns.

Then find out who manages the DNS zone, that is to say the technical records of your domain. This person is not necessarily the one who administers your site. Request a copy of existing records before any changes, as well as a rollback procedure. Do not email passwords to prepare this inventory.

Understand SPF, DKIM and DMARC without confusing them

SPF: allow sending servers

SPF relies on a DNS record that indicates which servers are allowed to send for the controlled domain. In the current case, this domain is that of the sender of the technical envelope, associated with the Return-Path, not necessarily the one displayed in “From”. The SPF documentation of Google describes permissions; his documentation DMARC explains this distinction between domains.

For the same controlled domain name, you need a single SPF record grouping the necessary authorizations, not a competing record per provider. Don't merge values ​​randomly: services can use different wrapping domains. Have the responsible person check the syntax and dependencies. Adding many suppliers may also encounter the limit of DNS consultations authorized by SPF; Have nested inclusions checked, not just text length.

DKIM: check the message signature

The sending service signs the message with a private key. The receiving server verifies this signature with a public key accessible in the DNS. This allows you to control the signed parts of the message and the signing domain. DKIM does not encrypt content and does not prove that the request contained in the email is honest.

The DKIM documentation of Google details keys and verification. Multiple providers may use different selectors, which identify their keys. Follow the names and values ​​provided by each tool. The DNS publication is not always enough: the activation of the signature on the sender side must also be checked.

DMARC: check alignment and define policy

DMARC uses the visible domain in "From". To succeed, you need at least one successful and aligned check: SPF with its envelope domain, or DKIM with its signatory domain. The alignment can be strict, with identical domains, or loose, with the same organizational domain, for example your domain and a subdomain, depending on the settings. The official documentation DMARC outlines these terms and available policies.

  • p=none does not require special treatment under DMARC; it is used in particular to observe with configured reports.
  • p=quarantine requires treating failures as suspicious, for example spam.
  • p=reject asks to reject failed messages.

The recipient server maintains its own filtering rules. “None” therefore does not mean that all messages will arrive in the inbox.

Illustrative example: one domain and several tools

This example is fictitious and does not provide any configuration to copy. A store uses professional messaging, a newsletter tool and an order confirmation service. All display its domain in “From”.

Mail messages pass DMARC with an aligned DKIM signature. The newsletter passes SPF, but only for the technical area of ​​the provider; its signature DKIM also uses this third-party domain. Without alignment with the visible domain, it fails DMARC. A “SPF successful” result therefore does not solve everything.

The store asks the supplier for authentication adapted to its domain and verifies a new real shipment. It also monitors order confirmations before strengthening its policy. These observations are hypothetical: they illustrate the checks to be made, not a diagnosis of your installation.

Roll out gradually and check results

Configure the necessary mechanisms following the instructions for each service. Google recommends starting DMARC with p=none, then adjusting the policy after observing authentication. Set up a reporting address that is actually tracked and designate who is responsible for interpreting them. Posting a recording without reviewing failures leaves problems invisible.

Then send an actual message from each service to an external test box. Review the recipient server's results in the headers, including Authentication-Results, and the domains used. The DKIM documentation explains this check. A green status in the sender tool or the simple presence of a DNS record does not demonstrate that all your flows are working.

Checklist to send to the technical manager

  1. Inventory active services and their sending domains.
  2. Identify the DNS manager and save the existing configuration.
  3. Check SPF for each affected envelope domain.
  4. Check DKIM selectors and signature activation.
  5. Check alignment DMARC to real messages.
  6. Plan the reception and analysis of reports.
  7. Test essential marketing messages and notifications.
  8. Correct legitimate flows before any more restrictive policy.

Limitations and common errors

Going directly to p=reject without inventory may block legitimate emails. Other mistakes to avoid include copying another company's records, replacing a SPF without checking active services, or posting a DKIM key with the wrong name.

These mechanisms do not replace consent to prospecting, nor the quality of the lists, nor the security of the accounts. They do not guarantee deliverability or make a message secure on their own. This guide explains the decisions; the DNS values ​​must be adapted by a competent person.

Frequently asked questions

Can the email provider configure everything?

He can provide instructions and manage the signature of his own shipments. Coordination with the DNS manager and other services remains necessary. Ask for evidence on each affected stream.

Is DMARC with p=none enough to protect the domain?

This is an observation step, not a request to block failures. Use the reports to identify legitimate services that need fixing, then decide on a suitable policy.

Why does an authenticated email still arrive as spam?

Authentication is only one element of control. The recipient also applies their own filters. Review returns and submission quality without promising that a DNS fix will remove any spam classification.

Your next step

Collect a recent message from each department and the list of their managers. Request a check of the SPF, DKIM and DMARC results and alignment before authorizing a change. This will give you a verifiable diagnosis rather than a simple “everything is configured”.

Sources and resources

A FIRST EXCHANGE

A project to develop?

Tell us about your site, campaigns or emails. We will define with you the next actions to take.

EN