Rev 27 | Details | Compare with Previous | Last modification | View Log | RSS feed
Rev | Author | Line No. | Line |
---|---|---|---|
67 | magnus | 1 | sa-exim (4.2.1-14) unstable; urgency=low |
2 | |||
3 | If you are using sa-exim's greylisting plugin for SpamAssassin you may |
||
4 | want to review your setup. Previously the documentation recommended |
||
5 | running spamd as the "nobody" user. This is not a very good |
||
6 | recommendation as nobody/nogroup should be completely unprivileged and |
||
7 | thus not own anything. This version won't change the ownership of any |
||
8 | directories or files and won't try to fix your SpamAssassin |
||
9 | configuration, but if you haven't modified /etc/cron.d/greylistclean |
||
10 | it will be changed to run greylistclean as "Debian-exim", which won't |
||
11 | work if the greylisting data is owned by nobody:nogroup. |
||
12 | |||
13 | -- Magnus Holmgren <holmgren@debian.org> Sun, 18 Sep 2011 23:19:53 +0200 |
||
14 | |||
26 | magnus | 15 | sa-exim (4.2.1-8) unstable; urgency=medium |
16 | |||
17 | * Since version 4.67-1, exim4 only exports those symbols that are part |
||
18 | of the official local_scan API. Unfortunately, sa-exim has all along |
||
19 | cheated and declared some "extern" variables by itself, something that |
||
20 | no longer works. For one of these, body_linecount, no workaround is |
||
21 | currently possible, meaning that it will not be updated if the message |
||
22 | body is rewritten (by way of SpamAssassin's report_safe together with |
||
23 | SARewriteBody: 1 in sa-exim.conf. This means that if you use |
||
24 | $body_linecount or $message_linecount in string expansions in your |
||
25 | Exim configuration, they will refer to the line count before rewriting |
||
26 | the message body. |
||
27 | |||
28 | This change will hopefully be restored soon, either by extending the |
||
29 | local_scan API or by making Exim count the lines. |
||
30 | |||
31 | -- Magnus Holmgren <magnus@kibibyte.se> Thu, 26 Apr 2007 16:22:49 +0200 |
||
32 |