How to Check SpamAssassin

Discussion in 'Site & Server Administration' started by seismicmike, Dec 29, 2008.

  1. #1
    Hi. I took over server management recently at my company. I've been noticing spam slipping through our mail system recently, and I was wondering if there was a way for me to quickly and easily check to see if our spamassassin's filters are working. I'm worried that the filters aren't being applied or that it's "forgotten" what it's supposed to be looking for.
     
    seismicmike, Dec 29, 2008 IP
  2. SSANZ

    SSANZ Peon

    Messages:
    861
    Likes Received:
    10
    Best Answers:
    0
    Trophy Points:
    0
    #2
    Spam ass comes with a readme, it also produces logs afaik.

    What mail server software are you using?
     
    SSANZ, Dec 29, 2008 IP
  3. seismicmike

    seismicmike Peon

    Messages:
    63
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    I'm using sendmail on RHEL 5.

    I ran a test using the GTUBE test (I think that's what it's called), there's a sample spam in the /usr/share/docs folder, and it seemed to work fine. Maybe this is just a really high traffic spam we're getting. They did say they were going to amp things up, but if Spamassassin is still catching 95% like it says it's supposed to, then they are sending a ton.

    I'm hoping spamassassin comes out with a new update. The Rules_du_jour are updated every night on a cron job, but I think this might call for a major update.

    Thanks for your help.
     
    seismicmike, Dec 30, 2008 IP
  4. seismicmike

    seismicmike Peon

    Messages:
    63
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #4
    I changed the cron job from

    sa-update
    Code (markup):
    to

    sa-update -D
    Code (markup):
    so I could get more information. There are a couple lines that are bothering me in this:

    ...
    [7781] dbg: diag: module not installed: Net::Ident ('require' failed)
    ...
    [7781] dbg: diag: module not installed: Mail::DKIM ('require' failed)
    ...
    [7781] dbg: diag: module not installed: Encode::Detect ('require' failed)
    ...
    [7781] dbg: channel: metadata version = 729912
    [7781] dbg: dns: 4.2.3.updates.spamassassin.org => 729912, parsed as 729912
    [7781] dbg: channel: current version is 729912, new version is 729912, skipping channel
    [7781] dbg: diag: updates complete, exiting with code 1
    Code (markup):
    Does this mean that updates are not being run and that spamassassin is not being updated?
     
    seismicmike, Dec 30, 2008 IP