From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Brett Viren <brett.viren@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Problems with Maildir and files moving from new/ to cur/
Date: Tue, 09 Feb 2010 18:20:01 +0100 [thread overview]
Message-ID: <87ljf2jpha.fsf@steelpick.localdomain> (raw)
In-Reply-To: <46263c601002090738k6a8f0e92v807b535918cbc7a5@mail.gmail.com>
On Tue, 9 Feb 2010 10:38:04 -0500, Brett Viren <brett.viren@gmail.com> wrote:
> Hi,
>
> I use procmail to prefilter mail into various sub groups of a Maildir.
> This Maildir is served by dovecot IMAP and is also visible to
> notmuch. I run "notmuch new" followed by "notmuch tag -inbox -unread
> tag:inbox" (I use GNUS to do my reading and don't want these tags in
> the way the few times I run notmuch for reading) every 10 minutes from
> cron. I often will check my email before the cron job gets a chance
> to run and vice versa.
>
> The problem I have is that this race condition means that sometimes
> notmuch will index a message as being under the Maildir/.<topic>/new/
> subdirectory, I then read it and it is moved to Maildir/.<topic>/cur/
> (I think that is what is happening). Then when I do a search, notmuch
> returns a file that is no longer around.
>
> This may not be an issue with notmuch, per se, but does anyone have
> any suggestions to make this work more smoothly?
Hi,
I'm afraid that with current version there is no solution for this.
There were some proposals to tell notmuch which files you want to index
and use this functionality to run indexing right on delivery on when a
rename is detected (e.g. by inotify). See
id:1264719647-sup-9540@ben-laptop for details. AFAIK nobody have sent
patches for this yet.
Cheers,
Michal
next prev parent reply other threads:[~2010-02-09 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 15:38 Problems with Maildir and files moving from new/ to cur/ Brett Viren
2010-02-09 17:20 ` Michal Sojka [this message]
2010-02-10 0:34 ` 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=87ljf2jpha.fsf@steelpick.localdomain \
--to=sojkam1@fel.cvut.cz \
--cc=brett.viren@gmail.com \
--cc=notmuch@notmuchmail.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).