github postalsys/mailauth v8.1.0

one hour ago

8.1.0 (2026-11-16)

Summary

The experimental DKIM2 support now follows draft-ietf-dkim-dkim2-spec-09 (with draft-ietf-dkim-dkim2-dns-02 and draft-gondwana-dkim2-authres-01) instead of spec-06. Nothing outside DKIM2 changed.

Who should upgrade

  • Everyone signing or verifying DKIM2: messages are now checked by the spec-09 rules, which interoperate with other spec-09 implementations.
  • No change for SPF, DKIM, DMARC, ARC, BIMI or MTA-STS users.

Action required for DKIM2 users

  • Re-signing a message that already has DKIM2 header fields now verifies it first and fails with ENOTVERIFIED (or ETEMPNOTVERIFIED) unless it is a Fully Verified DKIM2 Message. Forwarders need DNS (resolver) and should pass the envelope the message arrived with as received. Use outOfBand: true only where an out-of-band arrangement covers it. strict: true makes received required.
  • The From domain has to match the signing domain of the hop that put it into the message; the signer refuses otherwise.
  • , in s= and h= now means every signature or hash must pass, and an unknown algorithm counts as a PERMERROR for its group. Use groups (signatureData: [[rsaKey, ed25519Key], [mlDsaKey]], CLI --group) for alternatives.
  • A null body Recipe is now a PERMERROR, and the donotmodify and donotexplode flags no longer have any effect.
  • Error strings follow section 14 of spec-09; chain of custody and timestamp errors are now FAIL.

Highlights

  • Authentic From check, including the Domain Policy Record (f=strict at _domainkey.<domain>).
  • ML-DSA-44 (mldsa44): signing on Node.js 24 and later, verification on every supported Node.js version, with a dependency-free FIPS 204 verifier where node:crypto has no ML-DSA.
  • AND/OR signature and hash groups, several keys with one algorithm, and | groups from the signer.
  • Recipes support u steps for bytes that are not UTF-8, and are validated strictly (unique lower case keys, one key per step, no Recipes for unsigned header fields).
  • Fixed the direction of the chain of custody match for null MAIL FROM and nd= hops.
  • New dkim2-sign CLI options: --group, --received-mail-from, --received-rcpt-to, --out-of-band, --strict, --dns-cache.

Features

  • dkim2: follow draft-ietf-dkim-dkim2-spec-09 (#187) (594e9f2)

Don't miss a new mailauth release

NewReleases is sending notifications on new releases.