> Why is it misconfigured? Its SPF record is fine, and IP 178.63.50.70 > is one of the authorized addresses.
> Why wasn't that "none", given that there's no SPF record for mx1.evo.pl? The reject isn't because of SPF, but because of HELO > if BOFHCHECKHELO really does what it's documented to do, and what > indicates this message, then you should not use it, since it violates RFC > 821 and all its successors. It may cause troubles to you (well, it just > did...) Actually, it also slashed about 30% of incoming spam, and I didn't notice any illogical behaviour of my courier when analyzing the logs. This gem is just one of hundreds hosts that connect to my server every day, and they don't have issues (unless, of course, they do, but 99.9% of these are either dynamic IPs or shady mailing servers). I sumbit to you: $ host mx1.evo.pl mx1.evo.pl A 178.63.45.155 However, I'm being reached by 178.63.50.70, thus HELO is mismatched, which suits my aggressive antispam policy - mail is rejected. Getting back to the point of discussion, Sam's hunch was duly justified, I used space instead of tabulation, this has now been fixed but still waiting for another attempt from their side. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
