• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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