Re: [RFC PATCH 3/3] cli: support Mail-Followup-To: in notmuch reply

diff --git a/3f/78857ce1d0e4f13305d70f0c2d4f1129ebabfd b/3f/78857ce1d0e4f13305d70f0c2d4f1129ebabfd
new file mode 100644 (file)
index 0000000..6f88705
--- /dev/null
+++ b/3f/78857ce1d0e4f13305d70f0c2d4f1129ebabfd
@@ -0,0 +1,104 @@
+Return-Path: <jani@nikula.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 76F93431FAF\r
+       for <notmuch@notmuchmail.org>; Sun,  3 Mar 2013 01:56:07 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id ZxFUAprmtIiv for <notmuch@notmuchmail.org>;\r
+       Sun,  3 Mar 2013 01:56:05 -0800 (PST)\r
+Received: from mail-la0-f50.google.com (mail-la0-f50.google.com\r
+       [209.85.215.50]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 1BAF3431FAE\r
+       for <notmuch@notmuchmail.org>; Sun,  3 Mar 2013 01:56:04 -0800 (PST)\r
+Received: by mail-la0-f50.google.com with SMTP id ec20so4172838lab.9\r
+       for <notmuch@notmuchmail.org>; Sun, 03 Mar 2013 01:56:03 -0800 (PST)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=google.com; s=20120113;\r
+       h=x-received:from:to:cc:subject:in-reply-to:references:user-agent\r
+       :date:message-id:mime-version:content-type:x-gm-message-state;\r
+       bh=VVEQH+O2DBeCNVT4mjypBH0x+LR2m7EBc5+1WC76nOs=;\r
+       b=Fks52RLIPPut2xZmWOpjqnisAfN1RHT9spWugq6ncL7CzRJwnaKFg7kIcD134YK/Vp\r
+       TfeAS8iZO200eAUFLDZ/8a3T4NP20mqIBydephdYlNDUsPTpN/RK2q9gceY0DqdSsxMr\r
+       ORjrqAouKe/GBCVpV1Ek0EnoU2uM/+nk8bvXMoFfcviDjrS/ajzBzVYpM8q4Ta5Q7UY0\r
+       WMRJqn+Cfg48yNF6ghvgI6JVB4fqqZgypI5egI0RYKoG+6LF5ZbKYWinNnVxRSnnj08O\r
+       hkr/DL4Z1We2+VQo5yoeBG5Jf05gJhV4vLHilRPUeydyB/K1UAbFVLvBut7vGZPWe0am\r
+       GBBA==\r
+X-Received: by 10.112.8.233 with SMTP id u9mr2975167lba.97.1362304563549;\r
+       Sun, 03 Mar 2013 01:56:03 -0800 (PST)\r
+Received: from localhost (dsl-hkibrasgw4-50df51-27.dhcp.inet.fi.\r
+       [80.223.81.27])\r
+       by mx.google.com with ESMTPS id ng6sm9772632lab.2.2013.03.03.01.56.01\r
+       (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+       Sun, 03 Mar 2013 01:56:02 -0800 (PST)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Peter Wang <novalazy@gmail.com>\r
+Subject: Re: [RFC PATCH 3/3] cli: support Mail-Followup-To: in notmuch reply\r
+In-Reply-To: <20130303120745.GA4884@hili.localdomain>\r
+References:\r
+ <5eaa3acc22ee5513bdce5ab931b7a79ade880e06.1362254104.git.jani@nikula.org>\r
+       <f9c7258be72bec0b174553db0410c29eba2745fa.1362254104.git.jani@nikula.org>\r
+       <20130303120745.GA4884@hili.localdomain>\r
+User-Agent: Notmuch/0.15.2+45~g53c33be (http://notmuchmail.org) Emacs/24.2.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Sun, 03 Mar 2013 11:56:00 +0200\r
+Message-ID: <871ubwdcy7.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-Gm-Message-State:\r
+ ALoCoQnP2Pso/YREjtEl2YHt2QmHczZoZ4Fw8tvdig+Vf8UE5CYlV0LhyCQDX4LFUaMEJm+unSoG\r
+Cc: notmuch@notmuchmail.org\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sun, 03 Mar 2013 09:56:07 -0000\r
+\r
+On Sun, 03 Mar 2013, Peter Wang <novalazy@gmail.com> wrote:\r
+> On Sat,  2 Mar 2013 21:55:21 +0200, Jani Nikula <jani@nikula.org> wrote:\r
+>> Use Mail-Followup-To header to determine recipients according to\r
+>> http://cr.yp.to/proto/replyto.html if configured and present in the\r
+>> message being replied to.\r
+>\r
+> I would like to see an option to --reply-to=list that, as far as\r
+> possible, does the right thing.  If we had that, do we need\r
+> reply.honor_followup_to?\r
+\r
+If you look at http://cr.yp.to/proto/replyto.html, it talks about *two*\r
+response functions, which correspond to our --reply-to=sender and\r
+--reply-to=all. The idea is to amend reply-all to honor Mail-Followup-To\r
+header if it is present in the mail being replied to. I don't think the\r
+interface should be more complicated than that.\r
+\r
+I have added the reply.honor_followup_to configuration because, although\r
+widely used, it's not a standard, and therefore some people might not\r
+like to respect that. Although I'd argue if the sender of the message\r
+has added that header, it's the sender's wish it should be respected.\r
+\r
+If people think our reply-all should always and unconditionally respect\r
+Mail-Followup-To if it's present, I'd be happy to throw out the config\r
+option. It's ugly.\r
+\r
+BR,\r
+Jani.\r
+\r
+\r
+PS. Please note that this is only the part that supports the\r
+Mail-Followup-To header when replying to incoming mail that has it;\r
+adding it to outgoing mail is beyond the scope here.\r