mailing list archives

meli community discussions

⚠️ if something does not work as intended when interracting with the mailing lists,
reach out Github mirror Gitea repo @epilys:matrix.org

E-mail headers
From: Ian Anderson <iana@apple.com>
To: imap-protocol@u.washington.edu
Date: Fri, 08 Jun 2018 12:34:48 -0000
Message-ID: 5B2D87F5-EFFF-4225-BE4A-F4660CF8E964@apple.com permalink / raw / eml / mbox
How is one supposed to put non-ASCII text in the human readable portion of a response?  Something like this.

tag01 NO [ALERT] some non-ASCII text to show the user

RFC 3501 is unclear on this, it would seem to indicate that this part of the response is "text" which boils down to "any CHAR except CR and LF".  But how are the bytes to be interpreted?  Are they limited to ASCII?  Is there another standard that allows non-ASCII bytes?

Ian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4383 bytes
Desc: not available
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20120710/39d0e56e/attachment.p7s>
Reply
E-mail headers
From: slusarz@curecanti.org
To: imap-protocol@localhost
Date: Fri, 08 Jun 2018 12:34:48 -0000
Message-ID: 20120710124542.Horde.DgHsC4F5lbhP-HhWuUbyDRA@bigworm.curecanti.org permalink / raw / eml / mbox
Quoting Ian Anderson <iana@apple.com>:

> How is one supposed to put non-ASCII text in the human readable  
> portion of a response?  Something like this.
>
> tag01 NO [ALERT] some non-ASCII text to show the user
>
> RFC 3501 is unclear on this, it would seem to indicate that this  
> part of the response is "text" which boils down to "any CHAR except  
> CR and LF".  But how are the bytes to be interpreted?  Are they  
> limited to ASCII?  Is there another standard that allows non-ASCII  
> bytes?

RFC 3501 is limited to US-ASCII response text.  To use UTF-8, you need  
the LANGUAGE extension: RFC 5255 (http://tools.ietf.org/html/rfc5255).

michael
Reply