From: David Bremner <david@tethera.net>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: notmuch@notmuchmail.org
Subject: Re: BUG: "notmuch insert" fails with "Delivery of non-mail file"
Date: Fri, 01 Feb 2019 15:33:32 -0400 [thread overview]
Message-ID: <87d0obl2wj.fsf@tethera.net> (raw)
In-Reply-To: <201901211953.q5nxxkrlghgp@alvherre.pgsql>
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> I'm not sure I follow. As I understand, notmuch does not work with
> mboxes, only with maildirs, so the behavior of splitting emails at "From
> " is not strictly necessary, since one file always equals one message.
Checking for mboxes was added as a safety feature since people found
indexing large mboxes led to bad results (bloated index, crashing
indexer, etc...).
> On the other hand, in my world, it's been quite a while since 'From '
> was considered a useful message separator. This stopped being true in a
> pretty extensive way when git-format-patches messages started being
> posted as attachments.
Sure. Things on disk should either be mboxes, or not. If they start with
'From ', they are mboxes. We attempted to take away support for single
message mboxes, but people complained even more about that. So
generally, if tools / users don't want to escape 'From ' after the first
line, the first line should not be 'From '.
My original question was whether notmuch-insert should strip the 'From '
(and presumbly save as a normal header) before delivery.
d
next prev parent reply other threads:[~2019-02-01 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 16:07 BUG: "notmuch insert" fails with "Delivery of non-mail file" Alvaro Herrera
2019-01-19 18:17 ` David Bremner
2019-01-21 19:53 ` Alvaro Herrera
2019-02-01 19:33 ` David Bremner [this message]
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=87d0obl2wj.fsf@tethera.net \
--to=david@tethera.net \
--cc=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).