unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tomi Ollila <tomi.ollila@iki.fi>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch ignoring alot of emails
Date: Mon, 1 Jul 2019 11:36:57 -0400	[thread overview]
Message-ID: <20190701153657.GA9961@alvherre.pgsql> (raw)
In-Reply-To: <m2y31j3rt7.fsf@guru.guru-group.fi>

On 2019-Jun-30, Tomi Ollila wrote:

> Just checking line starting with 'From ' would be pretty naïve since
> From may be first word in any line in text body.

Even so, early mail systems relied on there not being any such lines,
and they escaped those lines to be ">From" or to use quoted-printable
encoding.  GMime has bespoke code to do this, in fact.  Mail systems
stopped doing this escaping after MIME boundaries got more widely used,
I suppose.

I think NNTP used content length much more extensively than email.  Of
course, NNTP is almost disappeared now ...

> If we'd have to do content scanning then at least empty line before
> From would be reguired, and next lines starting like
> Received: someone@not.an.example
> Date: a date
> From: someone
> 
> (and then empty line... ;)
> 
> all this checkin would be required and still it could fail (perhaps
> this content get modified in the fly, but then signature check, if
> this mail had one, could fail...)

This logic still fails if you have mail-like content in the mail, such
as attachments produced by "git format-patch".  Many open source lists
don't have this problem because they use "git send-email" instead, but
this is not universal.

> If there is header that tells the length of the body, then things
> could be easier...

Early emails had Content-Length as a header, but it was not universal,
and nowadays it seems to have been abandoned as a practice; the MIME
content boundary is used universally (or at least I cannot find any
recent divergence from this practice.)

-- 
Álvaro Herrera                                http://www.twitter.com/alvherre

  reply	other threads:[~2019-07-01 16:35 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
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 [this message]
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=20190701153657.GA9961@alvherre.pgsql \
    --to=alvherre@alvh.no-ip.org \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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).