Re: [exim] blocking part of a relay

Top Page
Delete this message
Reply to this message
Author: Bill Hacker
Date:  
To: exim
Subject: Re: [exim] blocking part of a relay
Larry wrote:

> On Mon, Jan 23, 2006 at 05:11:23AM +0800, Bill Hacker wrote:
>
>
>>>>>I need to figure out how to block the origionator of a message.
>>>>>
>>
>>*SNIP*
>>
>>
>>>>Use originator-specific rules, optionally applied only to
>>>>traffic that arrives from mailhop.org.
>
>
>
> Thanks you for the lengthy answer. There is a lot of good information there.
> I think if I can figure out how to accomplish the above, things will begin
> to make a little more sense. I understand many of the commands to reject
> and warn with, the only part I am having a hellofatime with is figuring out
> how to "Use originator-specific rules". :)
>
>


Local blacklist is probably simplest if in doubt.

You were not all that specific as to wanting to block half the customers
of AOL, all of MSN, and 2/3 of the yahooligans, but only from Taiwan -
or just being temporarily pissed-off at your brother-in-law...

Blocking on seriously complex rules w/r IP, HELO, various bit of
address, headers, attachment characteristics, message size, format,
text expressions, even the sender's OS and mailer challenges even
SpamAssassin. Exim can do all that, but it can be a RBK [1] to maintain
- and not false-reject or generate unwelcome bounces.

For on or a few senders, all this is actually dead-easy with a Mozilla /
Thunderbird (or similar) MUA filter rule and bothers no one's MTA with
'collateral' damage.

MTA configurations should be for 'general case', not to target one
sender, unless they are trying a near-DoS.
For which there are better remedies anyway...

HTH,

Bill

{1] M1 Feline, female, immature, of noble rank, type one, class one,
standard A issue.