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

SpamAssasin On All Email Accounts

T

tomyknoker@

Guest
Hi All,

When I set up a new email account in Plesk I have to manually turn on SpamAssassin on for each account... Is there anyway to make this default to be on for all email accounts I create?
 
Originally posted by tomyknoker
Hi All,

When I set up a new email account in Plesk I have to manually turn on SpamAssassin on for each account... Is there anyway to make this default to be on for all email accounts I create?

It is possible to do that with help of Event Manager: Plesk admin CP -> Event Manager -> Add New Event Handler:

For example:

Event: Mail name created
Priority: High
User: root
Command:/usr/local/psa/bin/spamassassin.sh --update <new_mailname> -status true

It should work. Actually, Event Manager quite good feature for such sort of customization. Suggest you to check all available options for Event Manager. Probably you will find something useful for you except Spamassassin enabling.
 
Thanks Francuz! Do you know how I would make it so that when I create a new email account, it automatically creates a [email protected] aliases on the root?
 
Hmmm also noticed that works now, when I create a new user they have the SpamAssassin enabled, But in the email users permissions, they don't have control over the Spam Filter management... Does a client have control over it somewhere else that you know of?
 
Back
Top