Re: [exim] HELO checks and spamassassin

Top Page
Delete this message
Reply to this message
Author: Chris Lear
Date:  
To: Exim users list
CC: Alan J. Flavell
Subject: Re: [exim] HELO checks and spamassassin
* Alan J. Flavell wrote (12/04/2005 16:07):
> On Tue, 12 Apr 2005, Chris Lear wrote:
>
>> xxxxxx-xxxxxx-xx H=(ns.citynet.ru) [62.118.250.132] Warning: HELO
>> argument does not match calling host
>
> Is that a "message" or a "log_message"? If it's a message (i.e it's
> going to cut an additional log header), you might want the text to
> start with a distinctive header name string, like X-HELO-warning: or
> whatever you choose.


It's a log_message, but there's also a message (header), which is
similar to what you suggest. As far as I can see, this can contribute to
spamassassin's bayesian analysis, but doesn't seem to trigger a rule
like FORGED_RCVD_HELO, which is what I'd prefer (and which isn't being
triggered).

[...]

>
>> Is there anything I can do in exim.conf that will affect the
>> spamassassin score? I guess the answer may be to use an acl variable.
>
> indeed - along the lines of (having calculated some spam bonus in
> acl_m7):
>
>   deny [...]
>       spam = nobody:true
>       condition = ${if \
>           >{${eval:$spam_score_int+$acl_m7}}{80}{yes}{no}}

>


I think I'll do this, although it doesn't actually affect the
spamassassin score (so doesn't help with autolearning etc).

Thanks for your help.

Chris