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

qmail-scanner and 8.0

It did until this latest "patch". Now qmail won't even recognise that spamassassin is there. Uninstalled qmail-scanner, spamassassin, and clamd, then reinstalled spamassassin through the pdater (which is screwed, btw), then again through the SSH installer, and qmail still won't recognise spamassassin.
Doing a complete mail reinstall now, hopefully it will bring things back.
Why is it I feel like the customers are the unwary beta testers of Plesk software?

*update* Yes, it does, with some tweaking.
qmail-scanner-1.25st (clamdscan: 0.88/1364. spamassassin: 3.1.0. perlscan: 1.25st

Essentially, I had to shut off qmail (to avoid the spam flood while everything was removed), uninstall qmail-scanner, spamassassin, and psa-spamassassin. Then yum install spamassassin, rpm -Uhv install psa-spamassassin, then install qmail-scanner. Then of course fire up qmail and hope that the impending wave of trash does not kill anything serious. For some reason, the Plesk updater breaks the intigration, but when I tried it without qmail-scanner installed, it broke everything anyway... something along the line is messed up, and given that the web-based updater continously times out while loading the confirmation page for me and others, I'm betting it's likely something at the sw-soft end.
 
Back
Top