unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>,
	Alexei Gilchrist <te100@runbox.com>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch ignoring alot of emails
Date: Sat, 29 Jun 2019 21:09:06 +0200	[thread overview]
Message-ID: <87v9wodx9p.fsf@tethera.net> (raw)
In-Reply-To: <87y31kdxip.fsf@tethera.net>

David Bremner <david@tethera.net> writes:

> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
>
>> 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 --").
>>
>> Here's a sample message, BTW:
>> https://www.postgresql.org/message-id/raw/3ad5ba71-d200-96da-f903-7e3b16416140@lab.ntt.co.jp
>> (username "archives", password "antispam").
>
> I'm not keen on writing (more) ad hoc MIME parsing code, so if you can
> phrase this in terms of GMime API (or at least MIME parts) it would be
> great.
>
> d

On second thought, I guess it might not be practical to use GMime to parse
the file, since that might perform badly on large mboxes.

d

  reply	other threads:[~2019-06-29 19:09 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 [this message]
2019-07-01 15:26         ` Alvaro Herrera
2019-06-30 17:29     ` Tomi Ollila
2019-07-01 15:36       ` Alvaro Herrera
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=87v9wodx9p.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=alvherre@alvh.no-ip.org \
    --cc=notmuch@notmuchmail.org \
    --cc=te100@runbox.com \
    /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).