t for your postfix configuration (main.cf)
smtpd_milters = unix:/var/run/spamass/spamass.sock [...]
Best regards,
Edda
212.186.35.163 for IP checks.
It's a parsing error in spamassassin. I don't know wether it's fixed in
3.4.1.
Best regards,
Edda
the rules ... and looks like an ugly workaround...
.. I would prefer to do this ONE rdns lookup in Received.pm, and
only if necessary. Opinions?
Edda
Am 25.11.15 um 09:55 schrieb Matthias Apitz:
El día Tuesday, November 24, 2015 a las 08:27:45PM +0100, Edda escribió:
I have found the bug in your patch, just a spelling issue:
pop:Mail eh$ diff -u SpamAssassin/Plugin/DNSEval.pm.ORG
SpamAssassin/Plugin/DNSEval.pm
--- SpamAssassin/Plugin
and this is exactly what
my patch does.
Edda
, but more
generic, for the existing NO_DNS_FOR_FROM rule and for the RDNS_NONE one.
Any suggestions are welcome.
Edda
Anyway, for the moment, here's the patch, diff is on version 3.4.1:
Rule (I tested it as a simple rule in local.cf, sure one can combine it
with RDNS_NONE):
ifplugin Mail::Sp
Am 23.11.15 um 10:33 schrieb Matthias Apitz:
What should I fix exactly if apache.org triggers this RDNS_NONE:
$ fgrep RDNS_NONE /tmp/apache.d
nov 23 08:30:06.666 [2204] dbg: rules: ran header rule __RDNS_NONE ==> got hit:
"[ ip=140.211.11.3 rdns= "
you can find the full -D output of such
