guile-email discussion
 help / color / mirror / Atom feed
From: Ricardo Wurmus <>
To: Arun Isaac <>
Subject: Re: guile email: decoding error
Date: Fri, 29 Nov 2019 13:39:17 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Arun,

> Ricardo Wurmus <> writes:
>> I see that mumi fails to render
> This is due to an invalid charset in the Content-Type header of message
> 107 (debbugs numbering). In the event of such invalid Content-Type
> headers, RFC2045 recommends assuming the default Content-Type header. I
> have now implemented this recommendation in
> guile-email. See commit
> Could you try again with this latest fix and let me know if it works?

The latest version of guile-email fixes all problems I had.  Bug 37444
renders correctly now, as does bug 37978.

Thank you very much!  I’ll update mumi soon to use the latest version of

Aside; I’ve been having weird problems with the web server from (fibers
web server).  Using that web server somehow breaks XML parsing in my
recent tests.  Every XML processing outside of the web server loop works
just fine.  Very odd.  (This problem contributed to the delay in testing
your improvements, but really the biggest problem was making enough time
to sit down without the baby as I can’t type well enough with just one
free arm.)


  parent reply	other threads:[~2019-11-30 16:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2019-10-01 20:10 ` [guile-email] " Arun Isaac
2019-10-01 20:10   ` Arun Isaac
2019-10-22 16:41   ` [guile-email] " Arun Isaac
2019-10-22 16:41     ` Arun Isaac
2019-11-29 12:39   ` Ricardo Wurmus [this message]
2019-11-30 19:13     ` Arun Isaac
2019-11-30 19:13       ` 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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox