Re: How do you handle SPF errors?
Sam Varshavchik <[email protected]>
| Newsgroups | gmane.mail.imap.courier.general |
|---|---|
| Message-ID | <[email protected]> |
Alessandro Vesely writes: > On Sat 02/Dec/2023 01:20:38 +0100 Sam Varshavchik wrote: >> Alessandro Vesely writes: >> >>> It should return 4xx on DNS hiccups. That behavior shouldn't be difficult >>> to code, but what bofh setting would make it? >> >> Courier's implementation is based on an earlier SPF specification that >> directed that DNS lookup failures resulted in an "error" status. >> >> opt BOFHSPFHARDERROR is the setting. The default is >> >> opt BOFHSPFHARDERROR=fail,softfail >> >> So, either you added "error" here, or the reason for the failure is >> something else. > > > No, I had "error" in BOFHSPFHELO/MAILFROM. Too conservative. Now I removed > it, so it should correctly result in 4xx. > > Thank you for the clarification. That's not quite it. BOFHSPFHELO/BOFHSPFMAILFROM controls which SPF status will result in an error. BOFHSPFHARDERROR controls whether an error is reported as a hard or a soft failure. _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRupkKLJP96aW75pIOKYPgoojZS4gUCZWsmIQAKCRCKYPgoojZS 4vniAQC3AWqAS9ykeAcgEffTXlb7jEO3z5eRNjUr3/rvQY0lvAD/T+AZEmMSoV9/ wGz3FZK4l6PmwBRo3FeZ74RIcwfy6Qg= =h9Fl -----END PGP SIGNATURE-----