Michael Brunnbauer skrev den 2018-04-01 16:25:
hi
I think I lost quite a few customers in the last months because
DNS-lookups
are fucked up with Spamassassin so all DNSBL tests won't trigger while
not
reporting errors. A problem with newer versions of Net::DNS that has
been
known for months without any consequences - like a new release. This
sucks.
since spamassassin does NOT reject dont blame it
So I downgraded to Net-DNS-0.83 today and got spamassassin working but
not
spamd.
spamassassin -D looks like:
Apr 1 15:30:18.733 [22195] dbg: dns: hit
<dns:210.8.207.185.zen.spamhaus.org> 127.0.0.3
spamd -D looks like:
Apr 1 15:10:51 merlot spamd[6505]: dns: hit
<dns:210.8.207.185.zen.spamhaus.org> \# 4 7f000003
One time the result is an IP as integer and one time it's a normal IP.
The
integer result is not recognized and the DNSBL tests do not trigger.
What can I do?
say it sucks again :)
add trusted ips that should not reject to trusted_networks
or stop REJECT based on spamassassin ips blacklists
P.S.: This is the third time I try to send mail to the list - I hope it
works
this time. I'll try without PGP sig.
poor manns dkim :=)
i uaw poardix clamav spampd opendkim opendmarc pypolicyd-spf i never
rejected a maillist or wanted mail
