3f/78857ce1d0e4f13305d70f0c2d4f1129ebabfd

   1 Return-Path: <jani@nikula.org>\r
   2 X-Original-To: notmuch@notmuchmail.org\r
   3 Delivered-To: notmuch@notmuchmail.org\r
   4 Received: from localhost (localhost [127.0.0.1])\r
   5         by olra.theworths.org (Postfix) with ESMTP id 76F93431FAF\r
   6         for <notmuch@notmuchmail.org>; Sun,  3 Mar 2013 01:56:07 -0800 (PST)\r
   7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
   8 X-Spam-Flag: NO\r
   9 X-Spam-Score: -0.7\r
  10 X-Spam-Level: \r
  11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
  12         tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
  13 Received: from olra.theworths.org ([127.0.0.1])\r
  14         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
  15         with ESMTP id ZxFUAprmtIiv for <notmuch@notmuchmail.org>;\r
  16         Sun,  3 Mar 2013 01:56:05 -0800 (PST)\r
  17 Received: from mail-la0-f50.google.com (mail-la0-f50.google.com\r
  18         [209.85.215.50]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
  19         (No client certificate requested)\r
  20         by olra.theworths.org (Postfix) with ESMTPS id 1BAF3431FAE\r
  21         for <notmuch@notmuchmail.org>; Sun,  3 Mar 2013 01:56:04 -0800 (PST)\r
  22 Received: by mail-la0-f50.google.com with SMTP id ec20so4172838lab.9\r
  23         for <notmuch@notmuchmail.org>; Sun, 03 Mar 2013 01:56:03 -0800 (PST)\r
  24 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
  25         d=google.com; s=20120113;\r
  26         h=x-received:from:to:cc:subject:in-reply-to:references:user-agent\r
  27         :date:message-id:mime-version:content-type:x-gm-message-state;\r
  28         bh=VVEQH+O2DBeCNVT4mjypBH0x+LR2m7EBc5+1WC76nOs=;\r
  29         b=Fks52RLIPPut2xZmWOpjqnisAfN1RHT9spWugq6ncL7CzRJwnaKFg7kIcD134YK/Vp\r
  30         TfeAS8iZO200eAUFLDZ/8a3T4NP20mqIBydephdYlNDUsPTpN/RK2q9gceY0DqdSsxMr\r
  31         ORjrqAouKe/GBCVpV1Ek0EnoU2uM/+nk8bvXMoFfcviDjrS/ajzBzVYpM8q4Ta5Q7UY0\r
  32         WMRJqn+Cfg48yNF6ghvgI6JVB4fqqZgypI5egI0RYKoG+6LF5ZbKYWinNnVxRSnnj08O\r
  33         hkr/DL4Z1We2+VQo5yoeBG5Jf05gJhV4vLHilRPUeydyB/K1UAbFVLvBut7vGZPWe0am\r
  34         GBBA==\r
  35 X-Received: by 10.112.8.233 with SMTP id u9mr2975167lba.97.1362304563549;\r
  36         Sun, 03 Mar 2013 01:56:03 -0800 (PST)\r
  37 Received: from localhost (dsl-hkibrasgw4-50df51-27.dhcp.inet.fi.\r
  38         [80.223.81.27])\r
  39         by mx.google.com with ESMTPS id ng6sm9772632lab.2.2013.03.03.01.56.01\r
  40         (version=TLSv1.2 cipher=RC4-SHA bits=128/128);\r
  41         Sun, 03 Mar 2013 01:56:02 -0800 (PST)\r
  42 From: Jani Nikula <jani@nikula.org>\r
  43 To: Peter Wang <novalazy@gmail.com>\r
  44 Subject: Re: [RFC PATCH 3/3] cli: support Mail-Followup-To: in notmuch reply\r
  45 In-Reply-To: <20130303120745.GA4884@hili.localdomain>\r
  46 References:\r
  47  <5eaa3acc22ee5513bdce5ab931b7a79ade880e06.1362254104.git.jani@nikula.org>\r
  48         <f9c7258be72bec0b174553db0410c29eba2745fa.1362254104.git.jani@nikula.org>\r
  49         <20130303120745.GA4884@hili.localdomain>\r
  50 User-Agent: Notmuch/0.15.2+45~g53c33be (http://notmuchmail.org) Emacs/24.2.1\r
  51         (x86_64-pc-linux-gnu)\r
  52 Date: Sun, 03 Mar 2013 11:56:00 +0200\r
  53 Message-ID: <871ubwdcy7.fsf@nikula.org>\r
  54 MIME-Version: 1.0\r
  55 Content-Type: text/plain\r
  56 X-Gm-Message-State:\r
  57  ALoCoQnP2Pso/YREjtEl2YHt2QmHczZoZ4Fw8tvdig+Vf8UE5CYlV0LhyCQDX4LFUaMEJm+unSoG\r
  58 Cc: notmuch@notmuchmail.org\r
  59 X-BeenThere: notmuch@notmuchmail.org\r
  60 X-Mailman-Version: 2.1.13\r
  61 Precedence: list\r
  62 List-Id: "Use and development of the notmuch mail system."\r
  63         <notmuch.notmuchmail.org>\r
  64 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
  65         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
  66 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
  67 List-Post: <mailto:notmuch@notmuchmail.org>\r
  68 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
  69 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
  70         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
  71 X-List-Received-Date: Sun, 03 Mar 2013 09:56:07 -0000\r
  72 \r
  73 On Sun, 03 Mar 2013, Peter Wang <novalazy@gmail.com> wrote:\r
  74 > On Sat,  2 Mar 2013 21:55:21 +0200, Jani Nikula <jani@nikula.org> wrote:\r
  75 >> Use Mail-Followup-To header to determine recipients according to\r
  76 >> http://cr.yp.to/proto/replyto.html if configured and present in the\r
  77 >> message being replied to.\r
  78 >\r
  79 > I would like to see an option to --reply-to=list that, as far as\r
  80 > possible, does the right thing.  If we had that, do we need\r
  81 > reply.honor_followup_to?\r
  82 \r
  83 If you look at http://cr.yp.to/proto/replyto.html, it talks about *two*\r
  84 response functions, which correspond to our --reply-to=sender and\r
  85 --reply-to=all. The idea is to amend reply-all to honor Mail-Followup-To\r
  86 header if it is present in the mail being replied to. I don't think the\r
  87 interface should be more complicated than that.\r
  88 \r
  89 I have added the reply.honor_followup_to configuration because, although\r
  90 widely used, it's not a standard, and therefore some people might not\r
  91 like to respect that. Although I'd argue if the sender of the message\r
  92 has added that header, it's the sender's wish it should be respected.\r
  93 \r
  94 If people think our reply-all should always and unconditionally respect\r
  95 Mail-Followup-To if it's present, I'd be happy to throw out the config\r
  96 option. It's ugly.\r
  97 \r
  98 BR,\r
  99 Jani.\r
 100 \r
 101 \r
 102 PS. Please note that this is only the part that supports the\r
 103 Mail-Followup-To header when replying to incoming mail that has it;\r
 104 adding it to outgoing mail is beyond the scope here.\r