Rev 1 | Rev 6 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed
Rev | Author | Line No. | Line |
---|---|---|---|
1 | magnus | 1 | ***************** |
2 | * CONFIGURATION * |
||
3 | ***************** |
||
4 | |||
5 | This version of the sa-exim package defaults to placing a configuration |
||
6 | sniplet in /etc/exim4/conf.d/. Depending on what you have answered to the |
||
7 | DebConf questions while configuring Exim4, the module will be loaded |
||
8 | automatically, or human intervention is required. |
||
9 | |||
10 | To find out what configurationfile Exim4 is using, issue: |
||
11 | |||
12 | $ exim4 -bV | tail -1 |
||
13 | Configuration file is /path/to/configfile |
||
14 | |||
15 | If /path/to/configfile shows: |
||
16 | |||
17 | - /etc/exim4/exim4.conf |
||
18 | You are using the 'monolithic' configuration file. |
||
19 | See the 'MONOLITHIC' section below. |
||
20 | |||
21 | - /var/lib/exim4/config.autogenerated |
||
22 | You are using the 'split' configuration file. |
||
23 | See the 'SPLIT' section below. |
||
24 | |||
25 | |||
26 | MONOLITHIC |
||
27 | ---------- |
||
28 | |||
29 | Use 'grep "local_scan_path" /etc/exim4/exim4.conf" to see if the sa-exim |
||
30 | line is included in the configuration. If grep returns something, check |
||
31 | if it matches the following line. If grep returns nothing, you have to |
||
32 | manually add the following line to the exim4.conf file and restart exim4. |
||
33 | |||
34 | local_scan_path = /usr/lib/exim4/local_scan/sa-exim.so |
||
35 | |||
36 | Change or add the line above and manually restart exim4 by issuing |
||
37 | 'invoke-rc.d exim4 restart' or '/etc/init.d/exim4 restart' as root. |
||
38 | |||
39 | |||
40 | SPLIT |
||
41 | ----- |
||
42 | |||
43 | Use 'grep "local_scan_path" /var/lib/exim4/config.autogenerated' to see |
||
44 | if the sa-exim line is included in the configuration. If grep returns |
||
45 | something, you're set and already using the sa-exim module. If grep |
||
46 | returns nothing, we need to figure out a few things: |
||
47 | |||
48 | Issue: |
||
49 | $ grep "use_split_config" /etc/exim4/update-exim4.conf.conf |
||
50 | dc_use_split_config='true' |
||
51 | |||
52 | If your result shows 'false' where mine shows 'true', but the check |
||
53 | earlier showed that you *are* in fact using the split configuration, |
||
54 | then you have to edit /etc/exim4/update-exim4.conf.conf by hand and |
||
55 | change the 'false' to 'true' and issue 'update-exim4.conf' as root. |
||
56 | Next, check again if the sa-exim module-line is included. It should. |
||
57 | If it still isn't: mail me. If it is, restart exim4 by issuing |
||
58 | 'invoke-rc.d exim4 restart' or '/etc/init.d/exim4 restart' as root. |
||
59 | |||
60 | Next, read all about greylisting and sa-exim: |
||
61 | |||
62 | *************** |
||
63 | * GREYLISTING * |
||
64 | *************** |
||
65 | Notes on greylisting with sa-exim. |
||
66 | |||
67 | If you use SpamAssassin 3.0 or better, you do not need to patch it, you |
||
68 | can just use the Greylisting module shipped with sa-exim. |
||
69 | The only thing you need to do to enable it, is to copy the 4 lines below |
||
70 | loadplugin in the greylisting README, and adjust the score if you wish (see |
||
71 | README.Greylisting for details) |
||
72 | |||
73 | |||
74 | If you use a version of SA older than 3.0, you will need to patch |
||
75 | spamassassin's sources to support greylisting. |
||
76 | |||
77 | There are two versions of the patches: |
||
78 | - /usr/share/doc/sa-exim/patches/SA-greylisting-2.4x.diff |
||
79 | This patch can be applied to versions 2.4x of SpamAssassin. Note |
||
80 | that this patch is not fully functional anymore, it is just left as |
||
81 | a template should you want to backport the current 2.6x patch. |
||
82 | That said, you really ought to upgrade SA to 2.6x or 3.x |
||
83 | |||
84 | - /usr/share/doc/sa-exim/patches/SA-greylisting-2.6.diff |
||
85 | This patch can be applied to versions 2.6x of SpamAssassin. |
||
86 | |||
87 | Please read README.Greylisting for more information on how to enable |
||
88 | this feature, and what further changes are needed. |
||
89 | Note that this configuration won't be supported in the future, and you |
||
90 | are encouraged to upgrade to SA 3.0 or better. |
||
91 | |||
92 | ************* |
||
93 | * BE WARNED * |
||
94 | ************* |
||
95 | |||
96 | By applying these patches, you change the sourcecode of SpamAssassin |
||
97 | (again, this is if you use a version of SpamAssassin earlier than 3.0) |
||
98 | This also means that when the SpamAssassin package gets upgraded, the |
||
99 | changes made by the patch are LOST. |
||
100 | This *MIGHT* cause your mail setup to break. It might be best to put |
||
101 | SpamAssassin on hold: |
||
102 | |||
103 | $ echo "spamassassin hold" | dpkg --set-selections |
||
104 | |||
105 | You can later set it to install again with: |
||
106 | |||
107 | $ echo "spamassassin install" | dpkg --set-selections |