Message-ID: <4E5D5B7D.7050104@fifthhorseman.net>
Date: Tue, 30 Aug 2011 17:51:57 -0400
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20110807 Icedove/5.0
MIME-Version: 1.0
To: notmuch@notmuchmail.org
Subject: Re: How does notmuch detect the presence of attachments?
References:
 <CAJ+wP3X5SxPPLyy=jbVMW5QZvuZSq5Vkt=6tVnL_Sd=W9Ys_SA@mail.gmail.com>
	<4E565A61.7040600@fifthhorseman.net>
	<20110830062229.GC8590@lemote.jasonwoof.com>
In-Reply-To: <20110830062229.GC8590@lemote.jasonwoof.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enig11C0BE8A616BDB95A10B1CAA"
Precedence: list
Reply-To: notmuch <notmuch@notmuchmail.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig11C0BE8A616BDB95A10B1CAA
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 08/30/2011 02:22 AM, Jason Woofenden wrote:
>> [...]
>>
>>  [textconverters]
>>  application/pdf=3Dpdf2txt /dev/stdin
>=20
> Sounds awesome. I'd love the feature, and this sounds like a good
> way to do it. Or maybe we should use a mailcap file like mutt
> does... it has some useful features like nametemplate and maybe
> test.

hm, interesting suggestion.   I don't know enough about mailcap to know
whether it makes more sense to adopt it directly or to use a
notmuch-specific configuration.

One difference: mailcap seems to be about displaying/editing data to the
user (including, for example, opening a graphical window to display a
JPEG), whereas we need to set up a mechanism to convert whatever kind of
document we get into plain text to feed it into xapian.  So we couldn't
fully piggy-back on the mailcap infrastructure, if i'm reading the
mailcap documentation correctly.  notmuch would need to use its own
mime-types file.

Anyone with more experience with this stuff (or stronger opinions) have
any insight on what approach makes more sense?

> I as a user can decide that I'd like to run `abiword -t txt` on
> application/msword and application/rtf mime parts. If there's a
> security issue with abiword that someone can exploit by sending me
> an e-mail, then FML, but at least I won't be mad at the notmuch
> developers.

exactly :)

	--dkg


--------------enig11C0BE8A616BDB95A10B1CAA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQJ8BAEBCgBmBQJOXVt9XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD
Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpFIsP/0hnLZiOJWs0qoBjuugvGg+r
dkDJ5LiwdE9DA6vZdCJjzENiviM7XKGd2f53EXnPCmrIugK7ZtLJXcLIifEUrMb+
U24dAALskx5nnZ2mZaO3racmMCoZpcOdMTr5fbN17f32EGCprgESAuELwTQuitWH
97AI62v8Gj4ZYFeybrJRe9vST3hBJznkeQUYH2XHPTcVb6xOjyKbe412hUCqiDj4
i5xrYgdINwNQcozxHQ5E5PbV6LGGt8YPRijU2KgAxND0RVvkjypJBIMADm/+HaYS
ZLn4jJx8duApYR0use2ptSJjsoWgzxmQlWaB88Yf2X/OqUdum3xN7Gmt13yF4TWq
ougIkKhKpK68W84N7xmhIgSv88g4/DzWGgHp7djL765T569eaH1tFx+c6kAaooIJ
maoq2h9K976SAynKTscj+hK7CVysNjcItTEsF3PqXyWIAusN/TicSlA4wRbtMLnU
nfOWUSSbTHoFS6A0q8rt1Ufn308GgMEDtV3tSZsXZ/t34m584yEdcY/eehMu6LEw
4/4kuQ5Q393Mo3UjpayviW8zwA7JMdPwYCKf8T8uxHrqujydiSyhyb81jNuzxap5
J7L4RSO8nonStcKMKX8gQCVrslYjGWW4dT93TYJ4PWInTAQfcFLw4dcP5nRE7dli
PxsSehc4a7I5L01rW/eW
=+kTb
-----END PGP SIGNATURE-----

--------------enig11C0BE8A616BDB95A10B1CAA--