• 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.

Spamassassin dies (or you stop it) and mail fails to be delivered

B

brooks

Guest
If you stop SA, or if it dies it appears that mail can be lost if you allow per user filter settings. Qmail happily accepts the mail but when it trys to hand it off to spamc for processing it fails to open the socket:

Aug 31 09:50:40 ds spamc[4465]: connect(AF_UNIX) to spamd /tmp/spamd_light.sock failed: Connection refused

which results in lost mail. To test this you can do cat a message through spamc using the same commands as are listed in the users .qmail file:

cat Maildir/cur/1157137453.28119.ds.server.com\:2\,S | /usr/local/psa/bin/psa-spamc -u [email protected] -U /tmp/spamd_light.sock -E

When spamd is not running the exit status is "98", when it is running the exit status is "0" (since this message isn't spam). Given the information in the spamc man page at:

http://spamassassin.apache.org/full/3.0.x/dist/doc/spamc.html

It looks like spamc should exit with a "0" status in the event of an error. Given the .qmail script that would allow the message to be delivered in the event of a failure, unfortunately it isn't working.

After looking at the spamc code it really doesn't make any sense that it exists with a "98", it's not even a valid exit code.

This server is running CentOS 3.8. Can anyone else confirm this on the same or on another OS?
 
Back
Top