Andrew Tasi wrote in List-Managers-Digest V9 #30:

> Date: Wed, 16 Feb 2000 14:35:32 -0600
> From: "Andrew Tasi" <[EMAIL PROTECTED]>
> Subject: Banning in majordomo
> 
> Hello mail list gurus,
> 
> I run a large majordomo discussion list, and there is a particular
> user that has been a problem in the past.  Sometime last year, I
> started bouncing all messages from his addresses with taboo_header.
> It took him a while to catch on.
> 
> I let him continue reading the list (even though he was not able to
> post) and that was fine for a while.  But now he has taken to
> misinforming people and trying to pick fights in private.  So now I'd
> like to ban him from both reading and writing.  Is there a really
> easy/simple way to do this if my preference is to keep the current
> subscriber policy of open+confirm?  I realize he could always
> subscribe from a new address, but he hasn't tried that (yet?).

Andrew,

If you are using a modern Sendmail on your server like 8.9+, it's fairly
easy to set up an access database that will reject or silently drop any
incoming mail from a specific user and/or domain.  Mine looks like this:

[/etc/mail/access]

## After making changes to this file, run:
#
#  makemap dbm /etc/mail/access < /etc/mail/access
#
#
## Sample entry with custom 550 message
#
#[EMAIL PROTECTED]     550 Won't accept mail until looping problem with
user '[EMAIL PROTECTED]' is resolved

[EMAIL PROTECTED]                      DISCARD
#[EMAIL PROTECTED]                  DISCARD
[EMAIL PROTECTED]             DISCARD
#

--
For more information, see: http://www.sendmail.org/tips/relaying.html

As you can see, it's possible to include custom error messages, or just
"silently" drop the mail with the remote server unaware.  I use this feature
frequently when a remote site/user starts looping with Majordomo. 
Incidently, I run a 20,000+ mailing list on emerging diseases on a server at
Harvard University.

Cheers,

Phil Temples
[EMAIL PROTECTED]
-- 
Phil Temples <[EMAIL PROTECTED]>

Reply via email to