[Asterisk-Users] Important: The Asterisk Mailing list (newsubject)

[Steven Critchfield]

On Fri, 2004-03-19 at 22:23, Darren Nickerson wrote:
> Folks,
> 
> I strongly support removing the current reply-to-list setting, and you
> should too.
> 
> Like many new list admins, I once thought the reply-to was kewel. Requests
> to remove it kept coming up, ... usually around the same time someone
> embarrassed themselves by posting a personal reply/flame to the list.
> Someone, in frustration, finally pointed me to the following URL:
> 
>        http://www.unicom.com/pw/reply-to-harmful.html
> 
> I saw the light.
> 
> Please can the list admin step in and end this thread by either:
> 
>    a) announcing that the reply-to override has been removed
>    b) announcing their resignation ;-)


I'm sorry you saw the wrong light. You are peering into a light that
will anger many more of us to the point of removing ourselves from the
list as it becomes impossible to filter appropriately.

Reply to group has a nasty habit of piling up addresses and then people
who have dropped out of the thread are still getting barraged by
messages where their address is still a part of it.

It is bad enough we have users too lame to click on a link to the
submission url and instead just reply and erase old content, your
suggestion would just make people more likely to get nailed with
unrelated content.

Open source software thrives by efficient and open communications. To
start suggesting people take useful commentary off list by making it
less easy to reply to the list only reduces our resources. It also
starts a lot of private communications and possibly private flame wars.
If you post embarrassing information, or if your post embarrass you in
public, maybe they didn't need to be said in the first place.  

Your aversion to fixing a to line when you take a message off list is
not worth breaking good mail filtering.

You can probably blame me for the original switch of the Reply-To
header. I believe I am the one who requested it soo long ago.
-- 
Steven Critchfield  <critch at basesys.com>