Re: charsets list? (was Secrets = Hits = Sales)

[Ned Freed <Ned.Freed@INNOSOFT.COM>]

> > > I agree.  Let's either restrict access to the list, or shut it down.

> > As I have pointed out before, this isn't possible. This is an IETF list
> > intended for discussion of character set issues -- a highly political area to
> > begin with. IETF discussions are supposed to be open to all comers, including
> > people not subscribed to the list. I am not going to open myself up to a charge
> > that I've unfairly restricted IETF discussions. Simply put, I don't want to be
> > sued.
 
>    To me it does not make any sense sending a mail to a list which I'm
> not subscribed to, since I would not be able to see any responses. So
> why? If it is for adminstrative messages on the standards process
> from some general IETF staff, this could be forwarded by the WG
> convenor, couldn't it?
 
First of all, while it may not make any sense to you, rest assured it makes
tons of sense to lots of people. I see messages posted to lists not less
than a couple of times every day that include the phrase "I'm not on this
list so please cc me in any responses".

Second, this list, like many other lists, has any number of sublists on other
machines, not to mention news gateways. As such, even if it didn't make
sense for non-subscribers to post, I have no way of determining whether or
not someone is on the list, at least not wich sufficient accuracy on which
to base a decision to bounce mail.

Third, there is nothing that says the address I use when I post is the one I
use to receive list mail. In my case it certainly isn't, and I'll bet this
applies to lots of other people as well. Now, some list managers, including the
one I use here, provide a feature by which they can have addresses on the list
for purposes of authentication that do not get copies of list  mail (this is
usually referred to an address being SET NOMAIL). And this is probably
sufficient in the case of non-IETF lists. But as I have previously explained,
it simply isn't acceptable in the case of IETF lists because of the importance
of the issues discussed on such lists and the current litigious climate.

Finally, I have now managed to get some anti-spam facilities installed on this
list. (This message is an initial test to see if they work.) Again, I have
no intention of describing these facilities publicly; if you want a complete
description send me private mail and I will explain what I have done.

				Ned