Rev 27 | Details | Compare with Previous | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 26 | magnus | 1 | sa-exim (4.2.1-8) unstable; urgency=medium |
| 2 | |||
| 3 | * Since version 4.67-1, exim4 only exports those symbols that are part |
||
| 4 | of the official local_scan API. Unfortunately, sa-exim has all along |
||
| 5 | cheated and declared some "extern" variables by itself, something that |
||
| 6 | no longer works. For one of these, body_linecount, no workaround is |
||
| 7 | currently possible, meaning that it will not be updated if the message |
||
| 8 | body is rewritten (by way of SpamAssassin's report_safe together with |
||
| 9 | SARewriteBody: 1 in sa-exim.conf. This means that if you use |
||
| 10 | $body_linecount or $message_linecount in string expansions in your |
||
| 11 | Exim configuration, they will refer to the line count before rewriting |
||
| 12 | the message body. |
||
| 13 | |||
| 14 | This change will hopefully be restored soon, either by extending the |
||
| 15 | local_scan API or by making Exim count the lines. |
||
| 16 | |||
| 17 | -- Magnus Holmgren <magnus@kibibyte.se> Thu, 26 Apr 2007 16:22:49 +0200 |
||
| 18 |