From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Isaac To: Ricardo Wurmus Cc: guile-email@systemreboot.net Subject: Re: guile email: decoding error In-Reply-To: <875zl9fs9l.fsf@elephly.net> References: <875zl9fs9l.fsf@elephly.net> Date: Wed, 02 Oct 2019 01:40:27 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: Message-ID: <20191001201027.a8ZkuM2ccMiXAOvSNCc0JmjTVyUc2O73Lfb2ikCHOIk@z> --=-=-= Content-Type: text/plain Ricardo Wurmus writes: > 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? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl2TsrsACgkQLiXui2GA K7OpUAgAiwViggp3bI5CcfhTmZ+PkfZDkCN8cTIF4rCUDhgjGKushB5/ZbjIK1cj 4a8fHAFCODP/Bimz2bUgN4/BJtw86IAyv45BV8GSj6Xbm3+okPnllw/vESuPms+n 8JS12y5uaChiGW6eAYXKpRmaSvjKSf73EpELYNecaErNow0qOjWvoqa1yS7A2oVA cMDZyV22tJYwix3JFWnYgp1zlTLNUOfq9DK3m2abwWArlqyBuONS9xLsiZ+vL8Vc rJWJQbwu7RmJdHvKo081SkeW+53sQhQsNwBu+kSppmSQrr7+Ie+pEYw2PkNQ+P6a qd1d19BSHpz4KgQTLliKAu0vipR57g== =1Lez -----END PGP SIGNATURE----- --=-=-=--