Mark Crispin <[EMAIL PROTECTED]> wrote: > On Tue, 27 Jan 2004, Paul Jarc wrote: >> That server agrees with what Mark says ([1.1.HEADER] is the header of >> the multipart/mixed message), but it seems to disagree with the >> example in RFC3501. In my test message: >> [1] is an entire message/rfc822 message (itself encapsulated >> within a top-level message/rfc822 message), >> [1.TEXT] is the entire encapsulated multipart/mixed message, >> [1.1] is the same as [1.TEXT], and >> [1.1.1] is the first part contained in the multipart/mixed message. > > I find that difficult to believe. 1.1 should be the first part contained > in the multipart/mixed content.
So you're saying that in this case, [1.1.HEADER] is not supposed to be a component of [1.1]? > I'd like to see the exact text of the message that you claim works that > way. It's still available on the server right now. telnet cyrus.andrew.cmu.edu imap 1 login anonymous your-email-address 2 select inbox 3 fetch 5 body[] 4 fetch 5 body[1.text] 5 fetch 5 body[1.1] paul
