[ANN] notmuch-deliver

[ANN] notmuch-deliver

[Ali Polatel]

[-- Attachment #1: Type: text/plain, Size: 422 bytes --]


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.

Git: git://github.com/alip/notmuch-deliver.git
Readme: http://github.com/alip/notmuch-deliver/blob/master/README.mkd

-- 
Regards,
Ali Polatel

[-- Attachment #2: Type: application/pgp-signature, Size: 195 bytes --]

Re: [ANN] notmuch-deliver

[Carl Worth]

[-- Attachment #1: Type: text/plain, Size: 865 bytes --]

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. 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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANN] notmuch-deliver

[Ali Polatel]

[-- Attachment #1: Type: text/plain, Size: 1764 bytes --]

On Mon, 08 Nov 2010 09:50:46 -0800, Carl Worth <cworth@cworth.org> 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. 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.

You're welcome!
 
> What's the best way to advertise this to potential users?

Never thought about it honestly, I've just been using for sometime now
and I'm quite happy with the results.
 
> Should we include a separate utils directory in the notmuch repository
> with auxiliary programs like this?

Well, such programs should live in their own repositories. One big git
repository with everything in it is just against the idea of distributed
source control management imo.
 
> Or should we implement this functionality within the notmuch binary
> itself?

We can think about this when the tool gets enough testing in my opinion.
At this stage I don't think it's worth the hassle to include the
functionality into the notmuch binary itself, but this is my personal
opinion and I don't really know how many people in the outer-space uses
this program.

> I'm open to suggestions.

Oh well, I'm open to more vodka.

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

+1, but I won't be writing any documentation since I'm a mighty slacker.
 
> Thanks again,

You're welcome again!

> -Carl
> 
> -- 
> carl.d.worth@intel.com

-- 
Regards,
Ali Polatel

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: [ANN] notmuch-deliver

[Thomas Schwinge]

[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

Hallo!

On Mon, 08 Nov 2010 09:50:46 -0800, Carl Worth <cworth@cworth.org> 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. 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?

I recently put a description and link onto the notmuch web pages.

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

I wouldn't do so.  But that is not a very strong opinion of mine.

In general, I like it if I see a repository containing one specific tool,
and that one cleanly interfaces through specified interfaces with another
tool.  These two things are no longer as cleanly visible once
notmuch-deliver was part of the notmuch repository.


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

That's another option, of course.  (And a separate discussion.)


> 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.

I'm working on that (and other parts of the web pages) as I go on with
exploring the ``notmuch world''.

I'll also take the liberty to put stuff from the mailing list or IRC
discussions into web pages, for we have to document this notmuch beast
;-), and it's better to have a generic place to refer people to, instead
of discussing the same things more than once.


If someone disagrees with any of this, I'm open to discuss these items.


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

Re: [ANN] notmuch-deliver

[Felipe Contreras]

On Mon, Nov 8, 2010 at 7:50 PM, Carl Worth <cworth@cworth.org> 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. 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,

I think this should be part of notmuch itself, and there should be a
configuration to use this as Fcc, instead of relying on the mail
composer. This way both emacs and vim interfaces would share the same
configuration regarding the Fcc/Bcc preference.

-- 
Felipe Contreras

Re: [ANN] notmuch-deliver

[Austin Clements]

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

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 <cworth@cworth.org> 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. 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
>
>

[-- Attachment #2: Type: text/html, Size: 2059 bytes --]

Re: [ANN] notmuch-deliver

[Carl Worth]

[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]

On Tue, 11 Jan 2011 12:46:38 +0100, Thomas Schwinge <thomas@schwinge.name> wrote:
> > What's the best way to advertise this to potential users?
> 
> I recently put a description and link onto the notmuch web pages.

Great. Thanks for doing this.

> > Should we include a separate utils directory in the notmuch repository
> > with auxiliary programs like this?
> 
> I wouldn't do so.  But that is not a very strong opinion of mine.

Well, your opinion matters quite a bit in a case like this where it's
your utility. I guess I was simply offering the "hosting" of the
repository if you thought it would be useful. I understand the desire to
keep things cleanly packaged separately.

> I'll also take the liberty to put stuff from the mailing list or IRC
> discussions into web pages, for we have to document this notmuch beast
> ;-), and it's better to have a generic place to refer people to, instead
> of discussing the same things more than once.

Yes! Please continue to improve the web pages, and everyone, please feel
free to grab useful stuff from the lists or IRC and stuff them into the
web pages.

Also, if things should get shoved into the notmuch man page, then we
should do that too.

-Carl

-- 
carl.d.worth@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANN] notmuch-deliver

[Carl Worth]

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

On Tue, 11 Jan 2011 16:01:00 +0200, Felipe Contreras <felipe.contreras@gmail.com> wrote:
> I think this should be part of notmuch itself,

I'll be happy to see any proposed additions for this. (And to the extent
that some of this functionality exists in patches already proposed and
just waiting for me, then I'm already happy about that too!)

> and there should be a
> configuration to use this as Fcc, instead of relying on the mail
> composer. This way both emacs and vim interfaces would share the same
> configuration regarding the Fcc/Bcc preference.

Sharing the configuration as much as possible is definitely good.

But Fcc is going to have to rely quite a bit on the mail
composer. Currently, notmuch isn't involved at all in the sending of a
mail, and it's not until a mail is actually sent that it's time to
deliver the message to the Fcc location. So even getting notmuch to
become informed about the message at Fcc time will require modification
of the mail composer.

-Carl

-- 
carl.d.worth@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [ANN] notmuch-deliver

[Carl Worth]

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

On Wed, 12 Jan 2011 15:50:24 -0500, Austin Clements <amdragon@mit.edu> wrote:
> 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.

The idea has definitely been floated before. If I search for:

	notmuch search to:notmuch@notmuchmail.org inotify

in my collection I see 5 messages sent to the list, (other than
yours). But none of those include any code that I have seen.

It sounds like playing with inotify and notmuch might make a fun weekend
project for somebody. Is anyone looking for something like that?

-Carl

-- 
carl.d.worth@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]