From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: notmuch@notmuchmail.org
Subject: BUG: "notmuch insert" fails with "Delivery of non-mail file"
Date: Fri, 18 Jan 2019 13:07:35 -0300 [thread overview]
Message-ID: <201901181607.4rba4c5uyimv@alvherre.pgsql> (raw)
Hello
I've been using notmuch successfully for a couple of years now (mostly
via neomutt). Thanks for developing it.
Not long ago I switched my mail setup to use notmuch insert via
mailfilter instead of good old procmail. However, since then a number
of emails are reported by notmuch as "non-mail", and appear to not be
indexed. (I use --keep, so they're still in my maildir).
In my read of the code ultimately comes from
g_mime_parser_construct_message rejecting the message.
I reported this to GMime, and they said that the problem is that notmuch
insert is using the mbox mode:
https://github.com/jstedfast/gmime/issues/58
(Sample email is attached there).
As far as I can tell, this is all coming from
_notmuch_message_file_parse() which sets the is_mbox flag when it sees
the "^From " line at the start of the file ... which kinda makes sense
in general terms, but for notmuch-insert I think that's the wrong thing
to do. Maybe a solution is to pass a flag down from notmuch-insert.c's
add_file all the way down to _notmuch_message_file_parse telling it not
to treat the file as an mbox.
I *think* that not all of the messages that fail parsing contain an
email attachment, so maybe I'll come back with further issues later on.
This is the first one I debugged.
Thanks
--
Álvaro Herrera
next reply other threads:[~2019-01-18 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 16:07 Alvaro Herrera [this message]
2019-01-19 18:17 ` BUG: "notmuch insert" fails with "Delivery of non-mail file" David Bremner
2019-01-21 19:53 ` Alvaro Herrera
2019-02-01 19:33 ` David Bremner
2019-03-07 6:57 ` Leo L. Schwab
2019-03-07 21:05 ` David Bremner
2019-03-07 22:03 ` Alvaro Herrera
2019-03-07 22:34 ` David Bremner
2019-03-08 0:51 ` Alvaro Herrera
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=201901181607.4rba4c5uyimv@alvherre.pgsql \
--to=alvherre@alvh.no-ip.org \
--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).