MBOX-Line: From bill.shannon at ymail.com  Mon Oct 29 20:07:50 2012
To: imap-protocol@u.washington.edu
From: Bill Shannon <bill.shannon@ymail.com>
Date: Fri Jun  8 12:34:49 2018
Subject: [Imap-protocol] significance of leading whitespace in RFC 2822
	unstructured headers
In-Reply-To: <CAC4RtVAbtsg38HstaFYO8Hv4H6-X7noeMNRey1DtkvYEbrOQyA@mail.gmail.com>
References: <508F017B.4000606@ymail.com>
	<CAC4RtVAbtsg38HstaFYO8Hv4H6-X7noeMNRey1DtkvYEbrOQyA@mail.gmail.com>
Message-ID: <508F4486.8060405@ymail.com>

Barry Leiba wrote on 10/29/2012 05:41 PM:
>> (Maybe there's an RFC 2822 experts list that would be more appropriate
>> for this question?  If so, please point me in the right direction.)
> 
> Two things, to start with:
> 
> 1. The right list for this would be ietf-822@ietf.org

Thanks for the pointer.  I'll ask there if no answer appears here.

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?

> 2. RFC 5322 is the current spec; 2822 is obsolete.

A quick scan didn't turn up anything that would resolve my issue
differently.


