Rev 6 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 6 | Rev 46 | ||
|---|---|---|---|
| Line 112... | Line 112... | ||
| 112 | 112 | ||
| 113 | If you use SpamAssassin 3.0 or better, you do not need to patch it, you |
113 | If you use SpamAssassin 3.0 or better, you do not need to patch it, you |
| 114 | can just use the Greylisting module shipped with sa-exim. |
114 | can just use the Greylisting module shipped with sa-exim. |
| 115 | The only thing you need to do to enable it, is to copy the 4 lines below |
115 | The only thing you need to do to enable it, is to copy the 4 lines below |
| 116 | loadplugin in the greylisting README, and adjust the score if you wish (see |
116 | loadplugin in the greylisting README, and adjust the score if you wish (see |
| 117 | README.Greylisting for details) |
117 | README.Greylisting for details). |
| 118 | 118 | ||
| - | 119 | *********************************** |
|
| - | 120 | * PROBLEMS WITH BAYES AUTO-EXPIRY * |
|
| - | 121 | *********************************** |
|
| 119 | 122 | ||
| - | 123 | When scanning mail during the SMTP dialogue there is somewhat limited |
|
| - | 124 | time before the remote host gives up, even if they should wait for at |
|
| - | 125 | least ten minutes. To avoid Exim returning a temporary error status, |
|
| 120 | If you use a version of SA older than 3.0 (if you are, you really, |
126 | or the remote host giving up prematurely and in some cases for good, |
| 121 | really should upgrade!), you will need to patch spamassassin's sources |
127 | SA-Exim overrides Exim's timeout handler and accepts the message if |
| 122 | to support greylisting. |
128 | SpamAssassin takes too long, by default 240 seconds. |
| 123 | 129 | ||
| 124 | There are two versions of the patches: |
- | |
| 125 | - /usr/share/doc/sa-exim/patches/SA-greylisting-2.4x.diff |
130 | Using SpamAssassin's Bayesian learning module means that it will |
| 126 | This patch can be applied to versions 2.4x of SpamAssassin. Note |
131 | automatically expire old tokens when its database has grown too large. |
| 127 | that this patch is not fully functional anymore, it is just left as |
132 | That can take several minutes. If it takes too long, SA-Exim will |
| 128 | a template should you want to backport the current 2.6x patch. |
133 | abort it, meaning that SpamAssassin will run auto-expiry again next |
| 129 | That said, you really ought to upgrade SA to 2.6x or 3.x |
134 | time, and be aborted, and so on... |
| 130 | 135 | ||
| 131 | - /usr/share/doc/sa-exim/patches/SA-greylisting-2.6.diff |
- | |
| 132 | This patch can be applied to versions 2.6x of SpamAssassin. |
136 | If this happens, you have a few remedies: |
| 133 | 137 | ||
| 134 | Please read README.Greylisting for more information on how to enable |
- | |
| 135 | this feature, and what further changes are needed. |
- | |
| 136 | Note that this configuration won't be supported in the future, and you |
138 | 1) Set SAtimeout to a higher value in /etc/exim4/sa-exim.conf. |
| 137 | are encouraged to upgrade to SA 3.0 or better. |
- | |
| 138 | 139 | ||
| 139 | ************* |
- | |
| - | 140 | 2) Run sa-learn --force-expire periodically. How you run it depends on |
|
| 140 | * BE WARNED * |
141 | how you've configured SpamAssassin. Running it as Debian-exim may |
| 141 | ************* |
142 | be sufficient. |
| 142 | 143 | ||
| 143 | By applying these patches, you change the sourcecode of SpamAssassin |
- | |
| 144 | (again, this is if you use a version of SpamAssassin earlier than 3.0) |
- | |
| 145 | This also means that when the SpamAssassin package gets upgraded, the |
- | |
| 146 | changes made by the patch are LOST. |
- | |
| 147 | This *MIGHT* cause your mail setup to break. It might be best to put |
- | |
| 148 | SpamAssassin on hold: |
144 | 2 a) In addition, you can add |
| 149 | 145 | ||
| 150 | $ echo "spamassassin hold" | dpkg --set-selections |
146 | bayes_auto_expire 0 |
| 151 | 147 | ||
| - | 148 | to /etc/spamassassin/local.cf. This may not be a good idea if |
|
| - | 149 | SpamAssassin, for whatever reason, is also used as a more |
|
| - | 150 | traditional filter from e.g. .procmailrc, as all users will need to |
|
| 152 | You can later set it to install again with: |
151 | run sa-learn --force-expire then. |
| 153 | 152 | ||
| 154 | $ echo "spamassassin install" | dpkg --set-selections |
153 | 2 b) If you get a lot of mail, consider adding |
| 155 | 154 | ||
| - | 155 | bayes_learn_to_journal 1 |
|
| - | 156 | ||
| - | 157 | to local.cf. See the Mail::SpamAssassin::Conf(3) manual page for |
|
| - | 158 | more information. |
|
| 156 | 159 | ||
| 157 | ********************************** |
160 | ********************************** |
| 158 | * NOTICE ABOUT SPAMC CONFIG FILE * |
161 | * NOTICE ABOUT SPAMC CONFIG FILE * |
| 159 | ********************************** |
162 | ********************************** |
| 160 | 163 | ||
| 161 | Recent versions of spamc can read command-line parameters and switches |
164 | Recent versions of spamc can read command-line parameters and switches |
| 162 | from a configuration file called /etc/spamassassin/spamc.conf. If that |
165 | from a configuration file called /etc/spamassassin/spamc.conf. If that |
| 163 | file specifies conflicting options, it will prevent SA-Exim from |
166 | file specifies conflicting options, it will prevent SA-Exim from |
| 164 | working. For now, you'll have to make sure that it doesn't. |
167 | working. For now, you'll have to make sure that it doesn't. |
| - | 168 | ||
| - | 169 | -- Magnus Holmgren <holmgren@debian.org>, Tue, 24 Jun 2008 14:27:59 +0200 |
|