Spamassassin working but not adding headers?

T

thoroughfare

Verified User
Joined
Aug 11, 2003
Messages
540
Hi,

Spamd is running but isn't adding its headers to emails.

I'm using FreeBSD 5.3 and I installed SpamAssassin from the FreeBSD ports tree (it's version 3.x).

I've edit my exim.conf properly according to DA's knowledge base and spamd is started on boot using /usr/local/etc/rc.d/sa-spam.sh.

Spamd is running fine:

[root@xxxxx root]ps aux | grep spamd
root 26773 0.0 1.1 23448 22496 ?? Is 1:58AM 0:00.95 /usr/local/bin/spamd -c -d -r /var/run/spamd.pid (perl)
root 26777 0.0 1.1 23448 22472 ?? I 1:58AM 0:00.00 spamd child (perl)
root 26778 0.0 1.1 23448 22472 ?? I 1:58AM 0:00.00 spamd child (perl)
root 26779 0.0 1.1 23448 22472 ?? I 1:58AM 0:00.00 spamd child (perl)
root 26780 0.0 1.1 23448 22472 ?? I 1:58AM 0:00.00 spamd child (perl)
root 26781 0.0 1.1 23448 22472 ?? I 1:58AM 0:00.00 spamd child (perl)

/var/log/exim/mainlog shows no errors, and the email headers from test emails show:

Received: from mail by rubix.retroweb.net with spam-scanned (Exim 4.44)

But yet still no Spamassassin headers :( I also don't know if it's recognising any spam yet as I haven't given it enough time yet.

Any ideas would be much appreciated :)

Thanks!
Matt
 
im having the same issue if anyone finds a fix please let me know :)
 
I'm sorta experiencing the same thing. When an email comes through, it leaves out the ***spam*** from the header.

But when I test it via sending mail to myself from an external mail account, it DOES work. (ie: I include the magic words viagra, online pharmacy, $$$, etc)

So I have it working sometimes, and not others.
 
Hello,

Remember that you need to have a /home/user/.spamassassin/user_prefs file. It will be created once that User turns it on in his/her account.

You'll know if it's working because the transport in the exim/mainlog will say spam-scanned (as mentioned above). At that point, everything should be working, so check the message headers to see if there is an X type header mentioning the score.

John
 
John,

This file exists, it is the SAME mail account that I get spam coming in, some times it puts ****spam**** in the heading, other times it doesn't.

BOTH times it does attach the original email as an attachment, and the body of the emails say 'spam software running on host xxx.....'.

So the issue is not that spam assassin is NOT running, it is running, the user is setup correctly, SA does identify it as spam, but sometimes forgets to re-write the subject.

Here is the user_perfs file for my particular domain - the one I am referring to in the above example:

Code: 
required_hits   5.0
rewrite_subject 1
subject_tag     *****SPAM*****
report_safe     1

blacklist_from *@fangartists.com



required_score 5.0
rewrite_header subject *****SPAM*****
 
Hello,

I really couldn't say.
Check the actual mail headers to see what score SA is giving the mail.

John
 
In both cases, the score is higher than the threshold (obviously) as it has written it as spam.

Headers from an email that DID have the subject re-written:
Code: 
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on xxx.xxx.com.au
X-Spam-Level: ******
X-Spam-Status: Yes, hits=6.4 required=5.0 tests=CLICK_BELOW,HTML_20_30,
	HTML_LINK_CLICK_HERE,HTML_MESSAGE,MIME_HTML_ONLY,
	RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DSBL,RCVD_IN_XBL autolearn=no 
	version=2.64

Headers from one that was marked as spam, original email as attachment, but did not re-write the subject:

Code: 
X-Spam-Flag: YES
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on coolio.djc.com.au
X-Spam-Level: ******
X-Spam-Status: Yes, hits=6.0 required=5.0 tests=BIZ_TLD,DISGUISE_PORN,
	DNS_FROM_RFCI_DSN,HTML_50_60,HTML_FONTCOLOR_BLUE,
	HTML_FONTCOLOR_UNKNOWN,HTML_MESSAGE,MAILTO_TO_SPAM_ADDR autolearn=no 
	version=2.64


I spoke to somebody who said that it is a bug in the version of SA that DA uses, because the current version DA uses is outdated. His suggestion was to tell DA to use the latest version of SA?!?!?
 
Hello,

The spamd.sh should be set to version 3.0.4 which is the latest version. To update, just rerun the spam.sh. (Make sure you have the latest version of DA so that you have a new version of the spam.sh. If not, just edit the spam.sh and set the version to 3.0.4 and run it.

John
 
John,

We just updated a user system to the latest version of DA, and spam.sh still says version 3.0.2.

I changed the code in spam.sh to say 3.0.4 and ran spam.sh.

SpamAssassin now reports as running version 3.0.4.

We'll see whether it's now adding headers properly or not for this client.

Jeff
 
You must log in or register to reply here.
Back
Top