• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Slow mail delivery when Spamassassin is enabled

thewolf

Regular Pleskian
Hi,

We're running Plesk 7.5.4 with all the latest hotfixes on Red Hat Enterprise Linux 4 Update 5.

We've noticed that after enabling Spamassassin ("Server wide settings" mode, we're not interested in "Personal settings" mode for now) mail delivery gets slower, e.g. even sending a test message to self will take about 30 seconds or so before it gets in the mailbox. If we disable Spamassassin mail delivery get's back to normal, that is almost immediate.

Also, when Spamassassin is enabled, we've noticed a lot of error messages in the /usr/local/psa/admin/var/log/maillog file, see below.

Please advice on how to speed up mail delivery with Spamassassin enabled and how to prevent the error messages in the log file.

Thanks.


Jun 7 11:34:00 myserver.mydomain.com spamd[28262]: spamd: got connection over /tmp/spamd_full.sock
Jun 7 11:34:00 myserver.mydomain.com spamd[28262]: spamd: handle_user unable to find user: '[email protected]'
Jun 7 11:34:00 myserver.mydomain.com spamd[28262]: spamd: processing message <[email protected]> for [email protected]:110
Jun 7 11:34:00 myserver.mydomain.com spamd[28262]: mkdir //.spamassassin: Permission denied at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin.pm line 1536
Jun 7 11:34:14 myserver.mydomain.com spamd[28262]: mkdir //.spamassassin: Permission denied at /usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin.pm line 1536
Jun 7 11:34:14 myserver.mydomain.com spamd[28262]: locker: safe_lock: cannot create tmp lockfile //.spamassassin/auto-whitelist.lock.myserver.mydomain.com.28262 for //.spamassassin/auto-whitelist.lock: No such file or directory
Jun 7 11:34:14 myserver.mydomain.com spamd[28262]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile //.spamassassin/auto-whitelist.lock.myserver.mydomain.com.28262 for //.spamassassin/auto-white
list.lock: No such file or directory
Jun 7 11:34:14 myserver.mydomain.com spamd[28262]: bayes: locker: safe_lock: cannot create tmp lockfile //.spamassassin/bayes.lock.myserver.mydomain.com.28262 for //.spamassassin/bayes.lock: No such file or directory
Jun 7 11:34:14 myserver.mydomain.com spamd[28262]: spamd: clean message (0.0/7.0) for [email protected]:110 in 14.0 seconds, 663 bytes.
Jun 7 11:34:14 myserver.mydomain.com spamd[28262]: spamd: result: . 0 - scantime=14.0,size=663,[email protected],uid=110,required_score=7.0,rhost=localhost,raddr=127.0.0.1,rport=/tmp/spamd_full.sock,mid=<[email protected]>,autol
earn=failed
Jun 7 11:34:14 myserver.mydomain.com spamd[28258]: prefork: child states: II
 
Back
Top