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 BF497429E28
\r
6 for <notmuch@notmuchmail.org>; Tue, 30 Aug 2011 14:51:58 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\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 yqvJiVatouLJ for <notmuch@notmuchmail.org>;
\r
16 Tue, 30 Aug 2011 14:51:58 -0700 (PDT)
\r
17 Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 2A7D9429E27
\r
19 for <notmuch@notmuchmail.org>; Tue, 30 Aug 2011 14:51:58 -0700 (PDT)
\r
20 Received: from [192.168.13.75] (lair.fifthhorseman.net [216.254.116.241])
\r
21 by che.mayfirst.org (Postfix) with ESMTPSA id C5583F970
\r
22 for <notmuch@notmuchmail.org>; Tue, 30 Aug 2011 17:51:53 -0400 (EDT)
\r
23 Message-ID: <4E5D5B7D.7050104@fifthhorseman.net>
\r
24 Date: Tue, 30 Aug 2011 17:51:57 -0400
\r
25 From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
\r
26 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20110807 Icedove/5.0
\r
28 To: notmuch@notmuchmail.org
\r
29 Subject: Re: How does notmuch detect the presence of attachments?
\r
31 <CAJ+wP3X5SxPPLyy=jbVMW5QZvuZSq5Vkt=6tVnL_Sd=W9Ys_SA@mail.gmail.com>
\r
32 <4E565A61.7040600@fifthhorseman.net>
\r
33 <20110830062229.GC8590@lemote.jasonwoof.com>
\r
34 In-Reply-To: <20110830062229.GC8590@lemote.jasonwoof.com>
\r
35 X-Enigmail-Version: 1.2.1
\r
36 Content-Type: multipart/signed; micalg=pgp-sha512;
\r
37 protocol="application/pgp-signature";
\r
38 boundary="------------enig11C0BE8A616BDB95A10B1CAA"
\r
39 X-BeenThere: notmuch@notmuchmail.org
\r
40 X-Mailman-Version: 2.1.13
\r
42 Reply-To: notmuch <notmuch@notmuchmail.org>
\r
43 List-Id: "Use and development of the notmuch mail system."
\r
44 <notmuch.notmuchmail.org>
\r
45 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
46 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
47 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
48 List-Post: <mailto:notmuch@notmuchmail.org>
\r
49 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
50 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
51 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
52 X-List-Received-Date: Tue, 30 Aug 2011 21:51:58 -0000
\r
54 This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
\r
55 --------------enig11C0BE8A616BDB95A10B1CAA
\r
56 Content-Type: text/plain; charset=UTF-8
\r
57 Content-Transfer-Encoding: quoted-printable
\r
59 On 08/30/2011 02:22 AM, Jason Woofenden wrote:
\r
63 >> application/pdf=3Dpdf2txt /dev/stdin
\r
65 > Sounds awesome. I'd love the feature, and this sounds like a good
\r
66 > way to do it. Or maybe we should use a mailcap file like mutt
\r
67 > does... it has some useful features like nametemplate and maybe
\r
70 hm, interesting suggestion. I don't know enough about mailcap to know
\r
71 whether it makes more sense to adopt it directly or to use a
\r
72 notmuch-specific configuration.
\r
74 One difference: mailcap seems to be about displaying/editing data to the
\r
75 user (including, for example, opening a graphical window to display a
\r
76 JPEG), whereas we need to set up a mechanism to convert whatever kind of
\r
77 document we get into plain text to feed it into xapian. So we couldn't
\r
78 fully piggy-back on the mailcap infrastructure, if i'm reading the
\r
79 mailcap documentation correctly. notmuch would need to use its own
\r
82 Anyone with more experience with this stuff (or stronger opinions) have
\r
83 any insight on what approach makes more sense?
\r
85 > I as a user can decide that I'd like to run `abiword -t txt` on
\r
86 > application/msword and application/rtf mime parts. If there's a
\r
87 > security issue with abiword that someone can exploit by sending me
\r
88 > an e-mail, then FML, but at least I won't be mad at the notmuch
\r
96 --------------enig11C0BE8A616BDB95A10B1CAA
\r
97 Content-Type: application/pgp-signature; name="signature.asc"
\r
98 Content-Description: OpenPGP digital signature
\r
99 Content-Disposition: attachment; filename="signature.asc"
\r
101 -----BEGIN PGP SIGNATURE-----
\r
102 Version: GnuPG v1.4.11 (GNU/Linux)
\r
103 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
\r
105 iQJ8BAEBCgBmBQJOXVt9XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
\r
106 ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD
\r
107 Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpFIsP/0hnLZiOJWs0qoBjuugvGg+r
\r
108 dkDJ5LiwdE9DA6vZdCJjzENiviM7XKGd2f53EXnPCmrIugK7ZtLJXcLIifEUrMb+
\r
109 U24dAALskx5nnZ2mZaO3racmMCoZpcOdMTr5fbN17f32EGCprgESAuELwTQuitWH
\r
110 97AI62v8Gj4ZYFeybrJRe9vST3hBJznkeQUYH2XHPTcVb6xOjyKbe412hUCqiDj4
\r
111 i5xrYgdINwNQcozxHQ5E5PbV6LGGt8YPRijU2KgAxND0RVvkjypJBIMADm/+HaYS
\r
112 ZLn4jJx8duApYR0use2ptSJjsoWgzxmQlWaB88Yf2X/OqUdum3xN7Gmt13yF4TWq
\r
113 ougIkKhKpK68W84N7xmhIgSv88g4/DzWGgHp7djL765T569eaH1tFx+c6kAaooIJ
\r
114 maoq2h9K976SAynKTscj+hK7CVysNjcItTEsF3PqXyWIAusN/TicSlA4wRbtMLnU
\r
115 nfOWUSSbTHoFS6A0q8rt1Ufn308GgMEDtV3tSZsXZ/t34m584yEdcY/eehMu6LEw
\r
116 4/4kuQ5Q393Mo3UjpayviW8zwA7JMdPwYCKf8T8uxHrqujydiSyhyb81jNuzxap5
\r
117 J7L4RSO8nonStcKMKX8gQCVrslYjGWW4dT93TYJ4PWInTAQfcFLw4dcP5nRE7dli
\r
118 PxsSehc4a7I5L01rW/eW
\r
120 -----END PGP SIGNATURE-----
\r
122 --------------enig11C0BE8A616BDB95A10B1CAA--
\r