wasm-demo/demo/ermis-f/imap-protocol/cur/1600095043.22719.mbox:2,S

77 lines
2.3 KiB
Plaintext

MBOX-Line: From guenther+imap at sendmail.com Thu Aug 16 21:51:59 2012
To: imap-protocol@u.washington.edu
From: Philip Guenther <guenther+imap@sendmail.com>
Date: Fri Jun 8 12:34:48 2018
Subject: [Imap-protocol] IMAP part numbering corner case
In-Reply-To: <060A31A9-066E-43F0-97AF-4B68522832B1@iki.fi>
References: <502DBEA4.2070204@verizon.net>
<alpine.BSO.2.00.1208162109520.13998@morgaine.smi.sendmail.com>
<060A31A9-066E-43F0-97AF-4B68522832B1@iki.fi>
Message-ID: <alpine.BSO.2.00.1208162143500.13998@morgaine.smi.sendmail.com>
On Fri, 17 Aug 2012, Timo Sirainen wrote:
> On 17.8.2012, at 7.17, Philip Guenther wrote:
> >> [Outlook, I'm pretty sure, but it doesn't implement ID]:
> >> BODY[TEXT]: The entire inner message
> >> BODY[1]: The entire inner message
> >> BODY[1.1]: NIL
> >
> > This violates this paragraph from RFC 3501, page 55:
> > A part of type MESSAGE/RFC822 also has nested part numbers,
> > referring to parts of the MESSAGE part's body.
> >
> > ...which when combined with the first quote above, means that "1.1"
> > should be a valid specifier for the inner message's content.
>
> Is it valid? 1.1 makes sense when it's a multipart, in which case it
> refers to the first MIME part, but is it valid when ther's no multipart?
> Looks like UW-IMAP allows it, but not 1.1.1, so maybe it was meant to be
> valid. I could add it to my tests..
Flip it around. Given a message, if you nest it inside another message as
a message/rfc822 part, the addressing of its parts are formed by
concatenating the addressing of the part it is nested as and the parts
inside it.
Given this message
-----
Date: Fri, 01 Jan 2012 12:00 -0500
To: y@y.y
From: x@x.x
Subject: Blast from the future
MIME-Version:1.0
Content-Type: text/plain
Do you know what to do when you see this message?
-----
it has a single part, which can be addressed with the specifier "1". So,
if you nest it
-----
Date: Fri, 01 Jan 2010 12:00 -0500
To: x@x.x
From: y@y.y
Subject: download on demand problem
MIME-Version: 1.0
Content-Type: message/rfc822
Date: Fri, 01 Jan 2012 12:00 -0500
To: y@y.y
From: x@x.x
Subject: Blast from the future
MIME-Version:1.0
Content-Type: text/plain
Do you know what to do when you see this message?
-----
The entire inner message is "1", so the text of the inner message is the
concatenation "1.1".
Philip Guenther