1 Return-Path: <cworth@cworth.org>
\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 12913429E2B
\r
6 for <notmuch@notmuchmail.org>; Fri, 28 Jan 2011 14:02:58 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.99 tagged_above=-999 required=5
\r
12 tests=[ALL_TRUSTED=-1, T_MIME_NO_TEXT=0.01] 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 XYLB7pxvZzUE; Fri, 28 Jan 2011 14:02:56 -0800 (PST)
\r
16 Received: from yoom.home.cworth.org (localhost [127.0.0.1])
\r
17 by olra.theworths.org (Postfix) with ESMTP id E0BFD431FB6;
\r
18 Fri, 28 Jan 2011 14:02:52 -0800 (PST)
\r
19 Received: by yoom.home.cworth.org (Postfix, from userid 1000)
\r
20 id BD9252542CD; Sat, 29 Jan 2011 06:55:47 +1000 (EST)
\r
21 From: Carl Worth <cworth@cworth.org>
\r
22 To: Austin Clements <amdragon@mit.edu>, notmuch@notmuchmail.org
\r
23 Subject: Re: [ANN] notmuch-deliver
\r
24 In-Reply-To: <AANLkTikRMXM1=COCe8zJO9ziMGNoseG8tdf+=W98a0fA@mail.gmail.com>
\r
25 References: <86d3wig3sx.fsf@harikalardiyari.ev>
\r
26 <87pqufn1qh.fsf@yoom.home.cworth.org>
\r
27 <AANLkTikRMXM1=COCe8zJO9ziMGNoseG8tdf+=W98a0fA@mail.gmail.com>
\r
28 User-Agent: Notmuch/0.5 (http://notmuchmail.org) Emacs/23.2.1
\r
30 Date: Sat, 29 Jan 2011 06:55:47 +1000
\r
31 Message-ID: <87ei7wn3xo.fsf@yoom.home.cworth.org>
\r
33 Content-Type: multipart/signed; boundary="=-=-=";
\r
34 micalg=pgp-sha1; protocol="application/pgp-signature"
\r
35 X-BeenThere: notmuch@notmuchmail.org
\r
36 X-Mailman-Version: 2.1.13
\r
38 List-Id: "Use and development of the notmuch mail system."
\r
39 <notmuch.notmuchmail.org>
\r
40 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
41 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
42 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
43 List-Post: <mailto:notmuch@notmuchmail.org>
\r
44 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
45 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
46 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
47 X-List-Received-Date: Fri, 28 Jan 2011 22:02:58 -0000
\r
50 Content-Transfer-Encoding: quoted-printable
\r
52 On Wed, 12 Jan 2011 15:50:24 -0500, Austin Clements <amdragon@mit.edu> wrot=
\r
54 > Out of curiosity, has anyone considered using inotify to monitor maildirs
\r
55 > for new mail to hand to notmuch? For systems supporting inotify (or
\r
56 > equivalents), this would have the advantage of being compatible with any
\r
57 > delivery mechanism, be it a mail server, procmail, or emacs fcc'ing a
\r
60 The idea has definitely been floated before. If I search for:
\r
62 notmuch search to:notmuch@notmuchmail.org inotify
\r
64 in my collection I see 5 messages sent to the list, (other than
\r
65 yours). But none of those include any code that I have seen.
\r
67 It sounds like playing with inotify and notmuch might make a fun weekend
\r
68 project for somebody. Is anyone looking for something like that?
\r
73 carl.d.worth@intel.com
\r
76 Content-Type: application/pgp-signature
\r
78 -----BEGIN PGP SIGNATURE-----
\r
79 Version: GnuPG v1.4.10 (GNU/Linux)
\r
81 iD8DBQFNQy1T6JDdNq8qSWgRAjI6AJ4/1mmnQ+GD35OJaDJnJnwF2qT/ewCeIEjY
\r
82 kLB5Z2/riTz0IwRMeCudEoc=
\r
84 -----END PGP SIGNATURE-----
\r