David Bremner <da...@tethera.net> writes: > Alvaro Herrera <alvhe...@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-7e3b16416...@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 _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch