Re: [RFC PATCH 3/3] cli: support Mail-Followup-To: in notmuch reply
authorPeter Wang <novalazy@gmail.com>
Wed, 6 Mar 2013 11:08:49 +0000 (22:08 +1100)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:53:56 +0000 (09:53 -0800)
a6/46052c0b5b0e5813769a58510a2cd6bc2858d5 [new file with mode: 0644]

diff --git a/a6/46052c0b5b0e5813769a58510a2cd6bc2858d5 b/a6/46052c0b5b0e5813769a58510a2cd6bc2858d5
new file mode 100644 (file)
index 0000000..6747d0e
--- /dev/null
@@ -0,0 +1,91 @@
+Return-Path: <novalazy@gmail.com>\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 6E003431FAF\r
+       for <notmuch@notmuchmail.org>; Wed,  6 Mar 2013 03:09:08 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0.602\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0.602 tagged_above=-999 required=5\r
+       tests=[DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1,\r
+       FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_LOW=-0.7]\r
+       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 DLEd1qZSJrvi for <notmuch@notmuchmail.org>;\r
+       Wed,  6 Mar 2013 03:08:58 -0800 (PST)\r
+Received: from mail-ia0-f174.google.com (mail-ia0-f174.google.com\r
+       [209.85.210.174]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id E15A5431FAE\r
+       for <notmuch@notmuchmail.org>; Wed,  6 Mar 2013 03:08:57 -0800 (PST)\r
+Received: by mail-ia0-f174.google.com with SMTP id u20so7148990iag.5\r
+       for <notmuch@notmuchmail.org>; Wed, 06 Mar 2013 03:08:56 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=x-received:date:message-id:from:to:cc:subject:in-reply-to\r
+       :references:mime-version:content-type:content-disposition\r
+       :content-transfer-encoding;\r
+       bh=6Hltio5o8RaabGKtmD/OHBurA5A2U2XNCVaKZ06EdRY=;\r
+       b=kUiSS+V84f6N01t11ckF5avHoIz7OfwWLkB9RPD+f9fXA3CRYr9m1jRtyEhiCf8hgK\r
+       5IzRIKgmXrcBmr80VjFCy9ysuZ+RS5Y3u7wxa8+HOcC1PJF+3rC/ydvbRdTji0MiG1wK\r
+       /mFva7MtA1IvRqf5kDFuFlBs6G5/ny0hR9i2eq1PqG0f40PNsHzegNFtCFdPMnMD5V2T\r
+       pLlJhGkRnec2Mc46adFieHX7gVwatAchIauWa0scgDepf808OIic0RGcXvFHhfZ2M/TJ\r
+       pcdDkBOdtcyIYxGpcWrGsmUhzzNjV6W1pPW049ZW+jU9ytV1h1uLbuIFYJivgHy94RlM\r
+       yHEw==\r
+X-Received: by 10.50.154.129 with SMTP id vo1mr10127419igb.93.1362568136411;\r
+       Wed, 06 Mar 2013 03:08:56 -0800 (PST)\r
+Received: from localhost (215.42.233.220.static.exetel.com.au.\r
+       [220.233.42.215])\r
+       by mx.google.com with ESMTPS id uq1sm21505480igc.5.2013.03.06.03.08.53\r
+       (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
+       Wed, 06 Mar 2013 03:08:55 -0800 (PST)\r
+Date: Wed, 6 Mar 2013 22:08:49 +1100\r
+Message-ID: <20130306220849.GB5730@hili.localdomain>\r
+From: Peter Wang <novalazy@gmail.com>\r
+To: Jani Nikula <jani@nikula.org>\r
+Subject: Re: [RFC PATCH 3/3] cli: support Mail-Followup-To: in notmuch reply\r
+In-Reply-To: <871ubwdcy7.fsf@nikula.org>\r
+References:\r
+ <5eaa3acc22ee5513bdce5ab931b7a79ade880e06.1362254104.git.jani@nikula.org>\r
+       <f9c7258be72bec0b174553db0410c29eba2745fa.1362254104.git.jani@nikula.org>\r
+       <20130303120745.GA4884@hili.localdomain>        <871ubwdcy7.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Disposition: inline\r
+Content-Transfer-Encoding: 8bit\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: Wed, 06 Mar 2013 11:09:08 -0000\r
+\r
+On Sun, 03 Mar 2013 11:56:00 +0200, Jani Nikula <jani@nikula.org> wrote:\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
+How about making it it optional on the command-line rather than through\r
+configuration?  Then you don't lose the functionality where you can\r
+initiate a reply to all visible From/To/Cc addresses (ready for pruning),\r
+regardless of the value of some header you probably don't even see, even\r
+if typically you *do* want to respect that header.\r
+\r
+(Bringing us back to the three reply functions.)\r
+\r
+Peter\r