spamassassin problems?

[glg]

Within the last couple of days, it appears that spamassassin stopped working for my domain on www62. Nothing shows up in my spam folder, lots more in my inbox, but not as much as was going to spam folder. Figured I'd see if anyone else was having probs before opening a ticket.

[mharvey]

I have seen SpamAssassin stop running in the past, but not for a while. Look at the full headers for an email that you have received. If SpamAssassin is running you should see a header similar to:

X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on www58.hostpc.com

If you do see the header then SpamAssassin is running and scanned that message. If you do not see any headers starting with X-Spam in you email then it is likely that SpamAssassin is not running. Check your settings in DirectAdmin. If it is enabled but you are not seeing the headers then I would advise you open a helpdesk ticket.

[admin]

This can happen if a user gets mailbombed - the spam daemon gets confused/hung up trying to process everything for that one customer.

A quick ticket asking for a SA reset is all we need.

I clearded it on www62 and added a checker to make sure it wont happen again (I hope) :)

[mharvey]

Also: If you are seeing spam in you inbox that is not marked as spam you can also see why this was not detected as spam by looking at the headers. You should see a header starting with X-Spam-Status that looks similar to:


X-Spam-Status: No, score=7.5 required=8.0 tests=RCVD_IN_BL_SPAMCOP_NET=5,
URIBL_SBL=2.5

This example tells me that the message was not detected as spam ("No"), the score was 7.5, the requred score for spam is 8.0 and the tests that this message triggered were RCVD_IN_BL_SPAMCOP_NET and URIBL_SBL.

From that you can decide what adjustments, if any, you want to make to SpamAssassin. In this case the email that I received was spam. I decided to change the scoring for the rule URIBL_SBL to 3.0 so that in the future this email was be marked as spam.

More info about the tests that SA runs can be found at:
http://spamassassin.apache.org/tests_3_1_x.html

[Ortwin]

Wow! Thanks to all for posting this information. I was wondering why I was getting pounded with spam on 62.

:love

[glg]

This can happen if a user gets mailbombed - the spam daemon gets confused/hung up trying to process everything for that one customer.

A quick ticket asking for a SA reset is all we need.

I clearded it on www62 and added a checker to make sure it wont happen again (I hope) :)

Cool, thanks. In the future, I'll remember that the headers will be missing from non-flagged email as well (forgot about that) and if it's down I'll open a ticket.