openbsd-ports/mail/p5-Mail-SpamAssassin/pkg
sthen 91faa22c52 Where a program with an rc script _requires_ a certain command line
parameter to daemonize, move the parameter from daemon to daemon_flags,
so that the user cannot inadvertently prevent it from daemonizing by
adjusting the flags.

Discussed with ajacoutot and schwarze, this method was suggested
by schwarze@ as a simpler alternative to my diff. ok aja@
2011-12-17 22:01:12 +00:00
..
DESCR update to 3.3.1; thanks pea@ for testing and comments 2010-03-24 23:56:04 +00:00
PLIST - add p5-Mail-SPF-*|p5-Mail-SPF-Query-* as a run dep for SpamAssassin (two 2011-09-21 08:02:07 +00:00
README - add p5-Mail-SPF-*|p5-Mail-SPF-Query-* as a run dep for SpamAssassin (two 2011-09-21 08:02:07 +00:00
spamassassin.rc Where a program with an rc script _requires_ a certain command line 2011-12-17 22:01:12 +00:00

$OpenBSD: README,v 1.1 2011/09/21 08:02:07 sthen Exp $

+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} 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.

Configuration
=============
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, start
spamassassin from pkg_scripts as usual in /etc/rc.conf.local:

pkg_scripts="${pkg_scripts} spamassassin"

(Use "/etc/rc.d/spamassassin start" to start the daemon right away).

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

-- cut here -- -- -- -- -- -- --
:0fw
* < 256000
| spamc

:0e
{
EXITCODE=$?
}

:0:
* ^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).


Customizing
===========
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
filtered.

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