From: Carl Worth <cworth@cworth.org>
To: Jed Brown <jed@59A2.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] notmuch-reply.c: Handle munged `Reply-To' headers.
Date: Thu, 04 Feb 2010 12:54:20 -0800 [thread overview]
Message-ID: <87k4uspvr7.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <1259450376-24523-2-git-send-email-jed@59A2.org>
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
On Sun, 29 Nov 2009 00:19:36 +0100, Jed Brown <jed@59A2.org> wrote:
> Some mailing lists engage in the evil practice of changing the Reply-To
> header so that replies from all mailers go to the list by default, at
> the expense of not responding to the person who actually sent the
> message. When this is detected, we reply to `From' and remove the
> duplicate response to the mailing list. Consider a reply to the
> following message.
Thanks for the patch, Jed!
I've gone ahead and pushed this out, (along with some cleanups/fixes).
I augmented the notmuch test suite to actually test this case, (and the
related case of honoring Reply-To for a non-munged message). And I'm
glad I did because that turned up a bug in the patch, (using == instead
of != for the return value of strcasestr resulted in *all* messages with
a Reply-To header being considered as munged).
Here's one cleanup I made which you might find interesting as a style
issue (where I prefer naming a function based on what it *does* rather
than on what it's being *used* for):
commit d111c720bad53f98edba958aa605e857036a2bc8
Author: Carl Worth <cworth@cworth.org>
Date: Thu Feb 4 12:39:11 2010 -0800
notmuch reply: Rename the mailing_list_munged_reply_to function
This function detects whether the address in the Reply-To header
already appears in either To or Cc. So give it a name that reflects
what it does (reply_to_header_is_redundant) rather than the old name
which described one possible use of the function, (as a simple
heuristic for detecting whether a mailing list had applied reply-to
munging).
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-02-04 20:54 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
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 ` Carl Worth [this message]
2010-02-05 9:00 ` [PATCH 2/2] notmuch-reply.c: Handle munged `Reply-To' headers 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=87k4uspvr7.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).