1 Return-Path: <jason@jasonwoof.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 olra.theworths.org (Postfix) with ESMTP id B1954429E30
\r
6 for <notmuch@notmuchmail.org>; Mon, 29 Aug 2011 23:22:38 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\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 JonPQDwSPwBa for <notmuch@notmuchmail.org>;
\r
16 Mon, 29 Aug 2011 23:22:38 -0700 (PDT)
\r
17 Received: from mail-vx0-f181.google.com (mail-vx0-f181.google.com
\r
18 [209.85.220.181]) (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 3E1E8429E28
\r
21 for <notmuch@notmuchmail.org>; Mon, 29 Aug 2011 23:22:38 -0700 (PDT)
\r
22 Received: by vxh7 with SMTP id 7so2835300vxh.26
\r
23 for <notmuch@notmuchmail.org>; Mon, 29 Aug 2011 23:22:35 -0700 (PDT)
\r
24 Received: by 10.52.174.115 with SMTP id br19mr3963139vdc.132.1314685354992;
\r
25 Mon, 29 Aug 2011 23:22:34 -0700 (PDT)
\r
26 Received: from lemote.jasonwoof.com
\r
27 (pool-71-161-83-125.cncdnh.east.myfairpoint.net [71.161.83.125])
\r
28 by mx.google.com with ESMTPS id l9sm521872vdv.26.2011.08.29.23.22.33
\r
29 (version=TLSv1/SSLv3 cipher=OTHER);
\r
30 Mon, 29 Aug 2011 23:22:34 -0700 (PDT)
\r
31 Date: Tue, 30 Aug 2011 02:22:29 -0400
\r
32 From: Jason Woofenden <jason@jasonwoof.com>
\r
33 To: notmuch@notmuchmail.org
\r
34 Subject: Re: How does notmuch detect the presence of attachments?
\r
35 Message-ID: <20110830062229.GC8590@lemote.jasonwoof.com>
\r
36 Mail-Followup-To: notmuch@notmuchmail.org
\r
38 <CAJ+wP3X5SxPPLyy=jbVMW5QZvuZSq5Vkt=6tVnL_Sd=W9Ys_SA@mail.gmail.com>
\r
39 <4E565A61.7040600@fifthhorseman.net>
\r
41 Content-Type: text/plain; charset=us-ascii
\r
42 Content-Disposition: inline
\r
43 In-Reply-To: <4E565A61.7040600@fifthhorseman.net>
\r
44 User-Agent: Mutt/1.5.21 (2010-09-15)
\r
45 X-BeenThere: notmuch@notmuchmail.org
\r
46 X-Mailman-Version: 2.1.13
\r
48 List-Id: "Use and development of the notmuch mail system."
\r
49 <notmuch.notmuchmail.org>
\r
50 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
51 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
52 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
53 List-Post: <mailto:notmuch@notmuchmail.org>
\r
54 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
55 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
56 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
57 X-List-Received-Date: Tue, 30 Aug 2011 06:22:38 -0000
\r
62 > application/pdf=pdf2txt /dev/stdin
\r
64 Sounds awesome. I'd love the feature, and this sounds like a good
\r
65 way to do it. Or maybe we should use a mailcap file like mutt
\r
66 does... it has some useful features like nametemplate and maybe
\r
70 > Starting with an initially empty set of textconverters seems reasonable
\r
71 > and safe to me, and people could set up their own if they're interested.
\r
73 I also think starting empty is the right thing to do. We don't want
\r
74 to be the bad guys if there's a security exploit in one of the
\r
78 I as a user can decide that I'd like to run `abiword -t txt` on
\r
79 application/msword and application/rtf mime parts. If there's a
\r
80 security issue with abiword that someone can exploit by sending me
\r
81 an e-mail, then FML, but at least I won't be mad at the notmuch
\r