From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] reply-to munging
Date: Fri, 15 Apr 2005 09:37:55 +0900 [thread overview]
Message-ID: <20050415003755.GA10415@lion.gg3.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0504141407220.30824@stargazer.weeve.org>
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
maillog: 14/04/2005-14:10:34(-0600): Jason Wever types
> On Thu, 14 Apr 2005, Chris Gianelloni wrote:
>
> > Reply-to-All is evil. You should be using Reply-to-List. I know that I
> > sure don't need to get the same email both on and off-list. Off-list
> > emails should be reserved only for when you explicitly do not want to
> > send to the list and only to the original email's author.
>
> And just how many mail clients support reply-to-list (which in and of
> itself doesn't have well defined standards and is not adhered to in any
> specific way by the myriads of mailing list software packages out there)?
> Not very many last I checked.
"L" seems to work fine great in mutt. I do not have the word "gentoo"
mentioned in my muttrc, but it properly got the address from the
"List-Post" header. I also tried it on a "List-Post:<mailto:gentoo-dev@gentoo.org>"
posting (that was CCed to @lists) and it was properly addressed to
gentoo-dev@gentoo.org.
Congratulations. There is at least one properly behaving mail client.
It will be known how proper if it sets the Mail-FollowUp-To: header on
this mail.
> Best for now to deal with whether you want Reply-To to be altered or use
> Reply-To all.
I don't really care, but out of principle -- don't touch the header is
my vote.
--
\ Georgi Georgiev \ Apples have meant trouble since eden. -- \
/ chutz@gg3.net / MaDsen Wikholm, mwikholm@at8.abo.fi /
\ +81(90)2877-8845 \ \
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-15 0:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 8:54 [gentoo-dev] reply-to munging Paul de Vrieze
2005-04-14 9:01 ` Andrea Barisani
2005-04-14 9:06 ` Georgi Georgiev
2005-04-14 9:11 ` Andrea Barisani
2005-04-14 11:18 ` Chris Gianelloni
2005-04-14 13:49 ` Ming Zhao
2005-04-14 14:15 ` Stuart Longland
2005-04-14 15:23 ` Chris Gianelloni
2005-04-14 15:42 ` Ciaran McCreesh
2005-04-14 18:59 ` Chris Gianelloni
2005-04-14 16:32 ` Donnie Berkholz
2005-04-14 17:25 ` Drake Wyrm
2005-04-14 18:11 ` Paul de Vrieze
2005-04-14 19:01 ` Chris Gianelloni
2005-04-15 6:02 ` [gentoo-dev] " Duncan
2005-04-15 6:35 ` [gentoo-dev] " Andrea Barisani
2005-04-15 19:52 ` Donnie Berkholz
2005-04-16 8:59 ` Andrea Barisani
2005-04-16 9:09 ` Donnie Berkholz
2005-04-14 20:10 ` Jason Wever
2005-04-15 0:37 ` Georgi Georgiev [this message]
2005-04-17 18:02 ` D. Wokan
2005-04-14 23:20 ` Stuart Longland
2005-04-15 8:50 ` [gentoo-dev] " Torsten Veller
2005-04-15 11:32 ` [gentoo-dev] " Chris Gianelloni
2005-04-14 12:12 ` Graham Murray
2005-04-14 12:40 ` Ciaran McCreesh
2005-04-14 9:16 ` Spider
2005-04-14 9:11 ` Paul de Vrieze
-- strict thread matches above, loose matches on Subject: below --
2002-05-25 16:31 [gentoo-dev] Reply-To Munging Chad M. Huneycutt
2001-01-08 5:26 [gentoo-dev] reply-to munging drobbins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050415003755.GA10415@lion.gg3.net \
--to=chutz@gg3.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox