Several years ago, there was a thread... http://www.mail-archive.com/[email protected]/msg19307.html
The short version is, BOFHCHECKHELO=1 causes too many rejections for some deployments, and so there was talk of implementing less-extreme HELO checks, such as ones to do some (but not necessarily all, depending on the contents of the bofh file) of the following: * hosts that say they are us (but are not really us) are blocked * HELO names that aren't even an FQDN are blocked * non resolvable HELO names are blocked * HELO names that don't share at least the top couple of levels with the actual FQDN are blocked (so, for instance, if the HELO name is hotmail.com, it would match if the sending host's PTR record says out2.mail.hotmail.com but not if it says cpe-24-210-138-71.woh.res.rr.com. At the end of the thread Grzegorz Janoszka had indicated he was planning to actually implement this soon (this was 2004), but I can't seem to find any later mention of it. Maybe I'm just not finding it. (The mailing list archives are kind of a mess to search through, or I don't know what I'm doing, or both. I tend for any given query to find the same three threads over and over and over again, but the results are not grouped by thread, so then I lose my place in the search results and get confused about which ones I've already perused...) So did anything ever come of this? There's no mention of it in the man pages that I can find. Does that mean it never happened? -- Nathan Eady Galion Public Library ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
