• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

spamd error

G

Griffith

Guest
Anyone who knows what causes this error:
spamd[19252]: bad protocol: header error: (closed before headers)

I've got it on my severs after upgrading to psa-7.5.4... the error occurs at the exact same time on both servers... but not like a cron job that runs each hour... but normally I get the error twice within one hour...

Haven't found much in the logfiles either :p
 
It is a message which tells you that when psa-spamassassin restarts spamd, spamd fails which means your spam filter is not working.

I am having the same issue right now, and so far I am having no luck finding a solution, any one have any other info which could help?
 
It appears that the psa-spamassain is not configured properly to restart the new SA3 daemon.
 
I see this error message when we enable Watchdog monitoring for the Spamassassin service - that is with Spamassassin v2.63.

Do you get this as well? :rolleyes:

- Chris
 
We had installed Watchdog, but decided to remove the rpm as it was cuase many issues. However, now without watchdog intalled we are still unable to re-start psa-spamassassin via PLESK, we restart it from SSH with

# service psa-spamassassin restart

and it works.
 
You're not able to restart Spamassassin from within Plesk? Now that is strange... never seen that before. Did you report that to SWsoft as a bug?

RHN up2date released official support for Spamassassin 3.1 the other night so if you have any servers using up2date then watch out! Our RHES boxes ended up with Spamassassin 2.63 and 3.1 both installed at the same time. :eek:

- Chris
 
Thanks for the heads up, these are RHEL3 boxes, I will check for multiple versions of SA on them.
 
Back
Top