To: imap-protocol@u.washington.edu
MBOX-Line: From janssen at parc.com  Tue Feb  5 11:21:33 2008
From: Bill Janssen <janssen@parc.com>
Date: Fri Jun  8 12:34:41 2018
Subject: [Imap-protocol] non-ASCII byte sequences in IMAP? 
In-Reply-To: <rr9fu1gL3aYp0C0eYZ33eQ.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>
Message-ID: <08Feb5.112141pst."58696"@synergy1.parc.xerox.com>

> It happens if someone's password includes a non-ASCII letter. IMAP can 
> do it, more or less:
> 
> a login "name" password {8+}
> ääää

Yes, I see what you mean.  The "userid" and "password" arguments to
LOGIN are "astring", which can be "literal", which can be a sequence
of "CHAR8" (a binary blob without zero octets in it).  Basically,
*any* "astring" can be either an ASCII string or a binary blob.  Since
Python distinguishes between these two kinds of things (they're two
different primitive types), I guess the Python imaplib interface will
just have to deal with it.

Thanks!

Bill

