27 lines
1.1 KiB
Plaintext
27 lines
1.1 KiB
Plaintext
MBOX-Line: From tss at iki.fi Tue Oct 30 10:30:40 2012
|
|
To: imap-protocol@u.washington.edu
|
|
From: Timo Sirainen <tss@iki.fi>
|
|
Date: Fri Jun 8 12:34:49 2018
|
|
Subject: [Imap-protocol] significance of leading whitespace in RFC 2822
|
|
unstructured headers
|
|
In-Reply-To: <508F4486.8060405@ymail.com>
|
|
References: <508F017B.4000606@ymail.com>
|
|
<CAC4RtVAbtsg38HstaFYO8Hv4H6-X7noeMNRey1DtkvYEbrOQyA@mail.gmail.com>
|
|
<508F4486.8060405@ymail.com>
|
|
Message-ID: <EBBF36BC-AAAC-41DD-A967-C3EBB2E4F488@iki.fi>
|
|
|
|
On 30.10.2012, at 5.07, Bill Shannon wrote:
|
|
|
|
> One of the reasons I asked here is because of the interaction between
|
|
> the syntax of these header fields and what an IMAP server should do
|
|
> when parsing the header and returning the parsed value. The syntax
|
|
> would imply that all whitespace after the colon is part of the value
|
|
> of the header, but that's not what most/all IMAP servers do, and not
|
|
> what the examples show. Is there something in the IMAP spec that
|
|
> says leading whitespace should be removed from these header values?
|
|
|
|
|
|
http://marc.info/?t=105363818800005&r=1&w=4
|
|
|
|
|