guile-email discussion
 help / color / mirror / Atom feed
From: Arun Isaac <>
To: Ricardo Wurmus <>
Subject: Re: guile email: decoding error
Date: Wed, 02 Oct 2019 01:40:27 +0530	[thread overview]
Message-ID: <> (raw)
Message-ID: <20191001201027.a8ZkuM2ccMiXAOvSNCc0JmjTVyUc2O73Lfb2ikCHOIk@z> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

       reply	other threads:[~2019-10-01 20:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2019-10-01 20:10 ` Arun Isaac [this message]
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
2019-11-30 19:13     ` [guile-email] " 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