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>; Tue, 17 Sep 2019 09:50:12 +0530 Return-path: <guile-email-bounces@systemreboot.net> Envelope-to: arunisaac@systemreboot.net Delivery-date: Tue, 17 Sep 2019 01:51:01 +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 1i9xUb-0005ld-2g for arunisaac@systemreboot.net; Tue, 17 Sep 2019 01:51:01 +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 1i9xUX-0005lV-Tb; Tue, 17 Sep 2019 01:50:58 +0530 From: Arun Isaac <arunisaac@systemreboot.net> To: Christopher Baines <mail@cbaines.net> In-Reply-To: <cu7r24g8anm.fsf@systemreboot.net> References: <87woe91zv4.fsf@cbaines.net> <cu7tv9c8t92.fsf@systemreboot.net> <cu7r24g8anm.fsf@systemreboot.net> Date: Tue, 17 Sep 2019 01:50:56 +0530 Message-ID: <cu7o8zk802f.fsf@systemreboot.net> MIME-Version: 1.0 Subject: Re: [guile-email] decoding-error crash 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="===============6301665618005885967==" Errors-To: guile-email-bounces@systemreboot.net --===============6301665618005885967== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable >>> From: ludo@gnu.org (Ludovic Court=C3=A8s) > > On the other hand, I just realized that this is a non-standard Emacs > message mode parens style address described at > https://www.gnu.org/software/emacs/manual/html_node/emacs/Mail-Headers.ht= ml > . guile-email aims to support these non-standard addresses. So, I think > we can relax the requirement that email headers be strictly ASCII. I'll > push a fix and let you know. I've pushed a fix along with a test to prevent regression. See https://git.systemreboot.net/guile-email/commit/?id=3D203c9c2ae39a4c64bfd91= 99bbc2deae03c347998 Could you use a git checkout of the master branch for your guile-email deployment? Or would you rather I get a minor bugfix release out soon? Thanks for reporting this bug and thanks for choosing guile-email! :-) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl1/7qkACgkQLiXui2GA K7PJSwf+PpD7niMPBTy0lUPo8oE0K4IIgxNh2HP+hBp2KSgiILbAmaYPDTGchQu0 sSvOk7lXbx8hY+cHfxA5Cpfq6zpRKAlS00PfrjCVSKWuNBxu2cjFZ53aFAQt5YHh EbVNgzGEa5tX/lUNYoM9w+HtLjIa4xea8Z2EThNZitCt3e9Eny7GwYHasNcs8nm8 fIuvoJO/E/X/URH+xjH0l7UT8y2xysOjwFidk4Kc1Y/BwrYUsuqsYAmQGf6VArpR f7AajVv6gK3PgcVW+JlNbZKU5fapGDOtK1NIt//0NLAV5m9DK3z/fF7uZRhHEgbL pNKSgWvrvwjGO8n9eIZgo0FGMUBg6Q== =ZRp2 -----END PGP SIGNATURE----- --=-=-=-- --===============6301665618005885967== 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 --===============6301665618005885967==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Isaac <arunisaac@systemreboot.net> To: Christopher Baines <mail@cbaines.net> Cc: guile-email@systemreboot.net Subject: Re: [guile-email] decoding-error crash In-Reply-To: <cu7r24g8anm.fsf@systemreboot.net> References: <87woe91zv4.fsf@cbaines.net> <cu7tv9c8t92.fsf@systemreboot.net> <cu7r24g8anm.fsf@systemreboot.net> Date: Tue, 17 Sep 2019 01:50:56 +0530 Message-ID: <cu7o8zk802f.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: <20190916202056._H0gCXiIW2ef2c6r3OpRHa1io8Ln4VN7yxdXVJRVbVc@z> --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable >>> From: ludo@gnu.org (Ludovic Court=C3=A8s) > > On the other hand, I just realized that this is a non-standard Emacs > message mode parens style address described at > https://www.gnu.org/software/emacs/manual/html_node/emacs/Mail-Headers.ht= ml > . guile-email aims to support these non-standard addresses. So, I think > we can relax the requirement that email headers be strictly ASCII. I'll > push a fix and let you know. I've pushed a fix along with a test to prevent regression. See https://git.systemreboot.net/guile-email/commit/?id=3D203c9c2ae39a4c64bfd91= 99bbc2deae03c347998 Could you use a git checkout of the master branch for your guile-email deployment? Or would you rather I get a minor bugfix release out soon? Thanks for reporting this bug and thanks for choosing guile-email! :-) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl1/7qoACgkQLiXui2GA K7PneQf/ZD7/RTUp6RD/zrLAddl1h6tWyaEGmISZz+lzNE+L2KcCgemi0D4aLHqx gsU3hCweY50O/Kj3RU6neahdfaJ0RqoD8wOMl1cmYe/+EhuOoNsV8BPd3mmS5pB5 c0P4O3TC6kSvr7jRIx7NlenXIxxBxIZSwZn1a1PHqLCzJdgp776izsBGit/aqPAr vCh8cnGfg2Pafy1fojcuUbvuDrlxEwRknybx9bMLC4Kyi0JmfSBHo507hPTR+STA ITj0EM7iVG4BZUvs82z7T7z/+PYz1sASkBsPMcNCpwZAtx78jc+xiWwfQoO8GDRG S2+9CpHpkVVD356PyzsXfJr/qTIWwA== =E68l -----END PGP SIGNATURE----- --=-=-=--