1 Return-Path: <m.walters@qmul.ac.uk>
\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 89D59431FDD
\r
6 for <notmuch@notmuchmail.org>; Thu, 5 Sep 2013 02:12:48 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=1.401 tagged_above=-999 required=5
\r
12 tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,
\r
13 FREEMAIL_REPLY=2.499, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_MED=-2.3]
\r
15 Received: from olra.theworths.org ([127.0.0.1])
\r
16 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
17 with ESMTP id gddc+VnxDFVk for <notmuch@notmuchmail.org>;
\r
18 Thu, 5 Sep 2013 02:12:44 -0700 (PDT)
\r
19 Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])
\r
20 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
21 (No client certificate requested)
\r
22 by olra.theworths.org (Postfix) with ESMTPS id BE306431FDB
\r
23 for <notmuch@notmuchmail.org>; Thu, 5 Sep 2013 02:12:43 -0700 (PDT)
\r
24 Received: from smtp.qmul.ac.uk ([138.37.6.40])
\r
25 by mail2.qmul.ac.uk with esmtp (Exim 4.71)
\r
26 (envelope-from <m.walters@qmul.ac.uk>)
\r
27 id 1VHVcD-0007zE-Cv; Thu, 05 Sep 2013 10:12:40 +0100
\r
28 Received: from 93-97-24-31.zone5.bethere.co.uk ([93.97.24.31] helo=localhost)
\r
29 by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.71)
\r
30 (envelope-from <m.walters@qmul.ac.uk>)
\r
31 id 1VHVcC-00081u-SN; Thu, 05 Sep 2013 10:12:37 +0100
\r
32 From: Mark Walters <markwalters1009@gmail.com>
\r
33 To: Sebastian Schwarz <seschwar@gmail.com>,
\r
34 notmuch mailing list <notmuch@notmuchmail.org>
\r
35 Subject: Re: proposal to remove contrib/notmuch-vim and
\r
36 contrib/notmuch-deliver
\r
38 <874na0y6x3.fsf@pineapple.i-did-not-set--mail-host-address--so-tickle-me>
\r
39 References: <87ioygrkhj.fsf@zancas.localnet>
\r
40 <uaxa9jsncfm.fsf@beesknees.cern.ch>
\r
41 <87a9jsriii.fsf@zancas.localnet>
\r
42 <874na0y6x3.fsf@pineapple.i-did-not-set--mail-host-address--so-tickle-me>
\r
43 User-Agent: Notmuch/0.15.2+269~g01f5508 (http://notmuchmail.org) Emacs/23.4.1
\r
44 (x86_64-pc-linux-gnu)
\r
45 Date: Thu, 05 Sep 2013 10:12:36 +0100
\r
46 Message-ID: <87r4d3r5rv.fsf@qmul.ac.uk>
\r
48 Content-Type: text/plain; charset=us-ascii
\r
49 X-Sender-Host-Address: 93.97.24.31
\r
50 X-QM-SPAM-Info: Sender has good ham record. :)
\r
51 X-QM-Body-MD5: eb670bd230e51f57adebafb7d62a89c8 (of first 20000 bytes)
\r
52 X-SpamAssassin-Score: 0.6
\r
53 X-SpamAssassin-SpamBar: /
\r
54 X-SpamAssassin-Report: The QM spam filters have analysed this message to
\r
56 spam. We require at least 5.0 points to mark a message as spam.
\r
57 This message scored 0.6 points. Summary of the scoring:
\r
58 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail
\r
59 provider * (markwalters1009[at]gmail.com)
\r
60 * 1.0 FREEMAIL_REPLY From and body contain different freemails
\r
61 * -0.4 AWL AWL: From: address is in the auto white-list
\r
62 X-QM-Scan-Virus: ClamAV says the message is clean
\r
63 X-BeenThere: notmuch@notmuchmail.org
\r
64 X-Mailman-Version: 2.1.13
\r
66 List-Id: "Use and development of the notmuch mail system."
\r
67 <notmuch.notmuchmail.org>
\r
68 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
69 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
70 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
71 List-Post: <mailto:notmuch@notmuchmail.org>
\r
72 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
73 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
74 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
75 X-List-Received-Date: Thu, 05 Sep 2013 09:12:48 -0000
\r
78 On Wed, 04 Sep 2013, Sebastian Schwarz <seschwar@gmail.com> wrote:
\r
81 > On 2013-04-09, David Bremner <david@tethera.net> wrote:
\r
82 >> David Belohrad <david@belohrad.ch> writes:
\r
84 >>> is actually someone using notmuch deliver?
\r
86 > I am using notmuch-deliver with maildrop. This allows me to
\r
87 > filter and tag based on any header field of the message.
\r
91 >> notmuch-deliver is replaced by notmuch insert
\r
93 > Because of the way notmuch-insert(1) deals with failure it is
\r
94 > entirely useless to me. From the manual page:
\r
96 >> This command returns exit status 0 if the message was
\r
97 >> successfully added to the mail directory, even if the message
\r
98 >> could not be indexed and added to the notmuch database.
\r
100 > This means that if the index is locked when a message is
\r
101 > delivered it will not be tagged appropriately. The message will
\r
102 > still be written to disk. However if you rely on the tags to
\r
103 > find the message it effectively gets lost.
\r
105 > notmuch-insert(1) should fail if it isn't able to successfully
\r
106 > perform all of the following three tasks:
\r
108 > - write the message to disk
\r
109 > - index the message
\r
110 > - tag the message
\r
112 > It should return with a non-0 exit status and let its caller --
\r
113 > the MDA or another notmuch client -- handle the failure, since
\r
114 > notmuch-insert(1) cannot make any guarantees by itself anyway.
\r
115 > This would usually make an MDA retry delivering the message at a
\r
118 I think this is a good reason not to remove notmuch-deliver until there
\r
119 is at least an option to insert to fail in this case. A step in this
\r
120 direction was made in
\r
121 id:1374365254-13227-1-git-send-email-novalazy@gmail.com but this is not
\r
122 a complete solution and is not in mainline anyway.
\r
132 > _______________________________________________
\r
133 > notmuch mailing list
\r
134 > notmuch@notmuchmail.org
\r
135 > http://notmuchmail.org/mailman/listinfo/notmuch
\r