Topic · Troubleshooting
DKIM body hash mismatch
A DKIM body hash mismatch means the received body does not match the canonicalized content digest in the signature.
How it works
Receivers recompute the digest after the declared body canonicalization and compare it with bh=.
What can go wrong
Disclaimer insertion, line-ending transformations or footer rewriting can break signatures in transit.
What to check or do
Compare raw content before and after forwarding and identify the first modifying intermediary.
Practical scenario
A mailing-list system appends a legal footer to a message after the original sender signs it. The final body differs from the signed content, so the recipient reports a DKIM body hash mismatch even though delivery through the list was expected.
Verification checklist
- Capture original and forwarded raw MIME messages.
- Review c= canonicalization and bh= digest scope.
- Compare modifications introduced at each trusted relay.
- Consider authenticated ARC handling or routing changes rather than disabling DKIM entirely.
How to investigate DKIM body hash mismatch
- Signal to investigate
- A server-added disclaimer can break DKIM on messages that were valid when sent.
- Evidence to collect
- Compare copies of the message before and after gateways and inspect body canonicalization.
- Common wrong conclusion
- Avoid regenerating a new signing key as the first fix when the body was modified in transit.
Put this into practice
Run a focused check, then explore protection if your domain needs it.