• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Question Manual SpamAssassin Configuration / Bayes

SonjaP

New Pleskian
I've been searching for the right place to put manual/custom additions to the SpamAssassin configurations.

Usually I would have put something a file called local.cf in /etc/spamassassin but this seems to be ignored.

Also I would like to know where the actual configuration that plesk uses is stored there is a file in /etc/spamassassin/ named plesk.local.cf, but it seems that everything I add in that or any other cf file gets ignored.

I want to turn on bayes filtering for my server and cannot seem to find the right place to put the line
use_bayes 1

I'd be grateful for any pointers.
 
Global configurations can be placed in: /etc/mail/spamassassin/local.cf and they shouldn't be ignored. Any of the Plesk managed settings will also get written to that file. Plesk itself stores the configurations in the DB and writes them to disk.

Global enabled
Tools & Settings -> Spam Filter -> Switch on server-wide SpamAssassin spam filtering checked
Stored in plesk DB and written to /etc/mail/spamassassin/local.cf

Per mailbox configurations
Tools & Settings -> Spam Filter -> Apply individual settings to spam filtering checked
Stored in plesk DB and written to /var/qmail/mailnames/<domain>/<mailname>/user_prefs

I hope this helps.
 
Thanks for getting back quickly. So local.cf will not be completely overwritten everytime Plesk updates?
I'll check out the file and try that then.
 
So local.cf will not be completely overwritten everytime Plesk updates?

No it won't nor will any of the custom rules you create in the /etc/mail/spamassassin folder. You may need to create a cron job to automate updating spamassassin's default rules or manually by executing
# sa-update -D
# service spamassassin restart

Cheers
 
ou may need to create a cron job to automate updating spamassassin's default rules

Actually you don't need to run this manually. Plesk already has its own cron that does this: `/etc/cron.daily/60sa-update`
 
Back
Top