ARC lets forwarders, mailing lists and gateways record what authentication looked like when a message reached them, and seal it. arc=fail means that chain of seals did not validate, so the receiver ignores it — and cannot use it to excuse a DMARC failure caused by the forwarding.
arc=fail (signature failed)
How other mail servers write it
The standard form (RFC 8617)
arc=fail smtp.remote-ip=192.0.2.1
| Result | arc=fail |
| Usually fixed by | Whoever forwarded or relayed the message |
| Standard | RFC 8617 (Experimental) |
| A failed chain | Is treated as if there were none |
| Values | pass, fail, none (cv= in the ARC-Seal) |
Check the sending domain
Enter the domain from the From address: we check its SPF, DKIM, DMARC and mail servers together.
What it means
Each intermediary that handles a message can add an ARC set: its view of the authentication results, a signature over the message, and a seal over the chain. The receiver checks them all. If any fails, the chain is worthless, and a DMARC failure caused by the forwarding stands. Whether a valid chain would have been trusted is the receiver’s own choice — Microsoft lets admins name trusted sealers.
Why it happens
- A later hop changed the message after it was sealed.
- The sealer’s key could not be found in DNS.
- A key rotated while messages sealed with the old one were in transit.
How to fix it
- If you sent the message: you cannot fix another server’s seal. Sign with DKIM for your own domain, which survives forwarding when the message is not changed.
- If you run the forwarder or list: seal after your last change, and keep the sealing key published.
- If you run the receiving mail system: add the intermediaries you trust as trusted ARC sealers.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 8617 — rfc-editor.org
- Configure trusted ARC sealers — learn.microsoft.com
- Troubleshoot email authentication in Microsoft 365 — learn.microsoft.com
- Sender Best Practices — senders.yahooinc.com