From: Carl Worth <cworth@cworth.org>
To: Tassilo Horn <tassilo@member.fsf.org>, notmuch@notmuchmail.org
Subject: Re: How to index /var/spool/mail with notmuch
Date: Mon, 23 Nov 2009 05:30:23 +0100 [thread overview]
Message-ID: <87my2dg8ww.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <877hti71f4.fsf@thinkpad.tsdh.de>
On Sun, 22 Nov 2009 21:24:47 +0100, Tassilo Horn <tassilo@member.fsf.org> wrote:
> But I get some permission problems when trying to index /var/spool/mail.
> I was able to create a .notmuch/ directory in there with permissions set
> to 700 for my user. All mail files are readable for my user.
>
> 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!).
But perhaps these errors should be made into warnings instead? Any
thoughts on that anyone?
> 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.
-Carl
next prev parent reply other threads:[~2009-11-23 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-22 20:24 How to index /var/spool/mail with notmuch Tassilo Horn
2009-11-22 20:48 ` Jed Brown
2009-11-22 21:00 ` Tassilo Horn
2009-11-23 4:30 ` Carl Worth [this message]
2009-11-23 7:42 ` Tassilo Horn
2009-11-26 20:53 ` Carl Worth
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=87my2dg8ww.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=notmuch@notmuchmail.org \
--cc=tassilo@member.fsf.org \
/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).