From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] guile email: decoding error
In-Reply-To: <cu7r23wkz0s.fsf@systemreboot.net>
References: <875zl9fs9l.fsf@elephly.net> <cu7r23wkz0s.fsf@systemreboot.net>
Date: Tue, 22 Oct 2019 22:11:09 +0530
Message-ID: <cu7d0eo91i2.fsf@systemreboot.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"
List-Id: <guile-email.systemreboot.net>
Message-ID: <20191022164109.dckJCSKK1yK9G6Ju-7A4pyhnZ-ACPCwwiKOmOAl6GI0@z>

--=-=-=
Content-Type: text/plain


Hi,

>> I see that mumi fails to render https://issues.guix.gnu.org/issue/37444.
>
> 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 https://git.systemreboot.net/guile-email/commit/?id=6159257c9da3664c516a26fad1ee942068fbbdd2
>
> Could you try again with this latest fix and let me know if it works?

Just a friendly ping. Did this work for you?

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl2vMS0ACgkQLiXui2GA
K7N2cQgAjKnthw4VpF+DMePEDszLvchzxqVd2hWB80aX0BTfNoPkNstacKkESQ2L
5XPI1gotfENVi6IHnvYFweqycOTXersIWEHfr/+Z7qGrEY9Lrn16IWBOGo/und5D
pJRYMX6N5O/l9aIkRdA4E8zRy5PZFZxNv0N2xXeNYo0lKZNrVpagsnBiqZdBxP/X
o5Pzk2++Aad8+i79VFfKnyn5WyE0Snl+oRw8HTWw19V34nJYPiFFRtze2VKdtdDK
q8m1F4rXjIkSJb/WHoZkXyqTpJoHM7WjiQFs5qmxpi3B6ohuD4AHz/l/jSuT4o2C
utp5qKYYDL22ilEu8bPIJxPJlVzAbQ==
=fBmB
-----END PGP SIGNATURE-----
--=-=-=--