Rspamd 4.3.0 stops forwarded mail from softening DMARC rejects
Rspamd 4.3.0 fixes bugs that let an unauthenticated attacker crash the spam filter’s workers or slip forged authentication results through it.

Rspamd 4.3.0 fixes bugs that let an unauthenticated attacker crash the spam filter’s workers or slip forged authentication results through it.
A header line without a colon was enough to stop a worker, and an empty Deliver-To header could crash workers again and again, and sites running the milter proxy, the part that connects Rspamd to the mail server, have a separate bug.
From 4.0.0 through 4.2.3, the proxy released a session twice when an upstream failed; before this release, ARC sets added after a genuine one could soften a DMARC reject.
Version 3.14 is not affected, and in 4.3.0 each failed message gets exactly one TEMPFAIL.
ARC lets mail forwarders vouch for the authentication checks a message passed before they handled it.
Rspamd also changed several checks on purpose, so verdicts will shift, and if you keep local scores or scripts that read those options, test them before rolling the upgrade out.
Why it matters
A sender could write dmarc=pass into it and have that read as a real result.
- Watch for revised vendor guidance, fixed versions and mitigation updates.