• 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 woes - headers only

P

psifx

Guest
FC3
PSA 7.5.4
PSA Spamassassin.
ClamAv : http://www.grafxsoftware.com/util/PLESK-HOWTO.txt


If a user has spamassassin enabled, then their incoming email is stripped and left as the following:

Return-Path: <[email protected]>
Delivered-To: [email protected]


I have narrowed it down to spamassassin as the culprit - although I cannot determine why.

They only thing recently performed on the server was plsek migration. Alhtough a disastorous event in itself, I do not see what the relationship could be????


The following extract shows spamassassin working ok (noting the existing bad protocol message)


Nov 2 20:10:34 hostname spamd[614]: server started on UNIX domain socket /tmp/spamd_full.sock (running version 3.0.4)
Nov 2 20:10:34 hostname spamd[614]: server successfully spawned child process, pid 618
Nov 2 20:10:34 hostname spamd[614]: server successfully spawned child process, pid 619
Nov 2 20:10:34 hostname spamd[614]: server successfully spawned child process, pid 620
Nov 2 20:10:34 hostname spamd[615]: server started on UNIX domain socket /tmp/spamd_light.sock (running version 3.0.4)
Nov 2 20:10:34 hostname spamd[615]: server successfully spawned child process, pid 622
Nov 2 20:10:34 hostname spamd[615]: server successfully spawned child process, pid 623
Nov 2 20:10:34 hostname spamd[615]: server successfully spawned child process, pid 624
Nov 2 20:10:34 hostname spamd[615]: server successfully spawned child process, pid 625
Nov 2 20:10:34 hostname spamd[614]: server successfully spawned child process, pid 621
Nov 2 20:10:34 hostname spamd[614]: server successfully spawned child process, pid 627
Nov 2 20:10:34 hostname spamd[617]: spamd starting
Nov 2 20:10:34 hostname spamd[618]: got connection over /tmp/spamd_full.sock
Nov 2 20:10:34 hostname spamd[618]: bad protocol: header error: (closed before headers)
Nov 2 20:10:34 hostname spamd[615]: server successfully spawned child process, pid 626
Nov 2 20:17:51 hostname spamd[619]: got connection over /tmp/spamd_full.sock
Nov 2 20:17:51 hostname spamd[619]: bad protocol: header error: (closed before headers)
Nov 2 20:17:51 hostname spamd[622]: got connection over /tmp/spamd_light.sock
Nov 2 20:17:51 hostname spamd[622]: bad protocol: header error: (closed before headers)
[root@hostname new]#


NOthing of interest in the messages file.....
 
psa-spamc

I also came across this problem just now, after updating my plesk configuration. Seems the problem in my case was that /usr/local/psa/bin/psa-spamc was no longer executable!

The error message in maillog was:


delivery 7200: success: /bin/sh:_line_1:_/usr/local/psa/bin/psa-spamc:_Permission_denied/Get_mailbox_size_error:_unable_to_get_size_of_subdir_in_mail_user_home_dir(please_report_about_to_development_group).//Get_mailbox_size_error:_unable_to_get_size_of_subdir_in_mail_user_home_dir(please_report_about_to_development_group).//did_1+0+2/did_0+0+1/

chmod a+x /usr/local/psa/bin/psa-spamc quickly solved the problem.

I sure wish Plesk would TEST their updates. :eek:
 
Back
Top