Re: [PATCH] emacs: wash: make word-wrap bound message width
[notmuch-archives.git] / d0 / 6af317af979b7aa7fa918e2b9d1ddf3a9a9c19
1 Return-Path: <dkg@fifthhorseman.net>\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 6020740DDE6\r
6         for <notmuch@notmuchmail.org>; Sat, 13 Nov 2010 08:00:41 -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: -1.899\r
10 X-Spam-Level: \r
11 X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5\r
12         tests=[BAYES_00=-1.9, UNPARSEABLE_RELAY=0.001] autolearn=ham\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 lBPvlS+2OlJq for <notmuch@notmuchmail.org>;\r
16         Sat, 13 Nov 2010 08:00:30 -0800 (PST)\r
17 Received: from rodolpho.mayfirst.org (mail.freitas.net [209.234.253.107])\r
18         (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))\r
19         (No client certificate requested)\r
20         by olra.theworths.org (Postfix) with ESMTPS id DA36240DDC7\r
21         for <notmuch@notmuchmail.org>; Sat, 13 Nov 2010 08:00:29 -0800 (PST)\r
22 Received: from localhost (localhost [127.0.0.1])\r
23         by rodolpho.mayfirst.org (Postfix) with ESMTP id 9D9B23CD5C\r
24         for <notmuch@notmuchmail.org>; Sat, 13 Nov 2010 11:00:24 -0500 (EST)\r
25 X-Virus-Scanned: Debian amavisd-new at rodolpho.mayfirst.org\r
26 Received: from rodolpho.mayfirst.org ([127.0.0.1])\r
27         by localhost (rodolpho.mayfirst.org [127.0.0.1]) (amavisd-new,\r
28         port 10024) with ESMTP id qVoAAbSAyFnL for <notmuch@notmuchmail.org>;\r
29         Sat, 13 Nov 2010 11:00:24 -0500 (EST)\r
30 Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender:\r
31         smtpauth@rodolpho.mayfirst.org) with ESMTPSA id 67DF93CD58\r
32 Message-ID: <4CDEB613.3080005@fifthhorseman.net>\r
33 Date: Sat, 13 Nov 2010 11:00:19 -0500\r
34 From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
35 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;\r
36         rv:1.9.2.9) Gecko/20100918 Icedove/3.1.4\r
37 MIME-Version: 1.0\r
38 To: notmuch <notmuch@notmuchmail.org>\r
39 Subject: Re: a proposed change to JSON output to report verification of\r
40         PGP/MIME signatures.\r
41 References: <4CDE4486.2050101@fifthhorseman.net>\r
42         <87d3q91mf7.fsf@zancas.localnet>\r
43 In-Reply-To: <87d3q91mf7.fsf@zancas.localnet>\r
44 X-Enigmail-Version: 1.1.2\r
45 OpenPGP: id=D21739E9\r
46 Content-Type: multipart/signed; micalg=pgp-sha512;\r
47         protocol="application/pgp-signature";\r
48         boundary="------------enig6789897A68EE7D50C4C9FC7E"\r
49 X-BeenThere: notmuch@notmuchmail.org\r
50 X-Mailman-Version: 2.1.13\r
51 Precedence: list\r
52 Reply-To: notmuch <notmuch@notmuchmail.org>\r
53 List-Id: "Use and development of the notmuch mail system."\r
54         <notmuch.notmuchmail.org>\r
55 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
56         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
57 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
58 List-Post: <mailto:notmuch@notmuchmail.org>\r
59 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
60 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
61         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
62 X-List-Received-Date: Sat, 13 Nov 2010 16:00:41 -0000\r
63 \r
64 This is an OpenPGP/MIME signed message (RFC 2440 and 3156)\r
65 --------------enig6789897A68EE7D50C4C9FC7E\r
66 Content-Type: text/plain; charset=UTF-8\r
67 Content-Transfer-Encoding: quoted-printable\r
68 \r
69 Thanks for the reply, David!\r
70 \r
71 On 11/13/2010 06:40 AM, David Bremner wrote:\r
72 > Are both the forward and backward pointers needed?\r
73 \r
74 Technically, only the "signs" pointer is needed, i guess.  I had\r
75 included the "signedby" pointer so that frontends which process the list\r
76 linearly know that a signed part will be referred to later by one or\r
77 more signatures.\r
78 \r
79 If you think that's not actually useful, i'd be happy to drop the\r
80 "signedby" pointer.  What do other people think?\r
81 \r
82 >> Would it make more sense to do deeper structural modifications of the\r
83 >> json output (e.g. return the full MIME tree instead of a list of parts=\r
84 )\r
85 >> than to go with the current proposal?\r
86 >=20\r
87 > Yeah, this occured to me too, especially since I think David Edmondson\r
88 > has some changes in mind to support better handling of\r
89 > multipart/alternative parts.\r
90 \r
91 Another related concern that occurred to me is that parts E and F in my\r
92 example mail are technically part of the aggregate that is signed by I,\r
93 but they apparently the end-user won't even know they exist (unless the\r
94 frontend uses "notmuch show --format=3Dmbox").\r
95 \r
96 This seems problematic if the message headers of the included message\r
97 have relevance to the content.  e.g. an e-mail that says "here's the\r
98 phishing attempt i received" (Received: would be relevant) or "Look at\r
99 the nasty things this guy said!" (From:, Subject:, and Date: would be\r
100 relevant at least).\r
101 \r
102 David Edmonson, i'd be interested in hearing your proposal for\r
103 restructuring the output to see how it might interact with my pieces here=\r
104 =2E\r
105 \r
106 I also found it interesting to consider the range of possible non-leaf\r
107 MIME types:\r
108 \r
109  https://secure.wikimedia.org/wikipedia/en/wiki/MIME#Multipart_messages\r
110  http://www.iana.org/assignments/media-types/multipart/\r
111 \r
112         --dkg\r
113 \r
114 \r
115 --------------enig6789897A68EE7D50C4C9FC7E\r
116 Content-Type: application/pgp-signature; name="signature.asc"\r
117 Content-Description: OpenPGP digital signature\r
118 Content-Disposition: attachment; filename="signature.asc"\r
119 \r
120 -----BEGIN PGP SIGNATURE-----\r
121 Version: GnuPG v1.4.10 (GNU/Linux)\r
122 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/\r
123 \r
124 iQIcBAEBCgAGBQJM3rYTAAoJEMzS7ZTSFznpn1oQAI+ASDXiCIU3H5AirGtgJVGV\r
125 KApUy3chU3J0iPAaFfHapS1HyTLlgNwfH6hoNNjVAa2DqLjXi9xHFF/SyeLCY9nG\r
126 eCS7gWYKzop//i7APiKn25FvzkHJRKX0DCer/flafmlxjHMA42nkUDI0Eqv9KNa7\r
127 kW4i0vhRDK+slP+WNsUla1r5DsUnaDHjX5ojLvv7S+Ej6hzmsssZTuvFzA4gv3yR\r
128 M02n4cSewjM6kgcF6sKsONhTpZLN2saP7zlPuW9PEGIgwKb1MuZewT9PLJt42Cw+\r
129 m/fc6tBFGyXx+q/889FMSCz1MTS26rAioopG8DTK04SoAnv0+68nPQwhTQJiRMZ+\r
130 DwxfSdrdYovYC97wKPV55hR9KjUtbFv/ApGJqduAQXe2jSKNcppoekOU9PJqjcWf\r
131 Pj4FpwZRtgVxNdVRKUVX1QbL9jbU4PCVTSHEvSExhITQ+km/H5u84ALxZ+nr0NV9\r
132 +L3E4NPxMowWBdYs+0GqsshGMFVNft+TKmQpWEqRA9Chua1qDqLFWwUjeDb7fp2w\r
133 xAt2aA1K6n1Q/nvr5+eNQKB1QFwPgQxCkBw+IZM4eJ8ud+HZlu5OqjMA5rcckoeb\r
134 2/FLHmCy6yTvwlQM/2EjiqsGpuDZYJDZUMoDd3qF5zvQ4ZcPBIf72yVjYryqc13B\r
135 kmeeaFcC1NHw3FFBGYP/\r
136 =hWfm\r
137 -----END PGP SIGNATURE-----\r
138 \r
139 --------------enig6789897A68EE7D50C4C9FC7E--\r