From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 3B6C36DE0EB5 for ; Sun, 31 Mar 2019 16:28:11 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.022 X-Spam-Level: X-Spam-Status: No, score=-0.022 tagged_above=-999 required=5 tests=[AWL=-0.021, SPF_PASS=-0.001] 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 8pRfOYzHmUWo for ; Sun, 31 Mar 2019 16:28:09 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 98F586DE0EB0 for ; Sun, 31 Mar 2019 16:28:09 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1hAjrq-0002hi-38; Sun, 31 Mar 2019 19:27:58 -0400 Received: (nullmailer pid 6521 invoked by uid 1000); Sun, 31 Mar 2019 23:27:56 -0000 From: David Bremner To: Alexei Gilchrist , Tomas Nordin Cc: notmuch@notmuchmail.org Subject: Re: notmuch ignoring alot of emails In-Reply-To: <318238AD-7746-4C6E-AE2E-E4943C23127B@runbox.com> References: <9359F7FC-94C5-48CA-B4C9-2FEB2C7EC398@runbox.com> <877ecgy505.fsf@tethera.net> <87o95rxq92.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> <318238AD-7746-4C6E-AE2E-E4943C23127B@runbox.com> Date: Sun, 31 Mar 2019 20:27:56 -0300 Message-ID: <878swuwrnn.fsf@tethera.net> 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Mar 2019 23:28:11 -0000 "Alexei Gilchrist" writes: > That=E2=80=99s interesting. Do you know a link to the file spec for maild= ir=20 > file content? All I can find is information about the directory=20 > structure and file naming, not the file content. As far as I know, this is specified by RFC 5322.=20 > mbsync which specialises in maildir also had an initial =E2=80=9CFrom =E2= =80=9C line=20 > for me, and they are independently configured. I=E2=80=99ll try out a cou= ple=20 > of different mail hosts to see if it=E2=80=99s that. Yes, it could well determined by how the messages are delivered on the server. > I can imagine that mutt just assumes they are maildir files once=20 > configured that way, but mu also assumes the files are maildir and also=20 > uses gmime to parse. However the current version on home-brew (Mac) is=20 > linked to a version of gmime which was fixed to accomodate multiple=20 > =E2=80=9CFrom =E2=80=9C lines I believe, though I haven=E2=80=99t dug thr= ough the source=20 > yet. As I mentioned above, it's not really related to the version of GMime, it's about how GMime is called, and whether the client wishes to parse mbox files containing more than one message. Or to ignore the "From " line at the beginning.