• 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 Absurd Problem

A

ajgomez

Guest
Hi,

I’m using Plesk 8 with Power Pack to host several domains for my clients. I’m offering SpamAssassin support as an added feature, but I’ve encountered a problem. If a client originally didn’t purchase the SpamAssassin feature and then decides to acquire it, his current mailboxes can’t be protected: the Spam Filter icon appears disabled and I haven’t found how to enable it. The only solution I’ve found is to delete the mailbox, create it again and now the Spam option is available. As you can imagine this can be difficult, especially if the user uses IMAP and has stored information, not to mention that this behavior is clearly absurd.

To clarify, I disable SpamAssassin for a domain by adding it to the Server-wide ignore list and enable them, by deleting them form this list. I’m not sure if there is another way to do this.

Any suggestions will be welcome.

Thanks
 
Back
Top