From: Arun Isaac <arunisaac@systemreboot.net>
To: Christopher Baines <mail@cbaines.net>
Cc: guile-email@systemreboot.net
Subject: Re: [guile-email] decoding-error crash
Date: Tue, 17 Sep 2019 11:07:46 +0530 [thread overview]
Message-ID: <cu7lfun8out.fsf@systemreboot.net> (raw)
Message-ID: <20190917053746.ib46U261uL7MZBKl15RbNp0ZiQbRtHqmXwTVQA7deTE@z> (raw)
In-Reply-To: <87sgow0xmw.fsf@cbaines.net>
[-- Attachment #1.1: Type: text/plain, Size: 1112 bytes --]
>> 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 è, 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 'è's correctly. Perhaps it's a decoding issue with
whichever viewer you are using.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
[-- Attachment #2: Type: text/plain, Size: 110 bytes --]
--
guile-email mailing list
guile-email@systemreboot.net
https://lists.systemreboot.net/listinfo/guile-email
next prev parent reply other threads:[~2019-09-17 6:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 12:57 Christopher Baines
2019-09-16 9:50 ` Arun Isaac
2019-09-16 9:50 ` Arun Isaac
2019-09-16 16:32 ` Arun Isaac
2019-09-16 16:32 ` Arun Isaac
2019-09-16 20:20 ` Arun Isaac
2019-09-16 20:20 ` Arun Isaac
2019-09-22 13:19 ` Christopher Baines
2019-09-23 5:21 ` Arun Isaac
2019-09-23 5:21 ` Arun Isaac
2019-09-23 7:30 ` Christopher Baines
2019-09-23 19:28 ` Arun Isaac
2019-09-23 19:28 ` Arun Isaac
2019-09-24 7:17 ` Christopher Baines
2019-09-16 20:55 ` Christopher Baines
2019-09-17 5:37 ` Arun Isaac [this message]
2019-09-17 5:37 ` Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7lfun8out.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=guile-email@systemreboot.net \
--cc=mail@cbaines.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox