Bill Taroli writes:
I noticed, having upgraded to 0.48 just over the weekend, that a BOFHCHECKHELO item we'd been discussing -- though had no particular agreement on -- wasn't in fact included in courier/submit.C. Namely, to reduce (or make configurable) the severity of SMTP result codes for HELO and DNS mismatches. From our original conversation, I'd suggested that 417 would be better than 517 because it actually allows a proactive administrator time to put exceptions into place without getting angry calls from users who can't receive their mail from legitimate -- albeit misconfigured -- sources.
Is there a process for ratifying or submitting such requests for change that needs to be followed here?
No. No process needs to be followed.
I was not looking at anything new in the last two months, instead focusing on troubleshooting the authentication library overhaul.
With this particular proposal, the primary issue is: you will find that quite a few broken mail servers interpret a 4xx response to a HELO as meaning "disconnect and try again immediately".
The results will not be pretty.
pgp53Etu7HhGg.pgp
Description: PGP signature
