From: Phil Blundell <pb@reciva.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] rw for Lynn Lin
Date: Sun, 17 May 2009 15:18:21 +0100 [thread overview]
Message-ID: <1242569901.4226.28.camel@lenovo.internal.reciva.com> (raw)
In-Reply-To: <4A1017FB.2000204@balister.org>
On Sun, 2009-05-17 at 09:58 -0400, Philip Balister wrote:
> PS: I know this is getting posted twice ... I am checking the both
> lists.oe.org and oe.org and receiving email.
Yeah, this is a longstanding misfeature of the way this mailing list is
set up and it is a little bit annoying. What happens is that you can
post to either oe-devel@lists.oe.org, or oe-devel@oe.org, but mailman
always adds Reply-to: oe-devel@lists.oe.org irrespective of which
address was used for posting. If you hit "Reply to all" on an email
which has different things in To: and Reply-to:, most MUAs will send a
copy of the reply to both places; Mailman doesn't seem to be de-duping
them, which means that we get both showing up on the list.
There are a few different ways to fix it but all of them would require
tweaks to the server configuration:
1. Just turn off the aliasing on the @oe.org address and make everybody
use the @lists.oe.org one. This would be a bit unfriendly but it's
probably the least administrative effort.
2. Configure Mailman to not add Reply-to at all, and rely on users
always hitting "Reply to all". This is the best solution if you belong
to the "reply-to considered harmful" school of thought, and/or can live
with some replies accidentally getting sent to just the original poster
and not the whole list.
2. Configure the mail system on lists.oe.org to rewrite oe-devel@oe.org
-> oe-devel@lists.oe.org on all incoming posts so that the To: and
Reply-to: headers are consistent with each other. If the replying MUA
only sees a single address there then it will only send one copy even
with "reply to all". This is probably the best solution if you want to
keep the Reply-to header.
4. Configure the lists.oe.org mail system to spot these dupes (which
have the same Message-ID) and drop all but the first copy.
p.
next prev parent reply other threads:[~2009-05-17 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 13:44 [RFC] rw for Lynn Lin Rolf Leggewie
2009-05-17 13:58 ` Philip Balister
2009-05-17 14:18 ` Phil Blundell [this message]
2009-05-21 7:36 ` Stanislav Brabec
2009-05-21 16:08 ` Marcin Juszkiewicz
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=1242569901.4226.28.camel@lenovo.internal.reciva.com \
--to=pb@reciva.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.