Return-Path: <tassilo@member.fsf.org>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id 2AEE1431FC0
	for <notmuch@notmuchmail.org>; Sun, 22 Nov 2009 23:42:14 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
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 l2gU75IyjZba for <notmuch@notmuchmail.org>;
	Sun, 22 Nov 2009 23:42:13 -0800 (PST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.194])
	by olra.theworths.org (Postfix) with ESMTP id 6E8BB431FBC
	for <notmuch@notmuchmail.org>; Sun, 22 Nov 2009 23:42:13 -0800 (PST)
Received: from deliver.uni-koblenz.de (deliver.uni-koblenz.de [141.26.64.15])
	by mx.perfora.net (node=mxus0) with ESMTP (Nemesis)
	id 0MN2S8-1NEeLs1CvY-007EOf for notmuch@notmuchmail.org;
	Mon, 23 Nov 2009 02:42:12 -0500
Received: from localhost (localhost [127.0.0.1])
	by deliver.uni-koblenz.de (Postfix) with ESMTP id 48A8578A30BD;
	Mon, 23 Nov 2009 08:42:10 +0100 (CET)
Received: from deliver.uni-koblenz.de ([127.0.0.1])
	by localhost (deliver.uni-koblenz.de [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 02871-10; Mon, 23 Nov 2009 08:42:09 +0100 (CET)
X-CHKRCPT: Envelopesender noch tassilo@member.fsf.org
Received: from thinkpad.tsdh.de (unknown [141.26.95.131])
	by deliver.uni-koblenz.de (Postfix) with ESMTP id A550078A30BB;
	Mon, 23 Nov 2009 08:42:09 +0100 (CET)
From: Tassilo Horn <tassilo@member.fsf.org>
To: Carl Worth <cworth@cworth.org>
References: <877hti71f4.fsf@thinkpad.tsdh.de>
	<87my2dg8ww.fsf@yoom.home.cworth.org>
Date: Mon, 23 Nov 2009 08:42:09 +0100
In-Reply-To: <87my2dg8ww.fsf@yoom.home.cworth.org> (Carl Worth's message of
	"Mon, 23 Nov 2009 05:30:23 +0100")
Message-ID: <87fx85it66.fsf@thinkpad.tsdh.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Virus-Scanned: amavisd-new at uni-koblenz.de
Cc: notmuch@notmuchmail.org
Subject: Re: [notmuch] How to index /var/spool/mail with notmuch
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2009 07:42:14 -0000

Carl Worth <cworth@cworth.org> writes:

Hi Carl,

>> Unfortunately, there are some dovecot internal files, which should
>> neither be indexed by notmuch, and which have 600 permissions for the
>> mail user.  And that's where notmuch errors and stops indexing. :-(
>
> Hi Tassilo, welcome to notmuch!
>
> I'm glad you found a workaround for this problem, (thanks Jed!).

Trying out notmuch already cashed out. ;-)

> But perhaps these errors should be made into warnings instead? Any
> thoughts on that anyone?

I think so.  For other dovecot internal index files it already says
something like "Ignoring non-mail file foobar.idx" and simply skips that
file.  I think that's the right thing to do for files where it has no
read permissions for, too.

>> All "real" mail files are named "u.<number>", so it would be cool if
>> I could provide a pattern to notmuch matching all files I'd like to
>> index.  And maybe the other way round (a blacklist pattern) would be
>> useful, too.
>
> I've been planning on having a blacklist pattern for a while.
> Originally, the only difficulty in implementing it was that we had
> nowhere to store configuration information.  But we have a
> configuration file now, so this would be a pretty easy thing to
> implement.
>
> It's not as obvious that a whitelist pattern would be as widely
> useful, but it would be possible too.

Well, for dovecot users using the dbox format, a whitelist pattern would
be much simpler because of the coherent mail file naming.  But I could
live with a blacklist pattern, too.

Bye,
Tassilo