Risorse · 34

Migliorare l'affidabilità del mittente e la deliverability delle email.

Verificare l'identità del mittente, le classi dei messaggi, il comportamento di disiscrizione e le cause di rifiuto.

Aggiornato · 8 min

Armadi di comunicazione e cablaggio di rete in una sala vuota Illustrazione editoriale generata con IA

Obiettivi di questa guida

  • Mappare i flussi.
  • Autenticare i domini.
  • Abilitare il ritiro.
  • Diagnosticare i rifiuti.

Verifica rapida

  • Quali sistemi inviano email con questo dominio?
  • I messaggi reali superano i controlli SPF, DKIM e DMARC previsti?
  • Ogni messaggio è promozionale o transazionale?
  • La richiesta di disiscrizione funziona correttamente?
  • I rifiuti sono raggruppati per causa?

Metodo passo passo

  1. 1

    Invio dell'inventario

    Separare newsletter, automazioni, ricevute e avvisi. Registrare dominio, provider, volume, scopo e proprietario per ogni flusso.

    Risultato: mappa del flusso e del dominio.

  2. 2

    Verifica dell'autenticazione

    Testare SPF, DKIM, DMARC e l'allineamento del dominio mittente su campioni inviati. Una configurazione DNS prevista non garantisce il funzionamento di ogni percorso di invio.

    Risultato: intestazioni ispezionate e risultati dell'autenticazione.

  3. 3

    Corrispondenza con le aspettative del destinatario

    Verificare l'iscrizione, la frequenza, il contenuto promesso e la separazione del traffico promozionale e transazionale. Evitare promozioni indesiderate nei messaggi di servizio.

    Risultato atteso: regole per classe di messaggio.

  4. 4

    Test di revoca

    Per le email promozionali applicabili, verificare la presenza di un link visibile e il comportamento di un clic conforme ai requisiti del provider e alla RFC 8058. Verificare che la rimozione venga effettivamente elaborata.

    Risultato atteso: prove complete della disiscrizione.

  5. 5

    Monitoraggio della reputazione

    Tracciare i rifiuti permanenti e temporanei, i reclami e i segnali tra destinatario e provider. Analizzare per flusso e provider anziché con una media globale.

    Risultato atteso: analisi delle cause di mancata consegna.

  6. 6

    Correzione e ritest

    Affrontare innanzitutto i problemi di autenticazione, le liste non qualificate, gli errori tecnici e le disiscrizioni non funzionanti. Aumentare gradualmente il volume delle attività laddove il contesto lo richieda.

    Risultato atteso: piano di correzione e risultati osservati.

Indicatori di gestione

IndicatoreCosa misuraPrima azione
AutenticazioneMessaggi reali con risultati SPF/DKIM/DMARC attesiCorrezione del percorso di invio
RifiutiFrequenza e cause per flussoPulizia o riparazione della lista
RitiroRichieste promozionali applicateCorrezione delle intestazioni e dell'elaborazione
ReclamiReport tracciati per campagnaRevisione del targeting e della frequenza

Errori comuni

  • Presupposto che il DNS pubblicato provi ogni flusso
  • Mix di email transazionali e promozionali
  • Confondere l'apertura con la consegna nella casella di posta
  • Mostrare un link di disiscrizione che non rimuove effettivamente un destinatario

Domande frequenti

È sufficiente il solo SPF?

No. I requisiti dei destinatari variano in base al volume e al contesto; verificare anche DKIM, DMARC e l'allineamento applicabile.

Ogni messaggio deve essere consegnato con un clic?

Le regole del provider distinguono i messaggi promozionali da quelli transazionali, quindi classificare prima ogni flusso.

L'apertura dimostra la consegna?

No. Le metriche di apertura hanno i propri limiti e non sostituiscono i risultati di consegna.

Sicurezza email: identità, allineamento e trasporto

Le note dettagliate di questa edizione sono disponibili in inglese.

Domain authentication, transport confidentiality and inbox placement are different questions. SPF, DKIM and DMARC inform domain identity; MTA-STS and DANE concern server-to-server connections; reports help observe failures. None of these signals proves a message is benign.

References and status checked on .

Which mechanism answers which question?

Which mechanism answers which question?
Mechanism and sourceWhat is checkedWhere to find evidenceLimit to retain
SPF

SPF · RFC 7208

Authorisation of the sending IP for the SMTP envelope domain; DMARC uses MAIL FROM.The evaluated domain’s TXT record and receiver result. Evaluation allows 10 DNS-querying terms, rather than simply 10 network requests.Forwarding may change the observed IP. Selecting multiple SPF records produces permerror; an SPF pass does not prove alignment with From.
DKIM

DKIM · RFC 6376

DKIM cryptography · RFC 8301

Cryptographic verification of signed message parts for the signature’s d= domain.DKIM-Signature, selector s=, domain d= and key under selector._domainkey. RFC 8301 requires RSA ≥ 1,024 bits, recommends ≥ 2,048 bits and excludes rsa-sha1.A valid signature from another domain may not satisfy DMARC. Changes to signed parts can break verification; DKIM does not encrypt the message.
DMARC

DMARC · RFC 9989

Links the visible From domain to at least one SPF- or DKIM-authenticated, aligned identifier.The TXT policy discovered through _dmarc and trustworthy results produced at reception. Record alignment mode and the domain actually evaluated.A pass neither guarantees delivery nor endorses content. Receivers retain local policy; DNS errors and non-conforming messages require separate handling.
DMARC aggregate / failure reports

DMARC aggregate reports · RFC 9990

DMARC failure reports · RFC 9991

Observation of streams using the domain: aggregate statistics and, separately, details about failing messages.rua / ruf destinations, covered period and received reports. Their formats are now specified in separate RFCs published in May 2026.Missing reports do not prove no mail was sent. Detailed reports may expose message data; define suitable access, minimisation and retention.
MTA-STS

MTA-STS · RFC 8461

Recipient-domain policy for SMTP TLS transport and expected MX hosts._mta-sts TXT, HTTPS policy at /.well-known/mta-sts.txt and certificate. Three modes: testing, enforce and none.Applies to supporting servers and transport, without end-to-end encryption. Initial discovery and caching have their own limits.
TLS-RPT

SMTP TLS Reporting · RFC 8460

Reporting of successful and failed TLS negotiation or validation between servers._smtp._tls TXT, reporting destinations and received JSON data, correlated with transport logs.Observation does not enforce encryption. TLS reports and DMARC domain-identity reports describe different events.
DANE for SMTP

DANE for SMTP · RFC 7672

TLS transport authentication using DNSSEC-protected TLSA records.Validated DNSSEC chain, SMTP service TLSA record and a match with the presented certificate or key.DNSSEC validation is required on this path. DANE does not validate From or replace SPF, DKIM and DMARC.
ARC

ARC · RFC 8617

Carries authentication assessments along paths involving intermediaries.ARC header sets, chain validation and a trust decision about intermediaries.RFC 8617 is Experimental. ARC is not a trust framework and does not automatically make a message safe or deliverable.

DMARC in 2026: documentation changes

Reference
RFC 9989, published in May 2026, replaces RFC 7489 and RFC 9091. Aggregate and failure reporting are separated into RFC 9990 and RFC 9991.
Discovery and alignment
The specification defines DNS Tree Walk discovery. Do not infer organisational domains by naively retaining the final two labels.
Testing a deployment
pct is removed; the new t=y requests handling one level below the published failure policy: reject becomes quarantine, and quarantine becomes none. t=n is the default.
Interoperability
The standard advises against p=reject for general-purpose email domains. Inventory forwarding and mailing lists and check actual implementations before changing policy.

Publication of an RFC does not show that every provider already implements that version. Check documentation, observed results and exceptions in your own streams. These examples are educational and provide no ready-to-deploy DNS record. RFC 9989 →

Understand DMARC logic with a scenario

Simplified model: a conforming From message, an already discovered DMARC policy, one SPF MAIL FROM result and one examined DKIM signature. You supply alignment based on the evaluated domains and mode. The tool performs no DNS resolution or signature verification and predicts no delivery.

(SPF pass AND aligned) OR (DKIM pass AND aligned)

With multiple DKIM signatures, check each result / d= pair: one valid, aligned signature can suffice. Never combine one signature’s pass with an aligned domain from another failing signature. DNS discovery errors, absent policy and invalid From fields are outside this model. All choices stay in your browser.

Six educational cases, readable without JavaScript

Six educational cases, readable without JavaScript
ScenarioSPF: result / alignmentDKIM: result / alignmentExpected interpretation
Aligned SPF is sufficientpass — authenticated
Yes
fail — observed failure
No
pass — at least one authenticated and aligned path

The SPF path meets both conditions.

Aligned DKIM is sufficientfail — observed failure
No
pass — authenticated
Yes
pass — at least one authenticated and aligned path

The DKIM path meets both conditions independently of the other path in this model.

Two passes without alignmentpass — authenticated
No
pass — authenticated
No
fail — no authenticated and aligned path in this scenario

Two third-party domains passing technically does not validate From.

Aligned domains, no authenticationfail — observed failure
Yes
fail — observed failure
Yes
fail — no authenticated and aligned path in this scenario

A matching domain does not replace successful authentication.

Incomplete evidenceResult not supplied
Alignment not supplied
fail — observed failure
No
Undetermined — complete the observations

Missing evidence on one path cannot be invented.

Proven DKIM, unknown SPFResult not supplied
Alignment not supplied
pass — authenticated
Yes
pass — at least one authenticated and aligned path

One complete positive result suffices even when the other path is unknown.

Prepare an actionable email review

Prepare an actionable email review
StreamEvidence to correlateUseful decision
Alerts, receipts and resetsProvider and From domain, envelope and DKIM identities, tracking ID, SMTP response and available delivery event.Separate transport failure, authentication error and absence of reading. Define an alternative for a critical service.
Campaigns and newslettersDomains and subdomains, alignment results, representative samples from every platform, withdrawal mechanism and stream-specific errors.Repair the affected sending path before changing a global policy; do not equate authentication with recipient expectations.
Forwarding and mailing listsPath before and after the intermediary, message changes, SPF/DKIM outcomes and ARC information when present.Explain the observed break and local policy; do not assume a valid ARC chain compels acceptance.
Transport to MX hostsRelevant MTA-STS policy or TLSA, certificates, DNSSEC validation for DANE, TLS reports and timestamped logs.Associate failures with the relevant host and period. Test changes within authorised scope and retain rollback.

Continue with domain and DNS governance →

Primary sources and publication dates

Dates below identify RFC publication months, separately from the consultation date. Descriptions and cases are editorial summaries rather than complete normative extracts.

Riferimenti ufficiali

I riferimenti supportano il metodo. Adattare i controlli al proprio contesto; non costituiscono una certificazione. I titoli dei riferimenti originali e i documenti di origine potrebbero essere in un'altra lingua.