• Spam Assassin  http://spamassassin.apache.org  This is a widely respected spam detection system, which works in various ways, including by reference to remote blacklists etc. and Bayesian recognition of spam based on the contents of the user's personal spam pit.
  
  
• The Anomy Sanitizer  http://mailtools.anomy.net Not actually a virus scanner, in terms of identifying specific viruses (which would require constant updates to its filtering rules) but a program to eliminate problems in attachments such as Javascript in HTML emails, and to rename or delete executable files and to do other things which generally render them less harmful.  (This is my rough summary - see the web page - for instance it can call a virus scanner.)  I have it "defang" various suspect HTML elements, and "drop" attached files which are executable. In April 2008, this software was last updated in 2006.  I have found it useful, and I am not sure what other programs do the same job.

http://advosys.ca/papers/postfix-filtering.html .

The Postfix configuration changes required for running the Advosys script for these two programs are entirely separate from how Postfix is configured to deliver messages with Maildrop.  However, this leads to them running on outgoing mail as well, not just mail to be delivered to local users' mailboxes.  (Actually, the script becomes part of Postfix's smtp program which also handles the messages arriving from local clients via the line entering the bottom right of the Postfix box above.)  Advosys solve this by running two instances of Postfix, with the first one doing the virus/spam filtering as usual and the second one responding to a second IP address purely for SMTP outgoing messages from local mail clients - therefore requiring all the clients be reconfigured.  For my own purposes, I think a better approach is to put Anomy Sanitizer and Spam Assassin in the local delivery section of Postfix, just before Maildrop.   See my separate page, from the parent directory for how I did this - running them from within Maildrop.  However, Advosys.ca have a lot of experience with large mail systems, for companies and educational institutions, and there are good reasons why they run two instances of Postfix, and do other things to improve efficiency.  For instance, their clients may want to filter for spam and viruses on all incoming email, but only filter for viruses on outgoing mail.  This is not because they are spammers, but because spam detection is an imperfect science.

• Spam-Marginal.  Those with a spam score marginally above my chosen threshold - below some marginally higher threshold.
• Spam.  Those scoring above the higher threshold.  It is exceedingly unlikely that there will be a false positive in this lot, so I generally don't manually check the contents of this mailbox.

To the client they appear as a tree of directories and sub-directories, such as:

    Inbox
     |
     |--aaa
     |
     |--Trash
     |
     |--xxx
     |
     |--yyy
         |
         zzz
 

Physically in the file system, they are as follows, not counting each directory's three subdirectories and two or three files which Courier IMAP puts
in each one.

/home/blah/Maildir/.aaa
/home/blah/Maildir/.Trash
/home/blah/Maildir/.yyy
/home/blah/Maildir/.yyy.zzz

1. Storage limits on the server's hard drive.
2. Time taken to copy and tar-gzip for backup purposes.
3. Total size of the entire backup file.
   

maildir-report-3.sh.txt     maildir-report-3.sh.txt.gz 

~/.spamassassin/user_prefs

• MIME::Base64
• MIME::QuotedPrint

This is my file /usr/local/anomy/anomy.conf.  Note, the file can have any name, provided it is given to the program when it is run, as I do in the .mailfilter file, as noted below.  

This is a totally freshly written config file, but with the business end of it based on the work of Advosys.ca.  

Here, I have explicitly set every option documented at: http://mailtools.anomy.net/sanitizer.html on 31 May 2003, but that page does not mention all features.  It includes:  "WARNING: This document is outdated! Please refer to the CHANGELOG for up-to-date information on new features."  Indeed the CHANGELOG at: http://mailtools.anomy.net/CHANGELOG.sanitizer.txt there is a new feature: feat_mime_files which is also explained in a mailing list message from Bjarni Einarsson on 29 May 2003.

I have also tried to document the meaning of different values for the various options, and indicate the default, in a way which is clearer than on this page.  However, I am a beginner with this program, there is lots I don't understand - so please do not consider my comments, or the values I have chosen, as being necessarily wise.

Added the following options to configure the HTML cleaner (all are off
by default):

   feat_html_noexe     Disallow links to executables
   feat_html_unknown   Allow unknown HTML tags
   feat_html_paranoid  Paranoid HTML Cleaner mode, bans all src= links
                           and enables feat_html_noexe paranoia as well.

Made the file-name/MIME-type sanity checks configurable (default on)
via. the feat_sane_names variable.  Set to 0 to disable.

This file is available here as: anomy.conf.txt and anomy.conf.txt.gz .

# Configuration file for Anomy Sanitizer
#
# Based on a file from Advosys Consulting Inc., Ottawa
# http://advosys.ca/papers/postfix-filtering.html
#
# Works with Anomy Sanitizer revision 1.60
#
# Doctored by Robin Whittle   http://www.firstpr.com.au/web-mail/
#
# All config items are set explicitly, with their defaults marked "*",
# as per http://mailtools.anomy.net/sanitizer.html on 2003-05-31.


# Warn user about unscanned parts, etc.
#   0  Don't warn. 
# * 1  Warn.
#
feat_verbose = 1   


# Insert log in the message itself.
#   0 Off.
# * 1 Maybe.
#   2 Force.
#
feat_log_inline = 0


# Log to STDERR:
#   0  Don't log.
# * 1  Log.
#
feat_log_stderr = 1       


# XML format for logs.
# * 0  Off.
#   1  On.
#
feat_log_xml = 0


# Include trace info from logs.
# * 0  Off.
#   1  Include.
#
feat_log_trace = 0       


# Add scratch space to part headers.
# * 0  Off.
#   1  Add.
#
feat_log_after = 0


# Enable filename-based policy decisions.
#   0  Off.
# * 1  Enable. 
#
feat_files = 1


# Force all parts (except text/html parts) to have file names.
# * 0  Don't force.
#   1  Force.
#
feat_force_name = 0


# Replace all boundary strings with our own
# NOTE:  Always breaks PGP/MIME messages!
# * 0  Off.
#   1  Replace.
#
feat_boundaries = 0


# Protect against buffer overflows and null values.
#   0  Off.
# * 1  Protect.
#
feat_lengths = 1


# Defang incoming shell scripts.
#   0  Off.
# * 1  On.
#
feat_scripts = 1


# Defang active HTML content - Javascript and more.
#   0  Off.
# * 1  Defang.
#
feat_html = 1


# Allow Web-bugs.
# * 0  Allow.
#   1  Disallow.
#
feat_webbugs = 0


# Scan PGP signed message parts.  See custom message below.
# * 0  Don't scan.  
#   1  Scan
#
feat_trust_pgp = 0


# Sanitize inline uuencoded files.  Bjarni R. Einarsson wrote:
# This should always be set to 1, or people will be able to send you
# uuencoded viruses/attachments and they'll slip by the sanitizer.
# Also, if this is 0 then uuencoded attachments won't be detected as
# such, and will instead get treated as text or HTML - and will get
# corrupted by the HTML cleaner.
#
#   0  Don't sanitize.
# * 1  Sanitize.
#
feat_uuencoded = 1


# Sanitize forwarded messages.
#   0  Don't sanitize.
# * 1  Sanitize.
#
feat_forwards = 1


# This isn't a test-case configuration.
# * 0  Not testing.
#   1  Test case.
#
feat_testing = 0


# Fix invalid MIME, if possible.
#   0  Don't fix.
# * 1  Fix.
#
feat_fixmime = 1


# Paranoia about MIME headers etc.
# * 0  Don't be excessively paraniod.
#   1  ???
#
feat_paranoid = 0


# Scoring and exit status.
# Any message requring this many modifications
# will cause the sanitizer to return a non-zero
# exit code after processing the entire message.
#
# eg. the default: score_bad = 100
#
# Here, this is disabled:
#
score_bad = 0  
       


# Depth of recursion when including config files.
# Default = 5. I left it alone.

#
#  max_conf_recursions = 5


# Temp file and quarantine directory.  This must exist
# and be writable by the user running the sanitizer.
# Temporary or saved files are created using this template.
#
#   file_name_tpl = /var/quarantine/att-$F-$T.$$$
#
# An attachment named "dude.txt" might be saved as
#
#&nbs