From: "Alexei Gilchrist" <te100@runbox.com>
To: "Tomas Nordin" <tomasn@posteo.net>
Cc: "David Bremner" <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: notmuch ignoring alot of emails
Date: Mon, 01 Apr 2019 09:02:21 +1100 [thread overview]
Message-ID: <318238AD-7746-4C6E-AE2E-E4943C23127B@runbox.com> (raw)
In-Reply-To: <87o95rxq92.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me>
That’s interesting. Do you know a link to the file spec for maildir
file content? All I can find is information about the directory
structure and file naming, not the file content.
mbsync which specialises in maildir also had an initial “From “ line
for me, and they are independently configured. I’ll try out a couple
of different mail hosts to see if it’s that.
I can imagine that mutt just assumes they are maildir files once
configured that way, but mu also assumes the files are maildir and also
uses gmime to parse. However the current version on home-brew (Mac) is
linked to a version of gmime which was fixed to accomodate multiple
“From “ lines I believe, though I haven’t dug through the source
yet.
Cheers,
Alexei
On 31 Mar 2019, at 22:00, Tomas Nordin wrote:
> Alexei Gilchrist <te100@runbox.com> writes:
>
>> 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.
>
> FWIW, I use Offlineimap and files retreived with it here does not
> begin
> with "From". I see things like "Received: from..." or
> "Return-Path:..."
> as the beginning of the first line.
>
>> 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.
>
> I tried that and find messages as expected. I mean, the message I sent
> and this thread.
>
> Best regards
> --
> Tomas
next prev parent reply other threads:[~2019-03-31 22:02 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
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 [this message]
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=318238AD-7746-4C6E-AE2E-E4943C23127B@runbox.com \
--to=te100@runbox.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomasn@posteo.net \
/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).