Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Magnus Bäck (magnusdsek.lth.se)
Date: Sun Nov 04 2007 - 08:45:03 CST
On Sunday, November 04, 2007 at 15:24 CET,
Frank Agricola <fagricolasolcon.nl> wrote:
> I am trying to set up some very strict checks for incoming mail, the
> check that i would like to activate is reject_unknown_helo_hostname
> But if i do so, e-mail from customers with in incorrect configured
> dns/mailserver is beeing rejected as well.
If you want to stop spam I don't think reject_unknown_helo_hostname is
very effective compared to the false positives you are going to get.
> I would like to override this by doing an first check in some kind of
> whitelist file, if found in here - the remaing check should not be
> done and e-mail accepted.
> However this does not seem to work.
> I added an customer IP (184.108.40.206) in the mynetworks section en
> still the reject_unknown_helo_hostname rule is making the e-mail.not
> accepted (because correct A or MX dns info is missing for this ip)
> Of course when i works i will set up an better rule with and hash
> database file instead...
Indeed, you probably don't want to grant the client relay access, just
exempt them from rejection because of their HELO name.
Show "postconf -n" output and logs from a rejection that accoring to you
shouldn't take place.