• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue SpamAssassin is not scanning server-wide

Hello,

I got a problem with server-wide SpamAssassin configured by Plesk. System:
Ubuntu 18.04.5 LTS
Plesk Obsidian Version 18.0.29 Update #3

After switching back from "Apply individual settings" to "server-wide SpamAssassin" the SpamAssassin is no more scanning Mails:

Excerpts from mail.log:

Before switching to server-wide:
Sep 10 12:49:52 cloudserver2 postfix/smtpd[4095]: connect from email.example.com[85.214.xxx.205]
Sep 10 12:49:52 cloudserver2 postfix/smtpd[4095]: 827242028C: client=email.example.com[85.214.xxx.205]
Sep 10 12:49:52 cloudserver2 postfix/cleanup[4098]: 827242028C: message-id=<[email protected]>
Sep 10 12:49:52 cloudserver2 check-quota[4101]: Starting the check-quota filter...
Sep 10 12:49:52 cloudserver2 psa-pc-remote[1529]: SKIP during call 'check-quota' handler
Sep 10 12:49:52 cloudserver2 postfix/qmgr[2827]: 827242028C: from=<[email protected]>, size=693, nrcpt=2 (queue active)
Sep 10 12:49:52 cloudserver2 postfix/smtpd[4095]: disconnect from email.example.com[85.214.xxx.205] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1
Sep 10 12:49:52 cloudserver2 postfix-local[4105]: postfix-local: from=[email protected], to=[email protected], dirname=/var/qmail/m
Sep 10 12:49:52 cloudserver2 dk_check[4106]: Starting the dk_check filter...
Sep 10 12:49:52 cloudserver2 dk_check[4106]: DKIM verify result: DKIM Feed: No signature
Sep 10 12:49:52 cloudserver2 postfix-local[4104]: PASS during call 'dd52-domainkeys' handler
Sep 10 12:49:52 cloudserver2 spamassassin[4107]: Starting the spamassassin filter...
Sep 10 12:49:52 cloudserver2 spamd[4027]: spamd: connection from ::1 [::1]:36194 to port 783, fd 5
Sep 10 12:49:52 cloudserver2 spamd[4027]: spamd: using default config for [email protected]: /var/qmail/mailnames/xyzxyzxyz.de/sysadmin
Sep 10 12:49:52 cloudserver2 spamd[4027]: spamd: processing message <[email protected]> for [email protected]:30
Sep 10 12:49:53 cloudserver2 spamd[4027]: spamd: identified spam (1000.0/7.0) for [email protected]:30 in 0.4 seconds, 790 bytes.
Sep 10 12:49:53 cloudserver2 spamd[4027]: spamd: result: Y 1000 - GTUBE,RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_NONE scantime=0.4,size=790,user=sysadm
Sep 10 12:49:53 cloudserver2 postfix-local[4105]: PASS during call 'spam' handler
[...]

So good. Now configuring SpamAssassin to "server-wide" (no other options are touched) via Plesk. Note that spamd is successfully restarted:

Sep 10 12:53:23 cloudserver2 spamd[4024]: spamd: server killed by SIGTERM, shutting down
Sep 10 12:53:24 cloudserver2 spamd[4503]: logger: removing stderr method
Sep 10 12:53:26 cloudserver2 postfix/smtpd[4095]: connect from unknown[185.234.219.227]
[...]
Sep 10 12:53:27 cloudserver2 postfix/smtpd[4095]: disconnect from unknown[185.234.219.227] ehlo=1 auth=0/1 quit=1 commands=2/3
Sep 10 12:53:29 cloudserver2 spamd[4525]: zoom: able to use 330/346 'body_0' compiled rules (95.375%)
Sep 10 12:53:32 cloudserver2 spamd[4525]: spamd: server started on IO::Socket::IP [::1]:783, IO::Socket::IP [127.0.0.1]:783 (running version 3.4.2)
Sep 10 12:53:32 cloudserver2 spamd[4525]: spamd: server pid: 4525
Sep 10 12:53:32 cloudserver2 spamd[4525]: spamd: server successfully spawned child process, pid 4529
Sep 10 12:53:32 cloudserver2 spamd[4525]: spamd: server successfully spawned child process, pid 4531
Sep 10 12:53:32 cloudserver2 spamd[4525]: prefork: child states: IS
Sep 10 12:53:32 cloudserver2 spamd[4525]: prefork: child states: II
Sep 10 12:53:32 cloudserver2 spamd[4525]: spamd: server killed by SIGTERM, shutting down
Sep 10 12:53:32 cloudserver2 spamd[4553]: logger: removing stderr method
Sep 10 12:53:37 cloudserver2 spamd[4569]: zoom: able to use 330/346 'body_0' compiled rules (95.375%)
Sep 10 12:53:40 cloudserver2 spamd[4569]: spamd: server started on IO::Socket::IP [::1]:783, IO::Socket::IP [127.0.0.1]:783 (running version 3.4.2)
Sep 10 12:53:40 cloudserver2 spamd[4569]: spamd: server pid: 4569
Sep 10 12:53:40 cloudserver2 spamd[4569]: spamd: server successfully spawned child process, pid 4576
Sep 10 12:53:40 cloudserver2 spamd[4569]: spamd: server successfully spawned child process, pid 4578
Sep 10 12:53:40 cloudserver2 spamd[4569]: prefork: child states: IS
Sep 10 12:53:40 cloudserver2 spamd[4569]: prefork: child states: II
Sep 10 12:53:57 cloudserver2 plesk_saslauthd[4527]: select timeout, exiting

... but now the SpamAssassin is not working any more:

Sep 10 12:53:59 cloudserver2 postfix/smtpd[4095]: connect from email.example.com[85.214.xxx.205]
Sep 10 12:54:00 cloudserver2 postfix/smtpd[4095]: 0AAD52028C: client=email.example.com[85.214.xxx.205]
Sep 10 12:54:00 cloudserver2 postfix/cleanup[4583]: 0AAD52028C: message-id=<[email protected]>
Sep 10 12:54:00 cloudserver2 check-quota[4587]: Starting the check-quota filter...
Sep 10 12:54:00 cloudserver2 psa-pc-remote[1529]: SKIP during call 'check-quota' handler
Sep 10 12:54:00 cloudserver2 postfix/qmgr[2827]: 0AAD52028C: from=<[email protected]>, size=693, nrcpt=2 (queue active)
Sep 10 12:54:00 cloudserver2 postfix/smtpd[4095]: disconnect from email.example.com[85.214.xxx.205] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1
Sep 10 12:54:00 cloudserver2 postfix-local[4591]: postfix-local: from=[email protected], to=[email protected], dirname=/var/qmail/m
Sep 10 12:54:00 cloudserver2 dk_check[4592]: Starting the dk_check filter...
Sep 10 12:54:00 cloudserver2 dk_check[4593]: Starting the dk_check filter...
Sep 10 12:54:00 cloudserver2 dk_check[4592]: DKIM verify result: DKIM Feed: No signature
Sep 10 12:54:00 cloudserver2 dk_check[4593]: DKIM verify result: DKIM Feed: No signature
Sep 10 12:54:00 cloudserver2 postfix-local[4590]: PASS during call 'dd52-domainkeys' handler
Sep 10 12:54:00 cloudserver2 postfix-local[4591]: PASS during call 'dd52-domainkeys' handler
Sep 10 12:54:00 cloudserver2 dovecot: service=lda, user=[email protected], ip=[]. msgid=<[email protected]>: sav
Sep 10 12:54:00 cloudserver2 check-quota[4602]: Starting the check-quota filter...
Sep 10 12:54:00 cloudserver2 plesk sendmail[4601]: handlers_stderr: SKIP
Sep 10 12:54:00 cloudserver2 plesk sendmail[4601]: SKIP during call 'check-quota' handler
Sep 10 12:54:00 cloudserver2 postfix/pickup[2826]: 5D506202FA: uid=30 from=<SRS0=KNWc=CT=email.example.com=[email protected]>
Sep 10 12:54:00 cloudserver2 postfix/cleanup[4583]: 5D506202FA: message-id=<[email protected]>
Sep 10 12:54:00 cloudserver2 postfix/pipe[4589]: 0AAD52028C: to=<[email protected]>, relay=plesk_virtual, delay=0.35, delays=0.1/0.01/0/0.24
Sep 10 12:54:00 cloudserver2 postfix/qmgr[2827]: 0AAD52028C: removed

The service SpamAssassin and postfix are running fine and a Server Reboot didn't change anything.
If I switch back, SA is working like before.

Any idea what is going wrong here and how to fix it - or how to analyze that problem? I'm familar with the Linux Console (SSH) but configurations are only made with plesk to prevent me about such problems.
Thanks for any tipps and hints.

Greetings from Germany :)
 
I can confirm the same issue on my Plesk server.
If I have the checkbox "apply server-wide spam-settings" enabled, checking through the CLI with "plesk bin spamassassin --info [email protected]" shows:
Bash:
Spam filter configuration for [email protected].

Status                           false
The score that a message must
receive to qualify as spam
What to do with spam mail
Add the following text to the    true
beginning of subject of each
message recognized as spam
Modify spam mail subject text.........
As well as sent mail to this mailbox does not contain any X-Spamassassin-Headers.

Switching back to individual settings (and setting up the same settings for more than 50 mailboxes.......) fixes the issue.
I also tried uninstalling and reinstalling spamassassin, without success.
Seems to be a bug in Plesk?
 
Back
Top