MBOX-Line: From dave at cridland.net  Thu Jun 13 06:03:36 2013
To: imap-protocol@u.washington.edu
From: Dave Cridland <dave@cridland.net>
Date: Fri Jun  8 12:34:51 2018
Subject: [Imap-protocol] Question on BODYSTRUCTURE
In-Reply-To: <004f01ce67e0$1a14a960$4e3dfc20$@i-freelancer.net>
References: <004101ce6689$2b6b0630$82411290$@i-freelancer.net>
	<CAKHUCzy1y+O_vn4R6JhwE5ZoDx6=XtoN13ii+pTSFes8m7-ZfQ@mail.gmail.com>
	<004f01ce67e0$1a14a960$4e3dfc20$@i-freelancer.net>
Message-ID: <CAKHUCzzCNdtRRNRjrZxC7pXXZ-O_9FqvXgMDYCF3bAjuTgyf9A@mail.gmail.com>

On Thu, Jun 13, 2013 at 3:45 AM, ??? <ayluen@i-freelancer.net> wrote:

> Hi Dave,****
>
> ** **
>
> I?m still a bit puzzled, hopefully you could help me out.  I was studying
> a thread posted long time ago.  In that post, Mark corrected a
> bodystructure response.  ****
>
> He put 4 NILs in the positions which I thought were for extension data.***
> *
>
> ** **
>
> Here is the thread I was referring to :****
>
> ** **
>
>
> http://mailman2.u.washington.edu/pipermail/imap-uw/2005-November/000287.html
> ****
>
> **
>

Yes; he's correcting other things, and he's including all the optional data
set to NULL (because that's what his library chooses to do).


>  **
>
> but according to your previous reply, the first non-multipart can look
> like this :****
>
> ** **
>
> ("TEXT" "PLAIN" ("CHARSET" "BIG5") NIL NIL "7BIT" 860 14 NIL)****
>
> ** **
>
> Where the last NIL stands for MD5 (the rest 3 are optional)?****
>
> **
>

That seems valid by RFC 3501 to me, yes.

Though I'm surprised that BIG5 can be 7-bit encoded.

Dave.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130613/d35cb219/attachment.html>
