[Gllug] They worked brilliantly

[Stig Brautaset]

On Mar 01 2003, Martin wrote:
> At 14:25 01/03/2003 +0000, you wrote:
> >Non-trivial.  This would mean I need to hook in a whitelist of addresses
> >from mailman (on one machine) to the spamscanner (on another).  To be
> >frank it's not going to happen.
> 
> Why not simply only accept postings from subscribed addresses? Or do we do 
> that already?

Been discussed before. Many times. Please read the archives. I
completely agree with you though -- the list _should_ be subscribers
only. 

The situation here is a bit different from e.g. linux-kernel. There, it
makes sense to let Joe/Jane Unsubscribed User post about his/her kernel
panic and then get back to work instead of forcing them to go through
the cycle of subscribing, post the bugreport, have it rejected because
membership is not confirmed yet, wait, post again, unsubscribe, then
subsequently delete the 50+ messages of (to him/her) pure gibberish that
landed in their inbox while they were subscribed. It doesn't here.

The general gist of it is that people read the list from different
places and don't want to be inconvenieced by having to register several
addresses in the fear that they'll get gllug mail twice.

A bollocks argument, of course, since:

 a) all mailinglist software I'm aware of[1] make it trivial to set up
    "don't deliver mail to this address", i.e. a write-only address.

 b) All mailreaders worth their salt are able to set sender address
    based on certain criteria, such as who the mail is for[2]. Thus the
    "problem" doesn't even exist in the first place.


 [1] /including/ the version of Mailman which handles the gllug list
 [2] You do this in mutt with a 'send-hook', e.g. the one I have for
     gllug looks like this:

     send-hook gllug "my_hdr From: Stig Brautaset <gllug at brautaset.org>"

Stig
-- 
brautaset.org

-- 
Gllug mailing list  -  Gllug at linux.co.uk
http://list.ftech.net/mailman/listinfo/gllug