Could anyone point me to some documentation on enabling some sort of spam protection for my HestiaCP managed mail domains?
I installed spamassasin and got it running on the box where HestiaCP is installed but I I have not been able to find any guides/howtos on how to “link” it with HestiaCP.
Any help, much appreciated because the SPAM we’re getting is humongous!
As it always happens with many questions…
After I had posted my question I came across a document that gave a solution to running spamassassin with exim.
My Hestia installation actually uses exim4 so I had to look for some of the config files mentioned in the page and I am running Hestia CP on an Ubuntu instance on Amazon but the configuration described in the page above, worked after I had located and chnaged the configuration files mentioned.
I installed spamassassin for my distro:
sudo apt-get install spamassassin
I enabled spamd with, systemctl enable spamd
Instead of “/etc/exim/exim.conf” I edited /etc/exim4/exim4.conf.template which is what Hestia uses to auto-generate exim4s’ config file
I made the spamassassin changes mentioned to the file /etc/spamassassin/local.cf
I created the filters file /etc/exim4/filters with the described contents.
After I had made the changes described in the page above, I started to see messages that Spamassassin categorizes as SPAM appearing in my dovecot’s SPAM folder, rather than the standard Inbox folder.
Good luck, if you’re following these steps for your distro.
Thanks, dude. It’s good to know the right way.
I’m a developer not a sys admin but I’m kind of stretching my skills.
Currently adding Razor and Pyzor real-time checks to spamassassin, which I believe will give our mail server additional protection from spam.