Details | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 70 | magnus | 1 | Description: Improvements (in my opinion) of the default sa-exim.conf |
| 2 | Author: Magnus Holmgren <holmgren@debian.org> |
||
| 3 | |||
| 4 | --- sa-exim-4.2.1.orig/sa-exim.conf |
||
| 5 | +++ sa-exim-4.2.1/sa-exim.conf |
||
| 6 | @@ -49,9 +49,19 @@ SAspamcpath: /usr/bin/spamc |
||
| 7 | # This decides whether SA gets run against the message or not. This |
||
| 8 | # default will not reject messages if the message had SA headers but |
||
| 9 | # they weren't added by us. |
||
| 10 | -SAEximRunCond: ${if and {{def:sender_host_address} {!eq {$sender_host_address}{127.0.0.1}} {!eq {$h_X-SA-Do-Not-Run:}{Yes}} } {1}{0}} |
||
| 11 | +SAEximRunCond: ${if and {{def:sender_host_address} {!eq {$sender_host_address}{127.0.0.1}} {!eq {$sender_host_address}{::1}}}} |
||
| 12 | +# If you want more detailed control over when to run SA, it's recommended |
||
| 13 | +# that you set an ACL variable indicating this from the acl section of |
||
| 14 | +# your Exim configuration file. The current maintainer sets acl_m0 to |
||
| 15 | +# "noscan" if the sending host is localhost or has authenticated. |
||
| 16 | +#SAEximRunCond: ${if !eq{$acl_m0}{noscan}} |
||
| 17 | +# (This means exactly the same as ${if !eq{$acl_m0}{noscan} {true}{}}, |
||
| 18 | +# where the empty string is considered false.) |
||
| 19 | + |
||
| 20 | +#---------------------------------------------------------------------- |
||
| 21 | # Remove or comment out the following line to enable sa-exim |
||
| 22 | SAEximRunCond: 0 |
||
| 23 | +#---------------------------------------------------------------------- |
||
| 24 | |||
| 25 | # If and only if SAEximRunCond was true, and we did run SA, this |
||
| 26 | # expression decides whether we actually consider acting upon SAdevnull, |
||
| 27 | @@ -70,10 +86,12 @@ SAEximRunCond: 0 |
||
| 28 | # Use this to tag messages that you shouldn't reject (messages sent to |
||
| 29 | # abuse or postmaster for instance). |
||
| 30 | # |
||
| 31 | -# X-SA-Do-Not-Rej should be set as a warn header if mail is sent to |
||
| 32 | -# postmaster and abuse (in the RCPT ACL), this way you're not bouncing |
||
| 33 | -# spam abuse reports sent to you. This is a RFC guideline. |
||
| 34 | -SAEximRejCond: ${if !eq {$h_X-SA-Do-Not-Rej:}{Yes} {1}{0}} |
||
| 35 | +# As an example, set acl_m0 to "canreject" if a recipient other than |
||
| 36 | +# postmaster or abuse is encountered (and the sender isn't local). That |
||
| 37 | +# way, spammers can't circumvent blocking by sending to postmaster and |
||
| 38 | +# 99 other recipients. (If acl_m0 is taken, you'll of course have to use |
||
| 39 | +# a different variable. |
||
| 40 | +#SAEximRejCond: ${if eq{$acl_m0}{canreject}} |
||
| 41 | |||
| 42 | |||
| 43 | # How much of the body we feed to spamassassin (in bytes) |
||
| 44 | @@ -280,7 +298,7 @@ SApermrejectsave: /var/spool/exim/SAperm |
||
| 45 | # This is now a string (without quotes) that gets evaluated at runtime by exim |
||
| 46 | # but you can still assign a simple float value to it |
||
| 47 | # Default value is 2^20, which should disable the behavior |
||
| 48 | -SAtempreject: 9.0 |
||
| 49 | +#SAtempreject: 9.0 |
||
| 50 | |||
| 51 | # You can optionally save or not save messages that matched the above rule |
||
| 52 | SAtemprejectSavCond: 1 |