From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Isaac To: Christopher Baines Cc: guile-email@systemreboot.net Subject: Re: [guile-email] decoding-error crash In-Reply-To: <87sgow0xmw.fsf@cbaines.net> References: <87woe91zv4.fsf@cbaines.net> <87sgow0xmw.fsf@cbaines.net> Date: Tue, 17 Sep 2019 11:07:46 +0530 Message-ID: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" List-Id: --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable >> we can relax the requirement that email headers be strictly ASCII. I'll >> push a fix and let you know. > > Great, thanks. Let me know if the fix works for you. > In terms of where this message came from, I'm using getmail [1] to > recieve the messages, then using the external MTA delivery config to > pass the message off to a Guile script. I was processing the messages as > strings, but I'm switching to using bytevectors. Ok. > I believe this issue happens with strings and bytevectors. Yes, you are right. The issue of strings and bytevectors is orthogonal. An email is a bag of bytes (not a bag of characters) -- a binary file that needs to be parsed by guile-email. > I've checked my mailserver, and the file corresponding to the sample > email provided doesn't look to have a pure ASCII from header (in the > terminal, I see a ? instead of =C3=A8, so I'm not sure what's going on > there). Not sure which line you are referring to, but in Icecat, as far as I can tell, I see all the '=C3=A8's correctly. Perhaps it's a decoding issue with whichever viewer you are using. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl2AcTMACgkQLiXui2GA K7N+hQf7Bin98wF00iWELIoZPM+frLvRjfgyp1rX2ZzYadhwaJfF+OrLoWlKx7bq n2LI8/No/j2J5/Y9a1Y05eIQap2Ma3i0CAENZHTUsM4Ia1kOdvj1r4DAdiFCHNWQ ZNeqABXAnzYITt5TqD8y4ZsZDS9nsCt7MdUZAfCG+C2vbMDdrwtqYfnnEFegfxqq AtvnSeVSkn4y6RpmKecqKvTaffNLNsFlrK6q/kRL2TmoDn1hD+BVdU07JNAvarT9 x+injWG9z/uT8VOh/L7JJEVM6B+sTtEo2pa+8x9tFc9Myz6QRdjfZkt0H417lyrq me95OPHEovkpej1Kr9R2WlzOsKhQag== =fmtu -----END PGP SIGNATURE----- --=-=-=-- 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 ; Tue, 17 Sep 2019 12:24:56 +0530 Return-path: Envelope-to: arunisaac@systemreboot.net Delivery-date: Tue, 17 Sep 2019 11:07:56 +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 ) id 1iA6BY-0006sB-BE for arunisaac@systemreboot.net; Tue, 17 Sep 2019 11:07:56 +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 ) id 1iA6BW-0006s4-Qa; Tue, 17 Sep 2019 11:07:54 +0530 From: Arun Isaac To: Christopher Baines In-Reply-To: <87sgow0xmw.fsf@cbaines.net> References: <87woe91zv4.fsf@cbaines.net> <87sgow0xmw.fsf@cbaines.net> Date: Tue, 17 Sep 2019 11:07:46 +0530 Message-ID: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: guile-email@systemreboot.net Content-Type: multipart/mixed; boundary="===============1842379553687811395==" Errors-To: guile-email-bounces@systemreboot.net Message-ID: <20190917053746.ib46U261uL7MZBKl15RbNp0ZiQbRtHqmXwTVQA7deTE@z> --===============1842379553687811395== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable >> we can relax the requirement that email headers be strictly ASCII. I'll >> push a fix and let you know. > > Great, thanks. Let me know if the fix works for you. > In terms of where this message came from, I'm using getmail [1] to > recieve the messages, then using the external MTA delivery config to > pass the message off to a Guile script. I was processing the messages as > strings, but I'm switching to using bytevectors. Ok. > I believe this issue happens with strings and bytevectors. Yes, you are right. The issue of strings and bytevectors is orthogonal. An email is a bag of bytes (not a bag of characters) -- a binary file that needs to be parsed by guile-email. > I've checked my mailserver, and the file corresponding to the sample > email provided doesn't look to have a pure ASCII from header (in the > terminal, I see a ? instead of =C3=A8, so I'm not sure what's going on > there). Not sure which line you are referring to, but in Icecat, as far as I can tell, I see all the '=C3=A8's correctly. Perhaps it's a decoding issue with whichever viewer you are using. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAl2AcSoACgkQLiXui2GA K7OONwf/fuxl63as+RsN3Xn1pwHZBai+emL7VFjcnnhiQ9AB+RyXGCAw6ea/YD8o 92nzusxc1P2J1IVlcWPujH6vQmzBkANPs2FUV0I3MqDvSdLCTk/dKQY+NhjlWXjh u2Uca++X/cf49SMdFHLJzQPGO8K66/6ld+FP79CWbhieAaugPxnqxDSuOqrekEYC IYUMTE+GTNdxFDvQ0b+kwOzmXdb85VzojHn0e+2NUOD9/xP2aaJOapwqy7bySGIk 6VxFrJU43esgUru1G3K2BB1xXp/OHBhJU8jIC/1t6LMztpVcfexvBv3u4ltq7wDr GOd9H9/GmUuVt5V2o6taVBOKK5VnBg== =tves -----END PGP SIGNATURE----- --=-=-=-- --===============1842379553687811395== 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 --===============1842379553687811395==--