114,46 → 114,49 |
can just use the Greylisting module shipped with sa-exim. |
The only thing you need to do to enable it, is to copy the 4 lines below |
loadplugin in the greylisting README, and adjust the score if you wish (see |
README.Greylisting for details) |
README.Greylisting for details). |
|
*********************************** |
* PROBLEMS WITH BAYES AUTO-EXPIRY * |
*********************************** |
|
If you use a version of SA older than 3.0 (if you are, you really, |
really should upgrade!), you will need to patch spamassassin's sources |
to support greylisting. |
When scanning mail during the SMTP dialogue there is somewhat limited |
time before the remote host gives up, even if they should wait for at |
least ten minutes. To avoid Exim returning a temporary error status, |
or the remote host giving up prematurely and in some cases for good, |
SA-Exim overrides Exim's timeout handler and accepts the message if |
SpamAssassin takes too long, by default 240 seconds. |
|
There are two versions of the patches: |
- /usr/share/doc/sa-exim/patches/SA-greylisting-2.4x.diff |
This patch can be applied to versions 2.4x of SpamAssassin. Note |
that this patch is not fully functional anymore, it is just left as |
a template should you want to backport the current 2.6x patch. |
That said, you really ought to upgrade SA to 2.6x or 3.x |
Using SpamAssassin's Bayesian learning module means that it will |
automatically expire old tokens when its database has grown too large. |
That can take several minutes. If it takes too long, SA-Exim will |
abort it, meaning that SpamAssassin will run auto-expiry again next |
time, and be aborted, and so on... |
|
- /usr/share/doc/sa-exim/patches/SA-greylisting-2.6.diff |
This patch can be applied to versions 2.6x of SpamAssassin. |
If this happens, you have a few remedies: |
|
Please read README.Greylisting for more information on how to enable |
this feature, and what further changes are needed. |
Note that this configuration won't be supported in the future, and you |
are encouraged to upgrade to SA 3.0 or better. |
1) Set SAtimeout to a higher value in /etc/exim4/sa-exim.conf. |
|
************* |
* BE WARNED * |
************* |
2) Run sa-learn --force-expire periodically. How you run it depends on |
how you've configured SpamAssassin. Running it as Debian-exim may |
be sufficient. |
|
By applying these patches, you change the sourcecode of SpamAssassin |
(again, this is if you use a version of SpamAssassin earlier than 3.0) |
This also means that when the SpamAssassin package gets upgraded, the |
changes made by the patch are LOST. |
This *MIGHT* cause your mail setup to break. It might be best to put |
SpamAssassin on hold: |
2 a) In addition, you can add |
|
$ echo "spamassassin hold" | dpkg --set-selections |
bayes_auto_expire 0 |
|
You can later set it to install again with: |
to /etc/spamassassin/local.cf. This may not be a good idea if |
SpamAssassin, for whatever reason, is also used as a more |
traditional filter from e.g. .procmailrc, as all users will need to |
run sa-learn --force-expire then. |
|
$ echo "spamassassin install" | dpkg --set-selections |
2 b) If you get a lot of mail, consider adding |
|
bayes_learn_to_journal 1 |
|
to local.cf. See the Mail::SpamAssassin::Conf(3) manual page for |
more information. |
|
********************************** |
* NOTICE ABOUT SPAMC CONFIG FILE * |
********************************** |
162,3 → 165,5 |
from a configuration file called /etc/spamassassin/spamc.conf. If that |
file specifies conflicting options, it will prevent SA-Exim from |
working. For now, you'll have to make sure that it doesn't. |
|
-- Magnus Holmgren <holmgren@debian.org>, Tue, 24 Jun 2008 14:27:59 +0200 |