Re: [guile-email] parse-email-headers returns just “fields”

[Ricardo Wurmus <rekado@elephly.net>]

Arun Isaac <arunisaac@systemreboot.net> writes:

>> In some cases the emails don’t seem to have a
>> content-transfer-encoding header,
>
> This is not a problem. RFC2045 specifies that
> "Content-Transfer-Encoding: 7BIT" should be assumed if the
> Content-Transfer-Encoding header is not present. guile-email implements
> this recommendation.

Hmm, I still get this error when the first line of an email to be
parsed is something like

    From debbugs-submit-bounces@debbugs.gnu.org Wed Apr 22 11:26:37 2020

The error message is

    Body decoding failed. Unknown encoding #f

So it fails to parse the headers correctly, ends up not finding the
header specifying the encoding, and then aborts body decoding.

>> * I sometimes need to discard the first two lines of the raw email to
>>   get the headers to be fully parsed
>
> Your attachment is an mbox, not a raw email. Perhaps you are treating it
> as a raw email and that's why you have to chop off the first line? And,
> I'm guessing your other problems are also related to this.

Oh, this may be.  However, I still get the same problem when I don’t
manually discard the first line if it looks like this:

    From debbugs-submit-bounces@debbugs.gnu.org Wed Apr 22 11:26:37 2020

I’m splitting the debbugs log file containing the messages and collect
all lines between the delimiters.  I then do

  (parse-email
   (and=> (call-with-input-string contents mbox->emails) first))

But this will only work if I drop the first line from “contents”.

-- 
Ricardo