SpamAssassin stops working

Discussion in 'HOWTO-Related Questions' started by heygazeebo, May 26, 2006.

  1. heygazeebo

    heygazeebo New Member

    Hi Everyone,

    I followed falko's guide to setting up postfix / mysql etc. on debian, and then followed the guide to add mailfiltering to it. After just a bit of tinkering it mostly worked properly, until i noticed that at some point SpamAssassin had stopped scanning my emails. As best i can figure it was when i added in the mailfiltering portion of the setup. Virus detection is still working, but not Spam. Anybody have any suggestions?
     
  2. falko

    falko Super Moderator ISPConfig Developer

    Are there any errors in your log files?
     
  3. heygazeebo

    heygazeebo New Member

    No, the only mention i see of anything related to spam in the log files is when it tagged somthing as spam.

    It does say this when i start amavisd...

    It says that among the list of modules....

    I checked syslog and mail.log and mail.err, the only error i am seeing is this one:

    Im not sure what that one means though..

    Thanks,
     
  4. falko

    falko Super Moderator ISPConfig Developer

    You could try to update to the latest SpamAssassin version. Hopefully that solves the problem...
     
  5. heygazeebo

    heygazeebo New Member

    Can you tell me how to find out what version of spamassassin i am running?

    I did this:
    Code:
    /usr/bin/spamassassin -V
    SpamAssassin version 3.0.3
      running on Perl version 5.8.4
    
    But i do not think that is the correct?

    I did apt-get upgrade spamassassin and it upgraded a lot of stuff, but that version stayed the same

    Code:
    apt-get upgrade spamassassin
    Reading Package Lists... Done
    Building Dependency Tree... Done
    The following packages will be upgraded:
      libmysqlclient12 lynx mysql-client mysql-common mysql-server postfix
      postfix-mysql postfix-tls
    8 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    I am seeing this in my headers to my email, but nothing to mention Spam anymore..

    Code:
    X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at localhost
     
  6. falko

    falko Super Moderator ISPConfig Developer

    That is the correct way to find out. :)

    The packages are not always up to date. If you want the newest version, you must compile it yourself.
     
  7. heygazeebo

    heygazeebo New Member

    nope..

    Code:
    Jun  3 12:46:58 localhost amavis[778]: Module Mail::SpamAssassin  3.001002

    Code:
    /usr/bin/spamassassin -V
    SpamAssassin version 3.1.2
      running on Perl version 5.8.4
    Upgrading to the new version doesnt seem to have done the trick, it does not seem to be invoking spamassassin and doing the scanning anymore. Any other suggestions? Everything else is working perfectly!
     
  8. falko

    falko Super Moderator ISPConfig Developer

    Did you maybe change /etc/amavisd.conf before it stopped working?
     
  9. heygazeebo

    heygazeebo New Member

    uhmm..

    I do not seem to have an /etc/amavisd.conf file.. i have an /etc/amavisd/amavisd.conf file though.... could that be part of the problem?
     
  10. falko

    falko Super Moderator ISPConfig Developer

    Sorry, I meant /etc/amavis/amavisd.conf... Did you change that one recently?
     
  11. heygazeebo

    heygazeebo New Member

    nope

    nope, havent changed that file at all.. ill delete it and re-create it based on the HOW-TO... maybe i inadvertantly edited it...

    I don't think this has anything to do with it, but if i do an saslauthd restart, it says saslauthd not running, and when it tries to restart it fails...
    Code:
    /etc/init.d/saslauthd restart
    Stopping SASL Authentication Daemon: (not running).
    Starting SASL Authentication Daemon: (failed)
    Im not sure if that could have any relevence, i have been playing a lot with my install and when i ran that command it seemed a little odd...
     
  12. heygazeebo

    heygazeebo New Member

    amavisd

    I redid the conf file amavisd.conf but it still does not appear to be invoking spamassassin...
     
  13. falko

    falko Super Moderator ISPConfig Developer

    Is SpamAssassin in this path?
    Code:
    $path = '/usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin';
    Please edit /etc/init.d/saslauthd and change PIDFILE to

    Code:
    PIDFILE="/var/spool/postfix/var/run/${NAME}/saslauthd.pid"
     
  14. heygazeebo

    heygazeebo New Member

    ...

    Thanks, that solved the SASL thing, i'm sorry i missed that in the How-To...

    SpamAssassin is located in /usr/bin, and has the following permissions...

    Code:
    /usr/bin# ls -la spamassassin 
    -r-xr-xr-x  1 root root 24717 2006-06-03 05:10 spamassassin
    If i do a whereis spamassassin i get this:

    Code:
    whereis spamassassin
    spamassassin: /usr/src/spamassassin-3.0.3/spamassassin.raw /usr/src/spamassassin-3.0.3/spamassassin.spec /usr/bin/spamassassin /etc/spamassassin /usr/share/spamassassin /usr/share/man/man1/spamassassin.1p.gz
     
  15. falko

    falko Super Moderator ISPConfig Developer

    What's in /var/log/mail.warn and /var/log/mail.err?

    When you restart amavisd, do you see any errors in /var/log/mail.log?
     
  16. heygazeebo

    heygazeebo New Member

    Code:
    Jun  8 11:44:26 localhost amavis[9849]: starting.  amavisd-new at danbury amavisd-new-20030616-p10, Unicode aware, LANG=en_US
    Jun  8 11:44:26 localhost amavis[9849]: Perl version               5.008004
    Jun  8 11:44:26 localhost amavis[9849]: Module Amavis::Conf        1.15
    Jun  8 11:44:26 localhost amavis[9849]: Module Archive::Tar        1.23
    Jun  8 11:44:26 localhost amavis[9849]: Module Archive::Zip        1.14
    Jun  8 11:44:26 localhost amavis[9849]: Module Compress::Zlib      1.34
    Jun  8 11:44:26 localhost amavis[9849]: Module Convert::TNEF       0.17
    Jun  8 11:44:26 localhost amavis[9849]: Module Convert::UUlib      1.051
    Jun  8 11:44:26 localhost amavis[9849]: Module DBI                 1.46
    Jun  8 11:44:26 localhost amavis[9849]: Module DB_File             1.808
    Jun  8 11:44:26 localhost amavis[9849]: Module MIME::Entity        5.417
    Jun  8 11:44:26 localhost amavis[9849]: Module MIME::Parser        5.417
    Jun  8 11:44:26 localhost amavis[9849]: Module MIME::Tools         5.417
    Jun  8 11:44:26 localhost amavis[9849]: Module Mail::Header        1.62
    Jun  8 11:44:26 localhost amavis[9849]: Module Mail::Internet      1.62
    Jun  8 11:44:26 localhost amavis[9849]: Module Mail::SpamAssassin  3.001002
    Jun  8 11:44:26 localhost amavis[9849]: Module Net::Cmd            2.26
    Jun  8 11:44:26 localhost amavis[9849]: Module Net::DNS            0.48
    Jun  8 11:44:26 localhost amavis[9849]: Module Net::SMTP           2.29
    Jun  8 11:44:26 localhost amavis[9849]: Module Net::Server         0.87
    Jun  8 11:44:26 localhost amavis[9849]: Module Time::HiRes         1.59
    Jun  8 11:44:26 localhost amavis[9849]: Module Unix::Syslog        0.100
    Jun  8 11:44:26 localhost amavis[9850]: Found $file       at /usr/bin/file
    Jun  8 11:44:26 localhost amavis[9850]: No $arc,          not using it
    Jun  8 11:44:26 localhost amavis[9850]: Found $gzip       at /bin/gzip
    Jun  8 11:44:26 localhost amavis[9850]: Found $bzip2      at /usr/bin/bzip2
    Jun  8 11:44:27 localhost amavis[9850]: No $lzop,         not using it
    Jun  8 11:44:27 localhost amavis[9850]: No $lha,          not using it
    Jun  8 11:44:27 localhost amavis[9850]: Found $unarj      at /usr/bin/arj
    Jun  8 11:44:27 localhost amavis[9850]: Found $uncompress at /bin/uncompress
    Jun  8 11:44:27 localhost amavis[9850]: No $unfreeze,     not using it
    Jun  8 11:44:27 localhost amavis[9850]: No $unrar,        not using it
    Jun  8 11:44:27 localhost amavis[9850]: Found $zoo        at /usr/bin/zoo
    Jun  8 11:44:27 localhost amavis[9850]: Found $cpio       at /bin/cpio
    Jun  8 11:44:27 localhost amavis[9850]: Using internal av scanner code for (primary) Clam Antivirus-clamd
    Jun  8 11:44:27 localhost amavis[9850]: Found secondary av scanner Clam Antivirus - clamscan at /usr/bin/clamscan
    I didn't see anything that looked out of the ordinary.. the only things that were mentioned in the .warn and .err files were disconnections from IMAP, saying i had logged off...
     
  17. falko

    falko Super Moderator ISPConfig Developer

    And spam filtering doesn't work at all? Is there nothing in the header of emails you receive that suggests that it went through SpamAssassin?
     
  18. heygazeebo

    heygazeebo New Member

    spam

    When i first installed it, i got this:

    Code:
    X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at localhos
    X-Spam-Status: Yes, hits=4.6 tagged_above=3.0 required=4.0 tests=AWL,
    	HELO_EQ_NO_DOT, HOST_EQ_D_D_D_D, HOST_MISMATCH_NET, HTML_90_100,
    	HTML_MESSAGE, IP_NOT_FRIENDLY, MSGID_FROM_MTA_ID
    X-Spam-Level: ****
    X-Spam-Flag: YES
    
    Now:

    Code:
    X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at localhost
    and thats it, its like its skipping over SpamAssassin Completely...

    I must have done somthing wrong somewhere or somthing, i am just at a total loss at the moment..
     
  19. falko

    falko Super Moderator ISPConfig Developer

    Try to remember what you did before it stopped working...
     
  20. heygazeebo

    heygazeebo New Member

    no idea


    Everything seemed to be working fine until i added the second how to, to add maildrop capabilities.. thats when spamassassin seems to have stopped working.

    I think i am just going to completely redo a second box and see what happens. I am at a loss right now, im just not sure what i have done wrong. I find it extremely strange that there are no messages in any long files anywhere, and it seems that no matter what i do or upgrade everything works except spamassassin. I'm not sure, i will try and put together a second box ASAP and see what happens.

    Thanks for all your help on this, i appreciate it.
     

Share This Page