From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 273DC429E34 for ; Wed, 4 Sep 2013 07:54:00 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.799 X-Spam-Level: X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 EH94IdXveUO9 for ; Wed, 4 Sep 2013 07:53:53 -0700 (PDT) Received: from mail-ea0-f173.google.com (mail-ea0-f173.google.com [209.85.215.173]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 0DC90429E32 for ; Wed, 4 Sep 2013 07:53:52 -0700 (PDT) Received: by mail-ea0-f173.google.com with SMTP id g10so244085eak.18 for ; Wed, 04 Sep 2013 07:53:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:in-reply-to:references:date:message-id:mime-version :content-type; bh=9cE+Yqc1TndHv21Yhup9mPeWZSmIFqzwpEn4Aejrq1Q=; b=XCUt70g2zYEnFEFH6krv/Wex/Yd3kElsvIbBqmpgc6aW/XYk3nnOqC6Roh8S+RSGGB ErDwcIW9PzzDhrmeOygdCJ80/WUh2DXpGojpwsNnw9Co59T1Kzhp3q7aOj+qoduOx3aM IOLWf2VIhHAhc83AE4auTpO5n84UF8esXfHY+m0s22lty1W0Uv0WSdTaxA6dMxIdnxh7 jNMtsBWyWSmc7AtUWnMN8Fc2twS1z4LqT7mqBf0gV21iHmXN9nOKur/QdiVqpmR15X92 Ie5NahEhsNE/66ZBp+y91z63qZLBFG62r5mJq+jfFTXIK4OFEi3Ygkejjkn9eQ3MTTHH d+lw== X-Received: by 10.14.89.72 with SMTP id b48mr5395592eef.43.1378306430018; Wed, 04 Sep 2013 07:53:50 -0700 (PDT) Received: from localhost (f049134146.adsl.alicedsl.de. [78.49.134.146]) by mx.google.com with ESMTPSA id a1sm40662876eem.1.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Sep 2013 07:53:49 -0700 (PDT) From: Sebastian Schwarz To: notmuch mailing list Subject: Re: proposal to remove contrib/notmuch-vim and contrib/notmuch-deliver In-Reply-To: <87a9jsriii.fsf@zancas.localnet> References: <87ioygrkhj.fsf@zancas.localnet> <87a9jsriii.fsf@zancas.localnet> Date: Wed, 04 Sep 2013 16:53:44 +0200 Message-ID: <874na0y6x3.fsf@pineapple.i-did-not-set--mail-host-address--so-tickle-me> MIME-Version: 1.0 Content-Type: text/plain 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, 04 Sep 2013 14:54:00 -0000 Hello, On 2013-04-09, David Bremner wrote: > David Belohrad 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. Regards, Sebastian