Page History

...

This is just a summary of the following websites. Go there for more detailed information.

http://flakshack.com/anti-spam/wiki/index.php (Detailed instructions for OpenBSD, RedHat, and Debian)

http://www.freespamfilter.org/www.geocities.com/scottlhenderson/spamfilter.html

http://www.dambrosioauto.com/razor_configijs.si/software/amavisd/README.postfix.html

http://www.ijs.si/software/amavisd/#faq-spam

http://www.xmissionijs.comsi/software/~jmcrc/index.htmlamavisd/amavisd-new-docs.html

http://www200.pair.com/mecham/spam/

This document describes the configuration for sitewide use of SpamAssassin with Amavis and Razor. The distribution used is SuSE Linux 9.0. If you use something else, some options may be different. For example Amavis may run as user amavis, not vscan and the path to the Amavis spool directory may be
/var/amavis not /var/spool/amavis

Postfix Configuration

...

This section describes how to configure Postfix to use amavisd-new as an after-queue content filter (see the \[http://www.postfix.org/FILTER_README .html FILTER_README file\] that comes with your version of Postfix).

First, a few services must be defined in master.cf. The first service will setup an extra SMTP listener on a different port (10025 in this example). It will be used for the reinjection of mail back into Postfix. By unsetting the content_filter parameter, content filtering will be disabled for incoming mail on this port. This avoids loops.

...

No Format
content_filter = smtp-amavis:[localhost127.0.0.1]:10026

In this case, amavisd-new is running on the same host as Postfix, but it can be any host. With brackets surrounding the hostname, MX lookups of the hostname are suppressed. They are also necessary when specifying bare IP addresses instead of a hostnamehostnames. MX records in DNS can be used to create simple load-balancing and fallback configurations.

Wiki MarkupThis simple setup will cause address rewriting both before and after the content filter. For most configurations this is not only unnecessary, but configurations with virtual aliases of the form a \-> a,b will cause duplicate mail to be delivered. Virtual rewriting must be turned off either before or after the content filter. How this is done is, again, documented in the \[http://www.postfix.org/FILTER_README.html FILTER_README file\] of your Postfixbut will cause duplicate mail to be delivered in configurations with virtual aliases of the form a -> a,b. Virtual rewriting must be turned off either before or after the content filter. How this is done is, again, documented in Postfix's FILTER_README file doc.

Amavis configuration

Amavis is just used for spam detection, not virus protection. See the options below.

...

We only want spam protection and no virus scanning, so this will disable virus scanning for all
your domains.

• $mailfrom_notify_spamadmin . . .
  Change
  "spam.police@$mydomain"; to "postmaster@domain1.com";

...

Here, remove the leading # symbol. (And make sure you have an emailbox a mailbox for this address on a destination server -
This is where you will review quarantined emails, and will forward on any "false positives" to the proper recipientrecipients.)
*Alternative:* Instead of delivering the spam to an emailbox a mailbox on the internal server, drop it into a folder right on the spamfilter. To do that, comment out the "spam_quarantine_to" line above that references the email address, and instead select and indicate a folder name for the value "spam_quarantine_to". (Read the comments in this area of amavisd.conf for more info.)

...