the socket for your postfix configuration (main.cf)
smtpd_milters = unix:/var/run/spamass/spamass.sock [...]
Best regards,
Edda
#x27;t use
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
uld
result in more work on 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
ree and this is exactly what
my patch does.
Edda
x27;s better to use the Spamassassin Resolver, 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 ca
tp (Exim 4.76)
(envelope-from)
id 1a0c7H-0003WU-3m
forg...@unixarea.de; Sun, 22 Nov 2015 22:24:11 +0100
RDNS_NONE shouldn't fire on that. Edda
