1 Return-Path: <tassilo@member.fsf.org>
\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 2AEE1431FC0
\r
6 for <notmuch@notmuchmail.org>; Sun, 22 Nov 2009 23:42:14 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id l2gU75IyjZba for <notmuch@notmuchmail.org>;
\r
11 Sun, 22 Nov 2009 23:42:13 -0800 (PST)
\r
12 Received: from mout.perfora.net (mout.perfora.net [74.208.4.194])
\r
13 by olra.theworths.org (Postfix) with ESMTP id 6E8BB431FBC
\r
14 for <notmuch@notmuchmail.org>; Sun, 22 Nov 2009 23:42:13 -0800 (PST)
\r
15 Received: from deliver.uni-koblenz.de (deliver.uni-koblenz.de [141.26.64.15])
\r
16 by mx.perfora.net (node=mxus0) with ESMTP (Nemesis)
\r
17 id 0MN2S8-1NEeLs1CvY-007EOf for notmuch@notmuchmail.org;
\r
18 Mon, 23 Nov 2009 02:42:12 -0500
\r
19 Received: from localhost (localhost [127.0.0.1])
\r
20 by deliver.uni-koblenz.de (Postfix) with ESMTP id 48A8578A30BD;
\r
21 Mon, 23 Nov 2009 08:42:10 +0100 (CET)
\r
22 Received: from deliver.uni-koblenz.de ([127.0.0.1])
\r
23 by localhost (deliver.uni-koblenz.de [127.0.0.1]) (amavisd-new,
\r
25 with ESMTP id 02871-10; Mon, 23 Nov 2009 08:42:09 +0100 (CET)
\r
26 X-CHKRCPT: Envelopesender noch tassilo@member.fsf.org
\r
27 Received: from thinkpad.tsdh.de (unknown [141.26.95.131])
\r
28 by deliver.uni-koblenz.de (Postfix) with ESMTP id A550078A30BB;
\r
29 Mon, 23 Nov 2009 08:42:09 +0100 (CET)
\r
30 From: Tassilo Horn <tassilo@member.fsf.org>
\r
31 To: Carl Worth <cworth@cworth.org>
\r
32 References: <877hti71f4.fsf@thinkpad.tsdh.de>
\r
33 <87my2dg8ww.fsf@yoom.home.cworth.org>
\r
34 Date: Mon, 23 Nov 2009 08:42:09 +0100
\r
35 In-Reply-To: <87my2dg8ww.fsf@yoom.home.cworth.org> (Carl Worth's message of
\r
36 "Mon, 23 Nov 2009 05:30:23 +0100")
\r
37 Message-ID: <87fx85it66.fsf@thinkpad.tsdh.de>
\r
38 User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux)
\r
40 Content-Type: text/plain; charset=us-ascii
\r
41 X-Virus-Scanned: amavisd-new at uni-koblenz.de
\r
42 Cc: notmuch@notmuchmail.org
\r
43 Subject: Re: [notmuch] How to index /var/spool/mail with notmuch
\r
44 X-BeenThere: notmuch@notmuchmail.org
\r
45 X-Mailman-Version: 2.1.12
\r
47 List-Id: "Use and development of the notmuch mail system."
\r
48 <notmuch.notmuchmail.org>
\r
49 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
50 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
51 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
52 List-Post: <mailto:notmuch@notmuchmail.org>
\r
53 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
54 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
55 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
56 X-List-Received-Date: Mon, 23 Nov 2009 07:42:14 -0000
\r
58 Carl Worth <cworth@cworth.org> writes:
\r
62 >> Unfortunately, there are some dovecot internal files, which should
\r
63 >> neither be indexed by notmuch, and which have 600 permissions for the
\r
64 >> mail user. And that's where notmuch errors and stops indexing. :-(
\r
66 > Hi Tassilo, welcome to notmuch!
\r
68 > I'm glad you found a workaround for this problem, (thanks Jed!).
\r
70 Trying out notmuch already cashed out. ;-)
\r
72 > But perhaps these errors should be made into warnings instead? Any
\r
73 > thoughts on that anyone?
\r
75 I think so. For other dovecot internal index files it already says
\r
76 something like "Ignoring non-mail file foobar.idx" and simply skips that
\r
77 file. I think that's the right thing to do for files where it has no
\r
78 read permissions for, too.
\r
80 >> All "real" mail files are named "u.<number>", so it would be cool if
\r
81 >> I could provide a pattern to notmuch matching all files I'd like to
\r
82 >> index. And maybe the other way round (a blacklist pattern) would be
\r
85 > I've been planning on having a blacklist pattern for a while.
\r
86 > Originally, the only difficulty in implementing it was that we had
\r
87 > nowhere to store configuration information. But we have a
\r
88 > configuration file now, so this would be a pretty easy thing to
\r
91 > It's not as obvious that a whitelist pattern would be as widely
\r
92 > useful, but it would be possible too.
\r
94 Well, for dovecot users using the dbox format, a whitelist pattern would
\r
95 be much simpler because of the coherent mail file naming. But I could
\r
96 live with a blacklist pattern, too.
\r