SpamAssassin 2.x introduced the spamc/ spamd combination to alleviate this issue. Starting SpamAssassin like this, with a decent amount of incoming e-mail, will increase I/O load and slows things down, fast. This process is expensive when you consider what this does: for each incoming e-mail, a perl interpreter starts and loads all of SpamAssassin’s perl code, including its thousands of rules. The spamc/spamd client/server combinationĪ normal SpamAssassin setup invokes the spamassassin command for each incoming e-mail that needs to be scanned. This depends completely on your setup, and more than likely there are plenty of other articles that describe the best way to setup what you want. This article does not discuss configuring your mail filtering system (i.e. These instructions can be adopted to other operating systems as well. Fortunately, there are several speed-ups and optimizations that can be applied to most SpamAssassin installations to speed up its rule processing, especially on Debian and Ubuntu GNU/Linux-based systems. Unfortunately, because there are so many different ways SpamAssassin can be used, SpamAssassin remains subject to many performance problems. # Otherwise, the init script will not be able to shut spamd down.SpamAssassin is one of the most-used spam filtering systems in use today. # -username option above, this needs to be writable by that user. # Where should spamd write its PID to file? If you use the -u or OPTIONS="-create-prefs -max-children 5 -username spamd -helper-home-dir /home/spamd -s /home/spamd/spamd.log" To setup after-queue content filter add the following line to the end of the file spamassassin unix - n n - pipe Now, Postfix will pipe the mail through Spamassassin. To do that, open Postfix config file using: nano /etc/postfix/master.cfįind the the line smtp inet n - smtpdĪnd add the following -o content_filter=spamassassin The emails still do not go through Spamassasin.
Start the Spamassassin daemon by using the following code: service spamassassin start
#UBUNTU SPAMASSASSIN FREE#
If you have a busy server, feel free to increase the max-children value. This specifies the username Spamassassin will run under as spamd, as well as add the home directory, create the log file, and limit the child processes that Spamassassin can run. Now create a variable named SAHOME with the Spamassassin home directory: SAHOME="/var/log/spamassassin/"įind and change the OPTIONS variable to OPTIONS="-create-prefs -max-children 2 -username spamd \ To enable automatic rule updates in order to get the latest spam filtering rules find the line CRON=0 and change it to CRON=1 To enable Spamassassin find the line ENABLED=0 and change it to ENABLED=1 Open the spamassassin config file using: nano /etc/default/spamassassin Then create the directory /var/log/spamassassin: mkdir /var/log/spamassassinĪnd change the ownership of the directory to spams: chown spamd:spamd /var/log/spamassassin Then add the user spamd with the home directory /var/log/spamassassin: useradd -g spamd -s /bin/false -d /var/log/spamassassin spamd To run Spamassassin you need to create a new user on your VPS.įirst add the group spams: groupadd spamd Once Spamassassin is installed, there are a few steps that has to be taken to make it fully functional.
#UBUNTU SPAMASSASSIN INSTALL#
Use apt-get to install Spamassassin and spamc. You can find instructions on that here Install Spamassassin Prerequisitesīefore installing Spamassassin, you need to install and setup a mail transfer agent such as Postfix on your virtual private server. It will save your mailbox from much unwanted spam emails. Spamassassin is a free and open-source mail filter written in Perl that is used to identify spam using a wide range of heuristic tests on mail headers and body text. You can use the search functionality at the top of the page to find a more recent version. If available, we strongly recommend using a guide written for the version of Ubuntu you are using. This guide might still be useful as a reference, but may not work on other Ubuntu releases. Reason: Ubuntu 12.04 reached end of life (EOL) on Apand no longer receives security patches or updates.
#UBUNTU SPAMASSASSIN UPGRADE#
0 kommentar(er)
