24 lines
904 B
Plaintext
24 lines
904 B
Plaintext
MBOX-Line: From janssen at parc.com Tue Mar 20 12:30:26 2007
|
|
To: imap-protocol@u.washington.edu
|
|
From: Bill Janssen <janssen@parc.com>
|
|
Date: Fri Jun 8 12:34:38 2018
|
|
Subject: [Imap-protocol] literal usage
|
|
In-Reply-To: <alpine.OSX.0.83.0703200854420.23026@pangtzu.panda.com>
|
|
References: <71fe4e760703200717v201c983dq39791707ec286aa5@mail.gmail.com>
|
|
<alpine.OSX.0.83.0703200854420.23026@pangtzu.panda.com>
|
|
Message-ID: <07Mar20.113032pst."57996"@synergy1.parc.xerox.com>
|
|
|
|
> As a general rule, one (and only one) space separates tokens in IMAP.
|
|
|
|
In my server implementation, I tried to follow the old rule of "be
|
|
liberal in what you accept, and strict in what you provide." So
|
|
though arguments to IMAP commands are strictly speaking separated by
|
|
exactly one space, I accept any run of whitespace in place of that
|
|
single space. I'm speaking only of top-level arguments to a command,
|
|
of course.
|
|
|
|
Bill
|
|
|
|
|
|
|