Topic: Spamassassin header lines?

[allsorts]

Dumb question: Does Spamassassin put anything into the header of emails it processes?

Spamassassin should be running on my server but when my ISPs spam filter failed yesterday spam started landing in my inbox without any hint that it had been looked at on my server. I see the "X-Virus-Checked: Checked by ClamAV on..." but nothing from Spamassassin.  B-(

[william_syd]

Dumb question: Does Spamassassin put anything into the header of emails it processes?

Spamassassin should be running on my server but when my ISPs spam filter failed yesterday spam started landing in my inbox without any hint that it had been looked at on my server. I see the "X-Virus-Checked: Checked by ClamAV on..." but nothing from Spamassassin.  B-(

It does here. Do you have it Enabled?

X-Virus-Checked: Checked by ClamAV on magicwilly.info
X-Spam-Status: No, hits=1.0 required=4.0 tests=SPF_FAIL
X-Spam-Check-By: magicwilly.info

[allsorts]

It does here. Do you have it Enabled?

I'm running SME 7.3, upgraded from 7.2 if that is relevant.

The web interface said it was but:

[root@srv1 etc]# config getprop spamassassin status
disabled
[root@srv1 etc]# config getprop spamd status
enabled

I then toggled the setting in the web page to "disabled" saved, then back to "enabled" saved and now have:

[root@srv1 etc]# config getprop spamassassin status
enabled
[root@srv1 etc]# config getprop spamd status
enabled

I then used the web interface "reconfigure" option in the reboot/shutdown and let that complete and reboot etc. I'm still not seeing any tag lines in email headers. Logged in at the command line a ps -xa shows spamd running and a couple of spamd children.

I assume that qpsmtpd is what calls spamassassin and ClamAV the latter is working (at least a tag line is there) but not anything from SA. Where would qpsmtpd be looking to know to call SA?

[william_syd]

The default was only external email got scanned for spam.

It looks like you have reached the point where it is not working "out of the box".

Time for a bug report.

[allsorts]

More digging and better reading of the logs it appears that there has been a change to the configuration in the upgrade from 7.2 to 7.3. Spamassassin isn't called for local connections anymore, this is a problem when using the maildrop method of mail collection as qpsmtpd is called as a local connection from fetchmail...

A bug report has been filed:  http://bugs.contribs.org/show_bug.cgi?id=3849

[william_syd]

This also occurred with the fetchmail contrib.

http://bugs.contribs.org/show_bug.cgi?id=2226

And the base system.

http://bugs.contribs.org/show_bug.cgi?id=2223

[allsorts]

Thanks for those, I'll add them to the bug I filed for information.

The resolution of  Bug 2223 should have fixed it so why has it come back with the upgrade to 7.3?

My qpsmtpd logs show connections coming from 127.0.0.1 not 127.0.0.200 as the fix should be...

Digs ha ha the 127.0.0.200 is hardcoded into the template.... I have a custom template for  /etc/fetchmail that is still hardcoded "localhost".

Right off to check & test then close the bug!

[CharlieBrady]

More digging and better reading of the logs it appears that there has been a change to the configuration in the upgrade from 7.2 to 7.3. Spamassassin isn't called for local connections anymore, this is a problem when using the maildrop method of mail collection as qpsmtpd is called as a local connection from fetchmail...

Not so if you have kept your system updated. Do you have a custom template?