as much as reply-to mangling is bad, +1 to add a reply-to header.  (+2 for Google adding an option to make the default reply on message from a mailing list configurable) <div class="gmail_quote">On Feb 10, 2008 6:40 AM, Youness Alaoui <<a href="mailto:kakaroto@kakaroto.homelinux.net">kakaroto@kakaroto.homelinux.net</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Yeah.. of course, I again forgot to CC the ML... lol ----- Forwarded message from Youness Alaoui <<a href="mailto:kakaroto@kakaroto.homelinux.net">kakaroto@kakaroto.homelinux.net</a>> ----- From: Youness Alaoui <<a href="mailto:kakaroto@kakaroto.homelinux.net">kakaroto@kakaroto.homelinux.net</a>> To: Ethan Blanton <<a href="mailto:elb@pidgin.im">elb@pidgin.im</a>> Subject: Re: Request: Add Reply-To Header Ok thanks, but it doesn't help.. first, by adding the 'subscribe' in muttrc it will change all the 'From' fields into 'To: openim.." or "CC: openim.." so I can't see who wrote the mail unless I open it. Also, the 'r'/'l'/'g' already works without adding the 'subscribe' and that's what I use when I think about it, but I'm just too used to typing 'r' to reply... if I could configure it to send to the mailing list automatically when I press 'r', that would help! Thanks! KaKaRoTo On Fri, Feb 01, 2008 at 10:06:05PM -0500, Ethan Blanton wrote: > Youness Alaoui spake unto us the following wisdom: > > I use mutt over a terminal as mail client, and it doesn't recognize > > the list, so I need to do a reply-all, which I am really not used to > > doing..  I prefer the reply-to header as this makes it much easier.. > > for me at least... we could try to vote on who wants it and who > > doesn't (or don't care) then decide.. I would vote for having a > > reply-to header. > > Put 'subscribe <a href="mailto:openim@imfreedom.org">openim@imfreedom.org</a>' in your .muttrc, and it will > recognize the list.  You will then have three reply options -- 'r' for > reply to sender, 'L' for reply to list, and 'g' for reply to all. > This is the correct way to handle things in any sane mailreader.  Mutt > has fantastic support for mailing lists. > > > Subject mangling would be nice, helps me see what was sent where, but > > it's not necessary at all, so I really don't mind it the way it is. > > Put: > > :0: > * ^List-Id: <openim\.imfreedom\.org> > { >     SUBJECT=`formail -c -xSubject:` >     :0fw >     | formail -I "Subject: [openim] $SUBJECT" > } > > in your .procmailrc. > > While I don't feel *too* strongly about reply-to mangling (it's > obviously wrong and broken, but easy enough to hack around if you have > to with rare ill-effects), subject mangling is a *really* bad idea. > > Ethan > > -- > The laws that forbid the carrying of arms are laws [that have no remedy > for evils].  They disarm only those who are neither inclined nor > determined to commit crimes. >               -- Cesare Beccaria, "On Crimes and Punishments", 1764 > _______________________________________________ > Openim mailing list > <a href="mailto:Openim@imfreedom.org">Openim@imfreedom.org</a> > <a href="http://pidgin.im/cgi-bin/mailman/listinfo/openim" target="_blank">http://pidgin.im/cgi-bin/mailman/listinfo/openim</a> ----- End forwarded message ----- _______________________________________________ Openim mailing list <a href="mailto:Openim@imfreedom.org">Openim@imfreedom.org</a> <a href="http://pidgin.im/cgi-bin/mailman/listinfo/openim" target="_blank">http://pidgin.im/cgi-bin/mailman/listinfo/openim</a> </blockquote> </div> -- - Norman Rasmussen - Email: <a href="mailto:norman@rasmussen.co.za">norman@rasmussen.co.za</a> - Home page: <a href="http://norman.rasmussen.co.za/">http://norman.rasmussen.co.za/</a>