guile-email discussion
 help / color / Atom feed
From: Ricardo Wurmus <>
To: Arun Isaac <>
Subject: Re: [guile-email] parse-email-headers returns just “fields”
Date: Thu, 23 Apr 2020 08:35:03 +0200
Message-ID: <> (raw)
In-Reply-To: <>

Arun Isaac <> 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 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 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

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

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


  parent reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 12:24 Ricardo Wurmus
2020-04-23  1:26 ` Arun Isaac
2020-04-23  1:26   ` Arun Isaac
2020-04-23  6:35   ` Ricardo Wurmus [this message]
2020-04-23 11:31     ` Arun Isaac
2020-04-23 11:31       ` Arun Isaac
2020-04-23 14:40       ` Ricardo Wurmus
2020-04-23 21:54         ` Arun Isaac
2020-04-23 21:54           ` Arun Isaac

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

guile-email discussion

Archives are clonable:
	git clone --mirror guile-email/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 guile-email guile-email/ \
	public-inbox-index guile-email

Example config snippet for mirrors

AGPL code for this site: git clone