Hi Glenn,
That looks very useful - like my current version on steroids :P
Just to clarify a few things:
On Thu, Jan 29, 2004 at 11:45:26PM +0000, Glenn Carver wrote:
> Starting with the @@ bit, this causes exim to split the local_part
> and the domain of an address. For, say, user@???, exim would
> then do a lookup in the file with 'user' and 'example.com'. If your
> file had the entry:
>
> example.com *
>
> it would match the domain in the 1st column and user in the right
> column. The above entry would match all local_parts. This is
> equivalent to removing the @@ and making a domain list.
>
> However, if you did this:
>
> example.com okuser
>
> then the match would fail because it would only match on the name
> 'okuser@???'. So @@ let's you be selective about what
> local_parts to match in the file. I use this for blacklisting certain
> senders from certain hosts.
>
> Now the * on the end of lsearch* means that if the domain name can't
> be found, it will look for a domain name of '*' in the 1st column and
> then try to match the local_part with the list in the 2nd column. I
> use this to match typical local_parts that spam tends to use although
> it's less effective now than it used to be.
What exactly does your lsearch blacklist rule look like here?
Presumably you use it in the RCPT ACL?
Like thie look of this: :P
> So for instance the top of my sender_reject_bydomain file, which uses
> @@lsearch*, looks like this:
>
> * ^tobaccogift.+$:^smokesfrom.+$:^.+prankcall.+$:^adultoffer.+$:
> thinkx.tv *
> connectfree.co.uk attaboy
>
>
> The first line would match: smokesfrom@???, smokesfrom2@???.
>
> Hope that helps. I find the syntax in exim a bit cryptic sometimes
> but this is a useful feature which makes domain blocking more
> flexible.
>
> Glenn
--
Jez Hancock
- System Administrator / PHP Developer
http://munk.nu/
http://jez.hancock-family.com/ - Another FreeBSD Diary
http://ipfwstats.sf.net/ - ipfw peruser traffic logging
