Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 5632D42D2BD for ; Wed, 12 Jan 2011 12:50:29 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.698 X-Spam-Level: X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XUZbt0jjqA1H for ; Wed, 12 Jan 2011 12:50:27 -0800 (PST) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.216.181]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id BE4F442D2BA for ; Wed, 12 Jan 2011 12:50:27 -0800 (PST) Received: by qyk12 with SMTP id 12so1130853qyk.5 for ; Wed, 12 Jan 2011 12:50:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=jTaXR0wDSQz4XvEUpMZSc3LHSNhfW0DPSQBv7FdkwGU=; b=FRT+O2XTrfLxBUB9x/SE3l5Scty0wT9Ju2Str1b1iLHkb3OQUEC/k8oBq7wXEV3mqk 8J7TBZueSj1wUXh7OcEjlkppavRQhTb0sMgXjedqMQ12A8O7QqWo1S0kY+8FqJ6qmeaS emU08n17MLCf/wCdLycU1anAPE8bxwmHpOOI0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=Ljh4jiiGt2gxc4AMrq6p+zSPWhtb07bYqM9CgOvzBHyVxF3k5U0jbGavdCvPNis0J0 6/7FfHpMumgpn59U342LP/wte7YK/hui12nepXzqDM/b1cOjccqkUz01NWu8l5j5cD3V 3CoxCljSVSzMoKQtKp6GM6P2TKKZUfSsi7TPs= MIME-Version: 1.0 Received: by 10.229.224.196 with SMTP id ip4mr1191574qcb.230.1294865424414; Wed, 12 Jan 2011 12:50:24 -0800 (PST) Sender: amdragon@gmail.com Received: by 10.229.97.143 with HTTP; Wed, 12 Jan 2011 12:50:24 -0800 (PST) In-Reply-To: <87pqufn1qh.fsf@yoom.home.cworth.org> References: <86d3wig3sx.fsf@harikalardiyari.ev> <87pqufn1qh.fsf@yoom.home.cworth.org> Date: Wed, 12 Jan 2011 15:50:24 -0500 X-Google-Sender-Auth: HT753TQbzFiN-Zf1OLjRp0t3JdM Message-ID: Subject: Re: [ANN] notmuch-deliver From: Austin Clements To: notmuch@notmuchmail.org Content-Type: multipart/alternative; boundary=0016363b8e76a77b660499ac59a8 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2011 20:50:29 -0000 --0016363b8e76a77b660499ac59a8 Content-Type: text/plain; charset=ISO-8859-1 Out of curiosity, has anyone considered using inotify to monitor maildirs for new mail to hand to notmuch? For systems supporting inotify (or equivalents), this would have the advantage of being compatible with any delivery mechanism, be it a mail server, procmail, or emacs fcc'ing a maildir. On Mon, Nov 8, 2010 at 12:50 PM, Carl Worth wrote: > On Wed, 26 May 2010 17:01:34 +0300, Ali Polatel wrote: > > notmuch-deliver is a maildir delivery tool for notmuch mail indexer. It > > reads from standard input, delivers the mail to the specified maildir > > and adds it to the notmuch database. This is meant as a convenient > > alternative to running notmuch new after mail delivery. > > Thanks for sharing this, Ali. > > What's the best way to advertise this to potential users? > > Should we include a separate utils directory in the notmuch repository > with auxiliary programs like this? > > Or should we implement this functionality within the notmuch binary > itself? > > I'm open to suggestions. > > If nothing else, the notmuchmail.org web page should grow a section to > point to auxiliary programs like this that users might find helpful. > > Thanks again, > > -Carl > > -- > carl.d.worth@intel.com > > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > http://notmuchmail.org/mailman/listinfo/notmuch > > --0016363b8e76a77b660499ac59a8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Out of curiosity, has anyone considered using inotify to monitor maildirs f= or new mail to hand to notmuch? =A0For systems supporting inotify (or equiv= alents), this would have the advantage of being compatible with any deliver= y mechanism, be it a mail server, procmail, or emacs fcc'ing a maildir.=

On Mon, Nov 8, 2010 at 12:50 PM, Carl Worth = <cworth@cworth.or= g> wrote:
On Wed, 26 May 2010 17:01:34 +0300, Ali Polatel <alip@exherbo.org> wrote:
> notmuch-deliver is a maildir delivery tool for notmuch mail indexer. I= t
> reads from standard input, delivers the mail to the specified maildir<= br> > and adds it to the notmuch database. This is meant as a convenient
> alternative to running notmuch new after mail delivery.

Thanks for sharing this, Ali.

What's the best way to advertise this to potential users?

Should we include a separate utils directory in the notmuch repository
with auxiliary programs like this?

Or should we implement this functionality within the notmuch binary
itself?

I'm open to suggestions.

If nothing else, the n= otmuchmail.org web page should grow a section to
point to auxiliary programs like this that users might find helpful.

Thanks again,

-Carl

--
carl.d.worth@intel.com

_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


--0016363b8e76a77b660499ac59a8--