From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tomi.ollila@iki.fi>
Received: from localhost (localhost [127.0.0.1])
 by arlo.cworth.org (Postfix) with ESMTP id 98A3B6DE1498
 for <notmuch@notmuchmail.org>; Sun, 30 Jun 2019 10:29:35 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at cworth.org
X-Spam-Flag: NO
X-Spam-Score: 1.016
X-Spam-Level: *
X-Spam-Status: No, score=1.016 tagged_above=-999 required=5 tests=[AWL=-0.843, 
 MISSING_HEADERS=1.207, SPF_NEUTRAL=0.652] autolearn=disabled
Received: from arlo.cworth.org ([127.0.0.1])
 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id A6KXXhxQABBm for <notmuch@notmuchmail.org>;
 Sun, 30 Jun 2019 10:29:34 -0700 (PDT)
Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34])
 by arlo.cworth.org (Postfix) with ESMTP id 079976DE1492
 for <notmuch@notmuchmail.org>; Sun, 30 Jun 2019 10:29:32 -0700 (PDT)
Received: from guru.guru-group.fi (localhost [IPv6:::1])
 by guru.guru-group.fi (Postfix) with ESMTP id 4F2941000D0
 for <notmuch@notmuchmail.org>; Sun, 30 Jun 2019 20:29:25 +0300 (EEST)
From: Tomi Ollila <tomi.ollila@iki.fi>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch ignoring alot of emails
In-Reply-To: <20190628201121.GA8537@alvherre.pgsql>
References: <20190628201121.GA8537@alvherre.pgsql>
User-Agent: Notmuch/0.28.3+84~g41389bb (https://notmuchmail.org) Emacs/25.2.1
 (x86_64-unknown-linux-gnu)
X-Face: HhBM'cA~<r"^Xv\KRN0P{vn'Y"Kd;zg_y3S[4)KSN~s?O\"QPoL
 $[Xv_BD:i/F$WiEWax}R(MPS`^UaptOGD`*/=@\1lKoVa9tnrg0TW?"r7aRtgk[F
 !)g;OY^,BjTbr)Np:%c_o'jj,Z
Date: Sun, 30 Jun 2019 20:29:24 +0300
Message-ID: <m2y31j3rt7.fsf@guru.guru-group.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Use and development of the notmuch mail system."
 <notmuch.notmuchmail.org>
List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Jun 2019 17:29:35 -0000

On Fri, Jun 28 2019, Alvaro Herrera wrote:

> On 2019-Jun-28, Alvaro Herrera wrote:
>
>> I think a real solution is to parse the message header, look for the
>> Content-Length, and determine mbox-ness by looking for "From" only past
>> that many bytes; that seems to match what other mail parsing tools do.
>
> Sorry, I misspoke: there's no such thing as Content-Length.
> It's Content-Type/boundary that needs to be watched for.  Only consider
> that the file is an mbox if a "^From " line appears after the boundary
> end marker (which seems to be defined as "the boundary string followed
> by two dashes --").

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

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...)

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

Tomi

>
> --=20
> =C3=81lvaro Herrera       Valdivia, Chile