Spamassassin setup install#
Spamassassin setup full#

To allow amavisd-new to send them back to postfix, we need to add additional configuration.

The above configuration will send the emails to amavisd-new. Add a line with “-o content_filter=smtp-amavis::10024” directly underneath it. In the /etc/postfix/master.cf configuration file you will find a line for the smtpd. This is done by adding a line of parameters to the smtpd. Configuring PostfixĪmavisd-new needs to be integrated into postfix to receive the unfiltered emails from the postfix queue. If you have both repositories installed, make sure you have configured yum repository priorities with yum-plugin-priorities to avoid errors during installation and later system updates via “yum update”. Here you can find details about the error message and a temporary solution.

Spamassassin setup install#

yum install spamassassin amavisd-new clamav clamd pyzor perl-Mail-SPF perl-Mail-DKIM postgrey tmpwatch lzopĪt the time of writing, I have noticed problems while installing amavisd-new while having the “epel” repository installed, but the package is available from the rpmforge repository as well. They include Postgrey policy server implementing greylisting, amavisd-new as a wrapper between postfix and other components like Spamassasin as the spam filter, ClamAV as the virus scanner, and SPF and DKIM libraries.

The following commands will install the required components for this setup. After the emails are checked, they are sent back to postfix for delivery. There, the emails get checked for viruses and spam. I find the basic configuration above to be pretty solid, but of course you can tinker with the spam scores, filtering methods, or other settings if you like.In the setup described in this post, postfix passes incoming mail on to amavisd-new.

X-Spam-Status: No, score=0.3 required=5.0 etc. X-Spam-Checker-Version: SpamAssassin 3.3.2 () on You should see some entries like this if everything is working correctly:

Spamassassin setup full#

Try sending your accounts on the server a couple of emails from an external account (Gmail,, whatever) and check the full message headers after you’ve received them. Step 6: Start/restart everything and test This tells the client to pass its completed checks to the default MTA (mail transfer agent, /usr/sbin/sendmail, i.e., the Postfix-Sendmail compatibility interface) for handoff to the MDA (mail delivery agent, Dovecot) for delivery. OPTIONS='-create-prefs -max-children 5 -username spamd -helper-home-dir $ # Set the username, home directory and log file # Change to one to enable the spamd daemon Step 3: Edit the configuration settings at /etc/default/spamassassin Step 1: Install SpamAssassin and its client Let’s set up the SpamAssassin anti-spam system to eliminate all the junk mail. It works so well that everybody wants to use our new mail server to sell Viagra and cheap home loans. In our previous installment, we set up a Postfix and Dovecot mail server with virtual domains and users on Ubuntu 12.04. To install SpamAssassin on Ubuntu 15+, see the instructions here. Note: This article pertains to Ubuntu 12, and it applies to versions of Ubuntu or Debian that use init rather than systemd.