From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Jani Nikula <jani@nikula.org>, Damien Cassou <damien@cassou.me>,
David Bremner <david@tethera.net>,
notmuch@notmuchmail.org
Subject: Re: notmuch-reply doesn't use Reply-To
Date: Tue, 29 Dec 2015 22:54:45 +0100 [thread overview]
Message-ID: <8760zgdioq.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <87twnygmps.fsf@nikula.org>
Hi all,
On Fri, Dec 04 2015, Jani Nikula wrote:
> On Fri, 04 Dec 2015, Damien Cassou <damien@cassou.me> wrote:
>> David Bremner <david@tethera.net> writes:
>>
>>> Damien Cassou <damien@cassou.me> writes:
>>>
>>>> "To" : "rmod@inria.fr",
>>>> "Reply-To" : "rmod@inria.fr",
>>>> "From" : "seaside@rmod.inria.fr",
>>>> "Subject" : "[rmod] [Mm10s] 2015-11-30",
>>>> "Date" : "Mon, 30 Nov 2015 07:00:01 +0100"
>>>
>>> A quick look at the code suggests this is falling victim to the
>>> "reply-to munging" detection code, which considers a reply-to field
>>> redudant if it duplicates one of the other fields. From the source
>>>
>>> /* Some mailing lists munge the Reply-To header despite it being A Bad
>>> * Thing, see http://www.unicom.com/pw/reply-to-harmful.html
>>> *
>>> * The munging is easy to detect, because it results in a
>>> * redundant reply-to header, (with an address that already exists
>>> * in either To or Cc). So in this case, we ignore the Reply-To
>>> * field and use the From header. This ensures the original sender
>>> * will get the reply even if not subscribed to the list. Note
>>> * that the address in the Reply-To header will always appear in
>>> * the reply.
>>> */
>>
>>
>> The last sentence seems to contradict my example:
>>
>> Note that the address in the Reply-To header will always appear in
>> the reply.
>>
>> Here is the reply message, and it does not contain the address in Reply-To.
>
> This was true way back when notmuch reply only knew about reply all. For
> --reply-to=sender, it's broken. The simplest "fix" might be
I don't think that this is broken for two reasons:
1. In tests/T230-reply-to-sender.sh, there is "Un-munging Reply-To"
test, which checks the same combination of headers as in Damien's
case and uses --reply-to=sender. The test passes and the reply has
To=From.
2. When replying to mailing lists using reply-to munging, current
notmuch behavior allows me to decide whether to reply 1) privately to
the mail sender (--reply-to=sender) or 2) to the mailing list
(--reply-to=all). The proposed change would make option 1) harder.
Therefore I suggest to fix this by applying the documentation patch from
the follow-up mail.
-Michal
next prev parent reply other threads:[~2015-12-29 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 16:28 notmuch-reply doesn't use Reply-To Damien Cassou
2015-12-04 12:07 ` David Bremner
2015-12-04 12:14 ` David Bremner
2015-12-04 15:06 ` Tomi Ollila
2015-12-04 16:40 ` Damien Cassou
2015-12-04 17:14 ` David Bremner
2015-12-04 17:14 ` Jani Nikula
2015-12-29 21:54 ` Michal Sojka [this message]
2015-12-29 21:55 ` [PATCH] doc/reply: Clarify how reply-to header is handled Michal Sojka
2016-03-14 23:39 ` David Bremner
2016-03-23 10:35 ` notmuch-reply doesn't use Reply-To David Bremner
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=8760zgdioq.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=damien@cassou.me \
--cc=david@tethera.net \
--cc=jani@nikula.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).