Skip to content

Tackle spam with SpamAssassin on CentOS 7 & Postfix

Published: | 2 min read

Table of contents

Open Table of contents


On some cases you need to maintain your own mail server, for example for development purposes. This article is another quick technical walkthrough, on how to install SpamAssassin to accompany Postfix on CentOS 7 Linux platform.


The following assumptions are made:

You can check the Postfix version with

postconf -d | grep mail_version

And the SpamAssassin version with

spamassassin -V

Install and configure SpamAssassin

Install SpamAssassin

yum update
yum install spamassassin

Configure SpamAssassin by editing the configuration file

vi /etc/mail/spamassassin/

Uncomment, or insert the following:

required_hits 5.0
report_safe 0
required_score 5
rewrite_header Subject [SPAM]

Add new user to run SpamAssassin. ** -g = add to group spamd, -s /bin/false = No shell (does not mean, cannot access via SSH!), -d = home dir **

groupadd spamd
useradd -g spamd -s /bin/false -d /var/log/spamassassin spamd
chown spamd:spamd /var/log/spamassassin

Enable (if not automatically enabled) and start the service

systemctl enable spamassassin
systemctl start spamassassin

Update the spam rules by running


Configure Postfix to use SpamAssassin

Configure the Postfix by editing the configuration file.

Open conf in editor

vi /etc/postfix/

On the top, replace

smtp      inet  n       -       n       -       -       smtpd


smtp      inet  n       -       n       -       -       smtpd -o content_filter=spamassassin

Add this as the last line:

spamassassin unix - n n - - pipe flags=R user=spamd argv=/usr/bin/spamc -e /usr/sbin/sendmail -oi -f ${sender} ${recipient}

Restart Postfix

systemctl restart postfix

Test the spam detection

Test, by sending an email outside of this mail server.

Title does not matter, enter XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34Xas the message body.

If all went well, your inbox should now have an email with a title beginning with [SPAM].

You shoud check the logs, what just happened, by querying journal with:

journalctl | grep spam

Automate the spam definition updates

Automatic definition updates with cron (run every night at 01.00)

00 01 * * * root /bin/sa-update && /sbin/service spamassassin restart

Check, that it has been run:

grep "sa-update" /var/log/cron

There we go, most spam should now be marked as such.

Further reading

SpamAssassin docs.