From: Mark Walters <markwalters1009@gmail.com>
To: Sebastian Schwarz <seschwar@gmail.com>,
notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: proposal to remove contrib/notmuch-vim and contrib/notmuch-deliver
Date: Thu, 05 Sep 2013 10:12:36 +0100 [thread overview]
Message-ID: <87r4d3r5rv.fsf@qmul.ac.uk> (raw)
In-Reply-To: <874na0y6x3.fsf@pineapple.i-did-not-set--mail-host-address--so-tickle-me>
On Wed, 04 Sep 2013, Sebastian Schwarz <seschwar@gmail.com> wrote:
> Hello,
>
> On 2013-04-09, David Bremner <david@tethera.net> wrote:
>> David Belohrad <david@belohrad.ch> writes:
>>
>>> is actually someone using notmuch deliver?
>
> I am using notmuch-deliver with maildrop. This allows me to
> filter and tag based on any header field of the message.
>
>>> [...]
>>
>> notmuch-deliver is replaced by notmuch insert
>
> Because of the way notmuch-insert(1) deals with failure it is
> entirely useless to me. From the manual page:
>
>> This command returns exit status 0 if the message was
>> successfully added to the mail directory, even if the message
>> could not be indexed and added to the notmuch database.
>
> This means that if the index is locked when a message is
> delivered it will not be tagged appropriately. The message will
> still be written to disk. However if you rely on the tags to
> find the message it effectively gets lost.
>
> notmuch-insert(1) should fail if it isn't able to successfully
> perform all of the following three tasks:
>
> - write the message to disk
> - index the message
> - tag the message
>
> It should return with a non-0 exit status and let its caller --
> the MDA or another notmuch client -- handle the failure, since
> notmuch-insert(1) cannot make any guarantees by itself anyway.
> This would usually make an MDA retry delivering the message at a
> later time.
I think this is a good reason not to remove notmuch-deliver until there
is at least an option to insert to fail in this case. A step in this
direction was made in
id:1374365254-13227-1-git-send-email-novalazy@gmail.com but this is not
a complete solution and is not in mainline anyway.
Best wishes
Mark
>
> Regards,
> Sebastian
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2013-09-05 9:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 9:42 proposal to remove contrib/notmuch-vim and contrib/notmuch-deliver David Bremner
2013-09-04 9:45 ` Tomi Ollila
2013-09-04 9:50 ` Patrick Totzke
2013-09-04 9:50 ` David Belohrad
2013-09-04 10:25 ` David Bremner
2013-09-04 12:07 ` Suvayu Ali
2013-09-04 14:53 ` Sebastian Schwarz
2013-09-05 9:12 ` Mark Walters [this message]
2013-09-04 11:21 ` Amadeusz Żołnowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r4d3r5rv.fsf@qmul.ac.uk \
--to=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=seschwar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).