Author: Peter Bowyer Date: To: exim users Subject: Re: [exim] Capturing Bad HELO
On 30/05/06, Peter Bowyer <peter@???> wrote: > On 30/05/06, Marc Perkel <marc@???> wrote:
> > So - I'm getting a lot of these:
> >
> > 2006-05-30 14:28:52 rejected HELO from
> > 58.red-88-11-33.dynamicip.rima-tde.net [88.11.33.58]: syntactically
> > invalid argument(s): (no argument given)
> >
> > If I can what I'm thinking about is that it appears the system is
> > catching these for me. What I want to do is capture these myself in an
> > ACL so as to process them the way I want (IP capture and logging).
> >
> > So - I'm trying to understand what's causing it in the first place and
> > what I might do with it. I've been feading spam and other info to
> > several spam filtering lists to try to spread some of my data around and
> > help others fight spam. So I'm more into harvesting than rejecting at
> > the moment.
>
> helo_verify_hosts
>
> is what causes the rejection you're seeing. If you set
> helo_try_verify_hosts instead, you can use
>
> verify=helo
>
> in a DATA acl to take some alternative course of action with invalid HELOs.
Correcting my own post - verify=helo can be used in any ACL after
acl_smtp_connect. I was thinking of verify=header_syntax, which can
(obviously) only be used after DATA.
