From: Carl Worth <cworth@cworth.org>
To: Jed Brown <jed@59A2.org>, notmuch@notmuchmail.org
Subject: Re: Mailing list Reply-To munging and notmuch reply
Date: Sat, 28 Nov 2009 09:55:43 -0800 [thread overview]
Message-ID: <87vdgupm8w.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <877htavdn1.fsf@59A2.org>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On Sat, 28 Nov 2009 17:05:06 +0100, Jed Brown <jed@59A2.org> wrote:
> First, I'm aware that such munging is A Bad Thing
>
> http://www.unicom.com/pw/reply-to-harmful.html
Definitely.
> From: Some User <some.user@example.com>
> To: Sample users list <sample-users@sample.org>
> Reply-To: Sample users list <sample-users@sample.org>
>
> Notmuch reply produces
>
> To: Sample users list <sample-users@sample.org>,
> Sample users list <sample-users@sample.org>
>
> Handling this is a bit messy, I think we want the current behavior
> unless To matches Reply-To, in which case we use From and Reply-To. If
> this is indeed the least bad behavior, I will make a patch for it.
Oh, I really like that. The condition there avoids breaking legitimate
uses of Reply-To, (such as the cairo lists I run, where cairo-commit@
has no user-generated From:---just a single automated address, but has
Reply-To: set to the cairo@ list instead so that replies to committed
patches go to the right place).
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-11-28 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 16:05 Mailing list Reply-To munging and notmuch reply Jed Brown
2009-11-28 17:55 ` Carl Worth [this message]
2009-11-28 19:26 ` Jed Brown
2009-11-28 20:11 ` Carl Worth
2009-11-28 23:19 ` [PATCH 1/2] notmuch-reply.c: factor adding recipients into common function Jed Brown
2009-11-28 23:19 ` [PATCH 2/2] notmuch-reply.c: Handle munged `Reply-To' headers Jed Brown
2009-11-30 13:21 ` [PATCH] notmuch-reply.c: early exit for munged Reply-To when header is not present Jed Brown
2010-02-04 20:54 ` [PATCH 2/2] notmuch-reply.c: Handle munged `Reply-To' headers Carl Worth
2010-02-05 9:00 ` Jed Brown
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vdgupm8w.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=jed@59A2.org \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).