From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.systemreboot.net (mugam.systemreboot.net [139.59.75.54]) by localhost (mpop-1.4.5) with POP3 for ; Wed, 23 Oct 2019 00:34:34 +0530 Return-path: Envelope-to: arunisaac@systemreboot.net Delivery-date: Tue, 22 Oct 2019 22:11:22 +0530 Received: from localhost.localdomain ([127.0.0.1] helo=[192.168.2.12]) by systemreboot.net with esmtp (Exim 4.92.3) (envelope-from ) id 1iMxDm-000kK4-O7 for arunisaac@systemreboot.net; Tue, 22 Oct 2019 22:11:22 +0530 Received: from [49.206.8.226] (helo=steel) by systemreboot.net with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1iMxDi-000kJw-EO; Tue, 22 Oct 2019 22:11:18 +0530 From: Arun Isaac To: Ricardo Wurmus In-Reply-To: References: <875zl9fs9l.fsf@elephly.net> Date: Tue, 22 Oct 2019 22:11:09 +0530 Message-ID: MIME-Version: 1.0 Subject: Re: [guile-email] guile email: decoding error X-BeenThere: guile-email@systemreboot.net X-Mailman-Version: 2.1.29 Precedence: list List-Id: guile-email discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guile-email@systemreboot.net Content-Type: multipart/mixed; boundary="===============4614041097915655979==" Errors-To: guile-email-bounces@systemreboot.net --===============4614041097915655979== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= 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/Lwnzx3v3nTLiXui2GAK7MFAl2vMSYACgkQLiXui2GA K7MhLwf8CaAEaYVqrk/MObaSTFMWHKmlSpcyTXdUdtg+Qy68BMTxdWwokN2i4Mu/ EXzAuwjepOkjKT3V2hH8gmAWpknEvlFPVyXvLtz0jaTJgpN6+fkTt11hUw9Wj+Kd MMmJNzS4EJRFlmyet7wtYGxVIcmtpPQsn+BbpO9E7DfonykEr6mOAIC1X+SCT9ZH CWQ+EuQsQh1Fq7U70kXBVAAfPcN65QCt9+azKRYrK2SELc9HwY2wQaT82lvpecsL KVR4TZftXVvKLK/JULIHSsABl5oEEiYxklyjCaAGq1DNOU0jSFoLijHTX3o4/OxO ixcWe+sTSoqjHUxI7K8fbUygCRnVog== =1a8F -----END PGP SIGNATURE----- --=-=-=-- --===============4614041097915655979== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- guile-email mailing list guile-email@systemreboot.net https://lists.systemreboot.net/listinfo/guile-email --===============4614041097915655979==-- 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] guile email: decoding error In-Reply-To: References: <875zl9fs9l.fsf@elephly.net> Date: Tue, 22 Oct 2019 22:11:09 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: 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----- --=-=-=--