[SA-exim] Using rewrite_header

Jason Lixfeld jason-saexim at lixfeld.ca
Mon Jul 24 10:04:11 PDT 2006


I think I figured it out. I didn't realize I had to restart exim and  
spamd if I made respective changes to their config files.  I thought  
the configs were read each time spamd/local_scan was called.

On 24-Jul-06, at 12:15 PM, Marc MERLIN wrote:

> On Mon, Jul 24, 2006 at 11:30:28AM -0400, Jason Lixfeld wrote:
>> On 24-Jul-06, at 11:10 AM, Marc MERLIN wrote:
>>
>>> grep -Ev "^(#|$)" sa-exim.conf
>>
>> SAEximDebug: 0
>> SAspamcpath: /usr/local/bin/spamc
>> SAspamcHost: 127.0.0.1
>> SAspamcPort: 783
>> 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}}
>> SAEximRunCond: 1
>> SAEximRejCond: ${if !eq {$h_X-SA-Do-Not-Rej:}{Yes} {1}{0}}
>> SAmaxbody: 256000
>> SATruncBodyCond: 0
>> SARewriteBody: 1
>
> If you are using report_safe, try turning that off and setting  
> SARewriteBody to
> 0, but it should work in the configuration you have, unless I'm  
> missing something.
>
> At this point, all I can offer is that you set SAEximDebug to 9,  
> and look at the SA
> logs after you accept a message that's spam.
> It should tell you that it's rewriting the subject header witt a  
> new value,
> and what that value is
>
> Marc
> -- 
> "A mouse is a device used to point at the xterm you want to type  
> in" - A.S.R.
> Microsoft is to operating systems & security ....
>                                       .... what McDonalds is to  
> gourmet cooking
> Home page: http://marc.merlins.org/
>




More information about the SA-Exim mailing list