Re: How does notmuch track mails?
[notmuch-archives.git] / 86 / 443f6f2a8e14865ab417280f3d061578015d5d
1 Return-Path: <sanelz@gmail.com>\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 arlo.cworth.org (Postfix) with ESMTP id BF03D6DE012F\r
6  for <notmuch@notmuchmail.org>; Fri,  1 Jul 2016 03:16:20 -0700 (PDT)\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org\r
8 X-Spam-Flag: NO\r
9 X-Spam-Score: -0.82\r
10 X-Spam-Level: \r
11 X-Spam-Status: No, score=-0.82 tagged_above=-999 required=5\r
12  tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
13  FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01,\r
14  RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled\r
15 Received: from arlo.cworth.org ([127.0.0.1])\r
16  by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
17  with ESMTP id W7ouh-8LjJaU for <notmuch@notmuchmail.org>;\r
18  Fri,  1 Jul 2016 03:16:13 -0700 (PDT)\r
19 Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com\r
20  [74.125.82.44]) by arlo.cworth.org (Postfix) with ESMTPS id ABB756DE00C8 for\r
21  <notmuch@notmuchmail.org>; Fri,  1 Jul 2016 03:16:12 -0700 (PDT)\r
22 Received: by mail-wm0-f44.google.com with SMTP id a66so22513205wme.0\r
23  for <notmuch@notmuchmail.org>; Fri, 01 Jul 2016 03:16:12 -0700 (PDT)\r
24 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
25  h=from:to:subject:user-agent:date:message-id:mime-version;\r
26  bh=zx6MR5bombon4brTI5h1GYaWLReBxvMOSDIqKz17158=;\r
27  b=MsPVDXl+Y7yeZAJeBckgbGuiEwZAzOaDCqnz5W4ZgEhzjkzuqvhbz2ko5JSQEw3RTN\r
28  Dp9sl0o8lnzb7r1VI38k2NQPzKsVW6lBTEeEqyz9ApJnU3uif43g9h5bmrjErmnTV2oc\r
29  elUrOSUH9sd2ohMM9fbH6Vqh6XnPsHrHDfVz8sKj1i0iUpo3AsfjesrwxuazGI0wCQrZ\r
30  Igo2f+95CN9xdB2nqbXQipMSv1RJZEEyEUsMDySLiSgDjyKF88OZ1asJHBvrKulG8eXw\r
31  UZqTv1tWHS8yyH4SQuevC4m27pm42BFdOwELYOpjJb7GtZggVoPEj0nl+AJZz83ahA5U\r
32  dO5Q==\r
33 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
34  d=1e100.net; s=20130820;\r
35  h=x-gm-message-state:from:to:subject:user-agent:date:message-id\r
36  :mime-version;\r
37  bh=zx6MR5bombon4brTI5h1GYaWLReBxvMOSDIqKz17158=;\r
38  b=nJwV/hgyhSomSQf7y3tObzlJIrPzMic+7szCpYHkfkHWGs5235pEWKqxqMUeyiBOvi\r
39  NwA7S2eTbMjtE8gVUXWdoRKv09Pbbj0QeKE/43iXFYF2IYROnoutiSyc2PBE31oa4P03\r
40  K7UCX800geQkvu7OD0rRjeu0nygC70TH4DbMEt4nav9L/0YQqeCiYBqIIFEtmPynEdZ/\r
41  cn8lqMGWbCAtcW2/QqZ2FUBfkvAdxG5+jfzoTx7mFq0pusJRKiM8yyCakaIzMYrAt0b0\r
42  xaJS1NY67KwGUSqq5/BKnXXpV97GmQNVA9Cq4+cE/9d7nwmnnA8yC/As5E40IoOGhKFo\r
43  RQVg==\r
44 X-Gm-Message-State:\r
45  ALyK8tI2oyexv6tGmVjO63D3Tg59KjTXvbflWCEBV277OyYKJL8jmNOOvYYFTwjMQt/jkA==\r
46 X-Received: by 10.28.211.142 with SMTP id k136mr32356208wmg.29.1467368169661; \r
47  Fri, 01 Jul 2016 03:16:09 -0700 (PDT)\r
48 Received: from localhost (cable-146-255-131-70.dynamic.telemach.ba.\r
49  [146.255.131.70])\r
50  by smtp.gmail.com with ESMTPSA id i14sm4213609wmf.13.2016.07.01.03.16.08\r
51  for <notmuch@notmuchmail.org>\r
52  (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
53  Fri, 01 Jul 2016 03:16:09 -0700 (PDT)\r
54 From: Sanel Zukan <sanelz@gmail.com>\r
55 To: notmuch@notmuchmail.org\r
56 Subject: Issue with verifying cleartext signed messages\r
57 User-Agent: Notmuch/0.21 (http://notmuchmail.org)\r
58 Date: Fri, 01 Jul 2016 12:16:07 +0200\r
59 Message-ID: <87oa6hbr4o.fsf@darkstar.example.net>\r
60 MIME-Version: 1.0\r
61 Content-Type: text/plain\r
62 X-Mailman-Approved-At: Fri, 01 Jul 2016 04:35:16 -0700\r
63 X-BeenThere: notmuch@notmuchmail.org\r
64 X-Mailman-Version: 2.1.20\r
65 Precedence: list\r
66 List-Id: "Use and development of the notmuch mail system."\r
67  <notmuch.notmuchmail.org>\r
68 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,\r
69  <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
70 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>\r
71 List-Post: <mailto:notmuch@notmuchmail.org>\r
72 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
73 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
74  <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
75 X-List-Received-Date: Fri, 01 Jul 2016 10:16:20 -0000\r
76 \r
77 Hi,\r
78 \r
79 I'm using epa-verify-cleartext-in-region to verify cleartext signed\r
80 messages and noticed it will sometimes fail with notmuch, especially\r
81 when target mail message is part of longer thread.\r
82 \r
83 For example, when signed mail is first in thread, body will look like:\r
84 \r
85 -----BEGIN PGP SIGNED MESSAGE-----\r
86  <content>\r
87 -----BEGIN PGP SIGNATURE-----\r
88  <signature>\r
89 -----END PGP SIGNATURE-----\r
90 \r
91 and epa-verify-cleartext-in-region will correctly capture and verify it.\r
92 However, when the message is second or third in thread, notmuch will\r
93 append spaces in front of it, making it looks like this:\r
94 \r
95   -----BEGIN PGP SIGNED MESSAGE-----\r
96    <content>\r
97   -----BEGIN PGP SIGNATURE-----\r
98    <signature>\r
99   -----END PGP SIGNATURE-----\r
100 \r
101 epa-verify-cleartext-in-region will fail here with: "Invalid cleartext\r
102 signed message".\r
103 \r
104 Error is reproducible - copy the body of message with signature in new\r
105 buffer, remove starting spaces and epa-verify-cleartext-in-region will\r
106 work.\r
107 \r
108 Any idea how to solve this? Or even better, is it possible to display\r
109 messages flat, without tree view.\r
110 \r
111 If you can, please CC me with reply as I'm not member of this list.\r
112 \r
113 Thanks in advace.\r
114 \r
115 Best,\r
116 Sanel\r