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 <arun>; Wed, 02 Oct 2019 02:53:23 +0530
Return-path: <guile-email-bounces@systemreboot.net>
Envelope-to: arunisaac@systemreboot.net
Delivery-date: Wed, 02 Oct 2019 01:40:36 +0530
Received: from localhost.localdomain ([127.0.0.1] helo=[192.168.2.12])
	by systemreboot.net with esmtp (Exim 4.92.1)
	(envelope-from <guile-email-bounces@systemreboot.net>)
	id 1iFOTk-0000nI-P6
	for arunisaac@systemreboot.net; Wed, 02 Oct 2019 01:40:36 +0530
Received: from [49.206.3.117] (helo=steel)
 by systemreboot.net with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256)
 (Exim 4.92.1) (envelope-from <arunisaac@systemreboot.net>)
 id 1iFOTi-0000nA-BE; Wed, 02 Oct 2019 01:40:34 +0530
From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
In-Reply-To: <875zl9fs9l.fsf@elephly.net>
References: <875zl9fs9l.fsf@elephly.net>
Date: Wed, 02 Oct 2019 01:40:27 +0530
Message-ID: <cu7r23wkz0s.fsf@systemreboot.net>
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 <guile-email.systemreboot.net>
List-Unsubscribe: <https://lists.systemreboot.net/options/guile-email>,
 <mailto:guile-email-request@systemreboot.net?subject=unsubscribe>
List-Archive: <https://lists.systemreboot.net/archives/guile-email/>
List-Post: <mailto:guile-email@systemreboot.net>
List-Help: <mailto:guile-email-request@systemreboot.net?subject=help>
List-Subscribe: <https://lists.systemreboot.net/listinfo/guile-email>,
 <mailto:guile-email-request@systemreboot.net?subject=subscribe>
Cc: guile-email@systemreboot.net
Content-Type: multipart/mixed; boundary="===============0440675462942065450=="
Errors-To: guile-email-bounces@systemreboot.net

--===============0440675462942065450==
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"

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

Ricardo Wurmus <rekado@elephly.net> 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/Lwnzx3v3nTLiXui2GAK7MFAl2TsrMACgkQLiXui2GA
K7PeKwf+Jh64Im2YGjIIyiqd1MuzV9x1dl+PvGRM5ItM5GVYdMEQjzNQE8gf8XEh
J+0reOiltOGyz4QDzDYNS+VB6VAB//mS5ojsEZj+qQoXlA0cZyJNIrYYbrh0WY3I
8ALIXgMNbQ2wZZbMOIUg8XjK0+eTSGbfUpqWQJBDlruIHfyqoV/CCLg9Q3sTR1k5
uQseWV7O53newyBmuhQuWM614UmZcrKPMmrHyo737Ansebzjxg2vZGl6yvM9GktZ
63rTifHYqFrmB6bky+Kr9HuLbRv8Cea1VGzRVjUa1wFltUqVyZl99jLcMRUZkDDi
MjMesVk2JZ+NeV2eujp5sA1piVXEYg==
=Yeri
-----END PGP SIGNATURE-----
--=-=-=--


--===============0440675462942065450==
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

--===============0440675462942065450==--


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: 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: <cu7r23wkz0s.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: <20191001201027.a8ZkuM2ccMiXAOvSNCc0JmjTVyUc2O73Lfb2ikCHOIk@z>

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

Ricardo Wurmus <rekado@elephly.net> 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-----
--=-=-=--