[Slackbuilds-users] Spamassassin from SBo - broken DNS RBL filtering?

Sebastian Arcus s.arcus at open-t.co.uk
Mon May 22 07:28:22 UTC 2017

On 22/05/17 00:27, Gerardo Zamudio wrote:
> On 05/20/2017 11:34 PM, Sebastian Arcus wrote:
>> Thank you! It would be really interesting if others could check their
>> machines and report here if they are seeing the same issue at their end.
>> To test, I just passed a mail message with a known spammy URL (detected
>> as a spammy URL on a good machine) through spamc - and if the spam
>> report didn't mention anything about any dns rbl test, I knew
>> Spamassassin wasn't working correctly.
> I use Amavis as an interface between SpamAssassin and Postfix. No issues
> here
> slack:~ # tail /var/log/maillog
> May 21 17:54:06 mail postfix/smtpd[15930]: NOQUEUE: reject: RCPT from
> static-IP_ADDRESS.bstnma.fios.verizon.net[IP_ADDRESS]: 554 5.7.1 Service
> unavailable; Client host [IP_ADDRESS] blocked using sbl.spamhaus.org;
> https://www.spamhaus.org/sbl/query/SBLCSS; from=<test at test.net>
> to=<USERNAME at yandex.com> proto=ESMTP helo=<WIN-LMN9SE23ES9>

I found that dns rbl's didn't work correctly in relation to spam URl's 
found inside emails. Above it seems the rejection is based on the 
originating host, unless I'm misreading the log?

More information about the SlackBuilds-users mailing list