MBOX-Line: From MRC at Washington.EDU  Tue Feb  5 14:26:05 2008
To: imap-protocol@u.washington.edu
From: Mark Crispin <MRC@Washington.EDU>
Date: Fri Jun  8 12:34:41 2018
Subject: [Imap-protocol] non-ASCII byte sequences in IMAP?
In-Reply-To: <L7I+rFsFWPQj+ynKj+tN7g.md5@libertango.oryx.com>
References: <"08Feb3. 133012pst. 58696"@synergy1.parc.xerox.com>
	<3/ZsgW8xag0zKO8asER9/Q.md5@libertango.oryx.com> <"08Feb5.
	091040pst. 58696"@synergy1.parc.xerox.com>
	<rr9fu1gL3aYp0C0eYZ33eQ.md5@libertango.oryx.com>
	<lpAcVvMb9aegwsaoYFELvw.md5@libertango.oryx.com>
	<alpine.WNT.1.00.0802051341000.3096@Tomobiki-Cho.CAC.Washignton.EDU>
	<L7I+rFsFWPQj+ynKj+tN7g.md5@libertango.oryx.com>
Message-ID: <alpine.WNT.1.00.0802051423450.3096@Tomobiki-Cho.CAC.Washignton.EDU>

On Tue, 5 Feb 2008, Arnt Gulbrandsen wrote:
> Mark Crispin writes:
>> The IMAP specification does NOT have any syntax that requires that text in 
>> an ENVELOPE or BODYSTRUCTURE be ASCII; only that any octets greater than 
>> 0x7f be transmitted in a literal.
> I wasn't saying anything incompatible. What I said is that even though there 
> is no relevant CHARSET, 8-bit data may appear.

You and I are loudly agreeing.

As I told Bill in a private message, an astring falls into one of two 
categories:

1) It definitely can contain non-ASCII.

2) Currently, it probably is ASCII-only, but you should accept non-ASCII
    if it shows up.

The point being that there is no such thing as an astring that "definitely 
can not contain non-ASCII" even if many current astrings appear that way.

-- Mark --

http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.

