From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Ralph Seichter <abbot@monksofcool.net>, notmuch@notmuchmail.org
Subject: Re: Unexpected output of "notmuch new --quiet"
Date: Fri, 19 Apr 2019 12:02:24 -0400 [thread overview]
Message-ID: <87ftqex9tb.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87a7gmdrqo.fsf@ra.horus-it.com>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
On Fri 2019-04-19 15:55:27 +0200, Ralph Seichter wrote:
> * Daniel Kahn Gillmor:
>
>> Why is "non-mail file found" in my maildir such a low priority?
>
> Because I do not agree with Notmuch's notion of what a non-mail file
> is. All files the Dovecot server uses for its own metadata are placed
> outside of "cur", "new", and "tmp".
>
> My understanding of the Maildir structure is that only these three
> subfolders in a given directory may contain mail files, so I expect
> Notmuch, as a default behaviour, to ignore whatever is stored outside
> of these subfolders.
Hm, notmuch supports trees of maildirs as well, and nested maildirs,
none of which are part of the maildir spec aiui.
Also, as far as maildir goes, i think notmuch probably *shouldn't* be
looking at stuff in …/tmp/ -- right? otherwise it's liable to
occasionally access some half-written files.
I've personally done the (maybe bad) thing where i just drop a folder
full of RFC5322 .eml files anywhere inside my message store and run
"notmuch new" to ingest them. I'd be sad if those files went away, but
perhaps you're right that we should only be looking at are things within
any cur/ and new/ subfolders within the message archive.
That'd be an easy fix if there was no deployed base to worry about. Any
thoughts about how to make such a transition safe for existing users
like me?
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-04-19 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 20:38 Unexpected output of "notmuch new --quiet" Ralph Seichter
2019-04-17 23:29 ` David Bremner
2019-04-18 13:15 ` Ralph Seichter
2019-04-18 13:29 ` David Bremner
2019-04-18 13:52 ` Ralph Seichter
2019-04-19 1:13 ` David Bremner
2019-04-19 11:47 ` Ralph Seichter
2019-04-19 12:02 ` Ralph Seichter
2019-04-19 16:25 ` David Bremner
2019-04-19 23:35 ` Ralph Seichter
2019-04-19 7:03 ` Daniel Kahn Gillmor
2019-04-19 13:55 ` Ralph Seichter
2019-04-19 16:02 ` Daniel Kahn Gillmor [this message]
2019-04-19 23:28 ` David Bremner
2019-04-19 23:46 ` Ralph Seichter
2019-04-20 10:45 ` Eric
2019-04-20 13:21 ` Ralph Seichter
2019-04-20 14:19 ` David Bremner
2019-04-20 14:28 ` Ralph Seichter
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=87ftqex9tb.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=abbot@monksofcool.net \
--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).