• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Plesk 7.5.1 SpamAssassin problems

T

Troy

Guest
Against our better judgement, we attempted to upgrade from 7.0.3 to 7.5.1 last night. What a nightmare that was!

We're back up and running now, but for the life of me I cannot get SpamAssassin working correctly.

It wasn't working at all on 7.0.3, stopped as soon as we upgraded from 7.0.2. It's at least running on 7.5.1, but cannot be customized. It seem to be stuck at a threshold of 5, no matter what settings are specified at the mailbox level.

We've tried various combinations of server wide settings and personal settings, one on the other off, vice versa, and both on at the same time, various thesholds, etc.

Server wide blacklist doesn't seem to work at all, at least not when personal settings are enabled.

And no matter what I try, the subject is never rewritten.

What is up with this?
 
Have u tried editing the spamassassin file manually?

I didnt have this problem but if I did here is what I would do. Try editing it manually , then restart the spamassassin service within Services management and then see if the server wide settings kick back in.

Btw,
How do you get SpamAssassin to autolearn. This part is puzzling me.

Peace,
Joe
 
Back
Top