On Sat, Feb 06, 1999 at 04:31:13PM -0800, Joe Rhett <[EMAIL PROTECTED]> wrote:
> 
> On Sat, Feb 06, 1999 at 01:02:53PM -0500, Stan Ryckman wrote:
>  
> > The procmail list is open (for similar reasons; the procmail man page
> > points to it), yet it only gets maybe one piece of spam per month.
> > How?  It only accepts posts that have the list address in the To: or Cc:
> > header.  Nearly all spam doesn't do that, you may have noticed, because
> > it would slow down the flow of sludge by requiring small individual mailings
> > (since it's easy to autotrash messages with zillions of visible recipients).
> > 
> > So posters can't Bcc the procmail list any more... none are complaining
> > about that.
>  
> That is an interesting idea. [yanks up majordomo code to look] I don't see
> why it would be difficult to implement, the code only needs to be in one
> place.
>  
> Given that I was being so bitchy, I'll offer to attempt to provide a patch
> to majordomo to do just that (I'm assuming it is using majordomo here)

That would be really useful.  Yeah, the lists are running on majordomo.

> > It might be nice if perhaps something like LISTSERV(tm)'s NOMAIL option
> > were available... a subscribed address, but no mail gets sent to it
> > (except perhaps a renewal confirmation if nothing comes from it for
> > 6 months or a year).
> 
> It can be done with Majordomo. The list of people who can post and the list
> of people who get mail can be different files. Most sites use the same file
> or link them so that it is easier to administer :-)
> 
> I've looked into this before, hoping we could use an :include: syntax in
> the authorized users file, and it ended up being more work than I wanted to
> tackle at the time. When I look at the To: header thing, I'll look again.

This would also be really useful, and is something I wished majordomo
had.  Alternately, how about just letting the administrator specify two
files to read authorized users from?  This might well be easier, and
then one of the files could be the subscriber list, the other a list of
additional authorized users.  Then the list maintainer could add more
authorized users without suddenly opening up a huge problem of keeping
the two lists in sync.

-Daniel

-- 
Daniel Eisenbud
[EMAIL PROTECTED]

Reply via email to