The mail/p5-Mail-SpamAssassin port

p5-Mail-SpamAssassin-4.0.1 – mailfilter to identify and mark spam (cvsweb github mirror)


SpamAssassin is a mail filter to identify spam.

Using its rule base and optional network sources (DNS-based lists and
collaborative spam-tracking databases), it carries out a wide range of
heuristic tests on mail headers and body text to identify "spam", also
known as unsolicited commercial email.

Once identified, the mail can then be optionally tagged as spam for
later filtering using the user's own mail user-agent application.

SpamAssassin requires very little configuration; you do not need
to continually update it with details of your mail accounts, mailing
list memberships, etc.  It accomplishes filtering without this
knowledge, as much as possible.

Read ${PREFIX}/share/doc/SpamAssassin/README
for further installation instructions.

Or if you are in a hurry you can read:

The SpamAssassin Wiki is available at 
and contains up-to-date information on configuring SpamAssassin, and using
some of the more advanced features of it.
WWW: http://spamassassin.apache.org/


| Running ${PKGSTEM} on OpenBSD

This is just a mini-README to get you up and running if you are in a
hurry. Please go to http://spamassassin.apache.org/ for further information.

You can use spamassassin in many ways. Larger installations might use
it in combination with smtp-vilter, MailScanner or amavisd-new (all are
available in packages). A common method for a simple setup is to use
the spamc/spamd combination with procmail. To configure this, add
"spamassassin" to your "pkg_scripts" line in /etc/rc.conf.local.

(Use "${RCDIR}/spamassassin start" to start the daemon right away).

The final step: put this at the top of your .procmailrc.

-- cut here -- -- -- -- -- -- --
* < 256000
| spamc


* ^X-Spam-Status: Yes
caughtspam # This is the mailbox where all spam goes.
-- -- -- -- -- -- -- -- -- -- --

If you do not want to use procmail, please check the online docs at
http://spamassassin.apache.org/doc.html and the documentation for any
other software you use to implement spamassassin (MailScanner, etc).

The spam filtering is not perfect. But since the feedback is very
extensive you should be able to do what is necessary to get most spam

If you want to add custom settings to spamassassin you can create the
file ${SYSCONFDIR}/mail/spamassassin/local.cf . All possible options
are described in: man Mail::SpamAssassin::Conf


Giovanni Bechis


mail perl5

Build dependencies

Run dependencies

Test dependencies

Reverse dependencies