Skip to content

ARC sealing for forwarded mail to preserve DMARC verdicts

How ARC (Authenticated Received Chain) lets a cPanel server forward mail through itself while preserving the original DMARC verdict, and how to configure and verify it works.

When a cPanel server forwards mail to a Gmail or Microsoft 365 destination, DMARC alignment usually breaks (see the forwarders-srs KB). SRS fixes SPF; ARC fixes the rest. ARC (Authenticated Received Chain) adds a cryptographic record of the authentication results the message had when it arrived at the forwarder, signed by the forwarder. Downstream receivers that trust the forwarder can use the ARC chain to accept the pre-forward authentication, letting DMARC pass even though the immediate authentication is different.

What’s happening

ARC adds three headers to forwarded mail: ARC-Authentication-Results (a copy of what the forwarder saw), ARC-Message-Signature (signs the message body and headers), and ARC-Seal (signs the entire ARC chain). Receivers like Gmail evaluate ARC: if the forwarder is in their trusted list and the chain is intact, they trust the authentication results captured at the forwarder, even when SPF or DKIM has broken in transit. The result is DMARC pass for legitimate forwarded mail that would otherwise be quarantined.

How to verify

Check if ARC is enabled on the cPanel server. cPanel introduced ARC support in Exim configurations in recent releases:

exim -bP | grep -i arc
grep "arc_sign" /etc/exim.conf.localopts 2>/dev/null

Send a test message through a forwarder and inspect the destination headers:

ARC-Authentication-Results: i=1; mx.google.com;
   spf=pass smtp.mailfrom=sender@partner.com;
   dkim=pass header.d=partner.com;
   dmarc=pass header.from=partner.com
ARC-Message-Signature: i=1; a=rsa-sha256; d=forwarder.example.com; s=arc; ...
ARC-Seal: i=1; a=rsa-sha256; d=forwarder.example.com; cv=none; s=arc; ...

If you see those headers and the destination’s Authentication-Results shows arc=pass, the chain is working.

The fix

  1. Confirm cPanel version supports ARC. cPanel/WHM versions from 102+ include ARC sealing support. Check WHM > Exim Configuration Manager for ARC options.
  2. Generate an ARC signing key, separate from your DKIM key. Use a new selector like arc._domainkey.example.com. The key length should match DKIM best practice (2048-bit RSA).
  3. Publish the ARC selector’s public key in DNS as a TXT record at arc._domainkey.example.com.
  4. Configure Exim to ARC-sign all forwarded mail in /etc/exim.conf.local. The configuration adds an arc_sign configuration block with the domain, selector, and private key path.
  5. Validate the chain with a test forward through your server to a Gmail destination. The destination headers should show all three ARC headers and the arc=pass result.
  6. For the chain to actually help, the forwarder must be in the receiver’s trusted-forwarder list. Gmail maintains an internal list of trusted ARC signers — small operators may not be on it, in which case ARC doesn’t help with Gmail specifically (it still helps with other receivers). Building reputation as an ARC signer takes time and consistent good behavior.

For environments where forwarders are critical and DMARC enforcement is in flight, Stack Harbor implements ARC sealing as part of WHM server management.