MBOX-Line: From ams at oryx.com  Wed Jan  9 20:02:09 2008
To: imap-protocol@u.washington.edu
From: Abhijit Menon-Sen <ams@oryx.com>
Date: Fri Jun  8 12:34:41 2018
Subject: [Imap-protocol] Re: Question on FETCH example in RFC3501
In-Reply-To: <b6f3249e0801091938m12cbccd6j4fff9f406cf0fee1@mail.gmail.com>
References: <b6f3249e0801091938m12cbccd6j4fff9f406cf0fee1@mail.gmail.com>
Message-ID: <20080110040209.GA25060@toroid.org>

Hi Liam.

At 2008-01-10 16:38:00 +1300, ml.cyresse@gmail.com wrote:
>
> C:    a004 fetch 12 body[header]
> S:    * 12 FETCH (BODY[HEADER] {342}
> S:    Date: Wed, 17 Jul 1996 02:23:25 -0700 (PDT)
> S:    From: Terry Gray <gray@cac.washington.edu>
> S:    Subject: IMAP4rev1 WG mtg summary and minutes
> S:    To: imap@cac.washington.edu
> S:    cc: minutes@CNRI.Reston.VA.US, John Klensin <KLENSIN@MIT.EDU>
> S:    Message-Id: <B27397-0100000@cac.washington.edu>
> S:    MIME-Version: 1.0
> S:    Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
> S:
> S:    )
> S:    a004 OK FETCH completed

> [...] but is the second actually split over multiple \r\n delimited
> lines?

Not exactly. It contains a literal that contains multiple CRLFs.

> If so, would it be possible for lines from separate fetch responses to
> arrive together?

No. This response:

> S:    * 12 FETCH (BODY[HEADER] {342}

promises to send you 342 bytes of literal data immediately following the
CRLF (see RFC 3501 ?4.3 for an explanation of literals).

-- ams

