1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice

Spamassassin 3.1.0 Issues

Discussion in 'Plesk for Linux - 8.x and Older' started by Traged1, Sep 19, 2005.

  1. Traged1

    Traged1 Guest

    0
     
    After upgrading to SA 3.1.0 PLESK 7.5.4:

    1. You cannot use PLESK to restart psa-spamassassin or it SA dies.

    2. psa-spamassassin quits periodically, need to use a cron job to keep spam filter running.

    3. spam filter training does not work anymore. After selecting the email to specify as spam or not spam, the page is returned with no email listed on it and the spam database stats are reset to 0,0,0

    4. If you do not toggle spamassassin off/on for each email address then emails will go missing and are not delivered.
     
  2. netamia

    netamia Guest

    0
     
    I got the same problem.

    I stille haven´t got any response from the support team. It's getting critical, since my customers is requesting the function.

    Anyone got a solution?
     
  3. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    What I have found is that you must stop both psa-spamassassin and spamassassin from the command line, then start psa-spamassassin only. It will call the spamd daemon into action as needed. But I too am having a problem with the training.
     
  4. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Any response from Plesk on this one netamia? It seems as though now spamassassin and/or psa-spamassassin are getting screwed up any time a new email address is created or an existing account is modified. I have to stop both from the command line and restart psa-spamassassin through the control panel.
     
  5. netamia

    netamia Guest

    0
     
    I had the support staff on my server yesterday.

    The problem is that we are using Debian Sarge/Testing. The system is not tested, and do not work under this ditstrib.

    I did a new testinstall on another server, with a stabel, and everything worked fine.

    The way to solve this is the downgrade to stable, or reinstall the server.
     
  6. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Doesn't help me much, mine is on CentOS 4. Guess I'll check with them myself.
     
  7. ShadowMan@

    ShadowMan@ Guest

    0
     
    Just to check - did any of you upgrade/update your spamassassin and psa-spamassassin from ART (atomicrocketturtle.com) ? If not, you may want to try that. Phoenixisp - I know you probably have, but wanted to check with the others as well.
     
  8. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    I sure did, but I may have messed up. I migrated servers from RH9 to CentOS4 and on this one in particular I had the Plesk SA license. To get around some of the problems I saw I installed ART's first, then the Plesk SA support, then removed spamassassin from ARTs qmail-scanner-queue.pl file. (otherwise it seems to override the Plesk settings for users) It just seems that when both run at the same time nothing works well.
     
  9. jamesyeeoc

    jamesyeeoc Guest

    0
     
    This was also from ART, right?
    Manually removed, or stopped SA, ran qmail-scanner-reconfigure, restart SA...?
     
  10. phoenixisp

    phoenixisp Silver Pleskian

    27
    57%
    Joined:
    Feb 2, 2002
    Messages:
    840
    Likes Received:
    0
    Stopped SA and psa-spamassassin, ran /usr/bin/qmail-scanner-rconfigure and then started SA from control panel.

    It works well until an email account is created or touched from the CP.
     
  11. vyacheslav

    vyacheslav Guest

    0
     
Loading...