From: "Alexei Gilchrist" <te100@runbox.com>
To: "David Bremner" <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch ignoring alot of emails
Date: Sun, 31 Mar 2019 10:53:27 +1100 [thread overview]
Message-ID: <F4D8E8F2-CD89-43B3-8811-A924DC101A6A@runbox.com> (raw)
In-Reply-To: <877ecgy505.fsf@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]
>> When I run notmuch I get a bunch (hundreds) of emails that are
>> ignored
>> with:
>>
>> Note: Ignoring non-mail file: ...
>>
>> The files are valid maildir files but have a paragraph somewhere in
>> the
>> body where someone has written "From ".
>>
>
> And do they also have have a line starting with "From " as the first
> line? This makes them mbox files. The second "From " makes them mbox
> files with multiple messages. Notmuch thinks your MDA (the thing that
> made those files) is misconfigured, assuming my guess about the format
> is correct.
Every message file begins with “From “. This is true of all messages
downloaded by both offlineimap (with type = Maildir) and mbsync.
neomutt has no issues dealing with these files as maildir and mu has no
issues indexing them either. I’m assuming that stating with “From
“ is part of the maildir spec.
The problem occurs specifically with notmuch. If someone sends a message
with a line that begins with “From “ in the *body* then it confuses
notmuch.
mu can correctly index these messages but my mu is linked against
libgmime-2.6, my notmuch (0.28.3) is linked against libgmime-3.0.
>> Is there a fix to force the recognition of maildir files in this
>> case? I
>> thought this was a solved problem with gmime since 2.6.7.
>
> There is not currently a way to do that. It's not a GMime problem,
> it's
> a design choice of notmuch to avoid parsing multiple message
> mbox's. That was originally added as a safety feature, and I think it
> should probably stay the default. If someone wants work on adding a
> configuration switch I can point them in the right direction.
This is a poor design decision. It means anyone on the internet can
break your mail setup simply by sending a message with a line starting
with “From “.
(and using usual quoted-printable Content-Transfer-Encoding).
Try it. Send yourself a message with the line “From bad parsing comes
chaos” and see if your notmuch can find it. My version can’t.
[-- Attachment #2: Type: text/html, Size: 3027 bytes --]
next prev parent reply other threads:[~2019-03-30 23:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 6:45 notmuch ignoring alot of emails Alexei Gilchrist
2019-03-30 11:29 ` David Bremner
2019-03-30 23:53 ` Alexei Gilchrist [this message]
2019-03-31 4:06 ` David Bremner
2019-03-31 8:52 ` Tomi Ollila
2019-03-31 11:00 ` Tomas Nordin
2019-03-31 22:02 ` Alexei Gilchrist
2019-03-31 23:27 ` David Bremner
2019-06-28 17:16 ` Alvaro Herrera
2019-06-28 20:11 ` Alvaro Herrera
2019-06-29 19:03 ` David Bremner
2019-06-29 19:09 ` David Bremner
2019-07-01 15:26 ` Alvaro Herrera
2019-06-30 17:29 ` Tomi Ollila
2019-07-01 15:36 ` Alvaro Herrera
2019-11-16 17:40 ` David Bremner
[not found] ` <87eey7szz6.fsf@eirikba.org>
2019-11-17 12:31 ` David Bremner
2019-11-17 13:46 ` David Bremner
[not found] ` <87blt9tdjj.fsf@eirikba.org>
2019-11-19 20:18 ` David Bremner
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=F4D8E8F2-CD89-43B3-8811-A924DC101A6A@runbox.com \
--to=te100@runbox.com \
--cc=david@tethera.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).