On Tue, 27 Jan 2004, Paul Jarc wrote: > > Consider a top-level message/rfc822, which contains a message/rfc822 > > part, which contains a multipart/mixed part, which contains a > > text/plain part. > I just checked the public Cyrus test server at cyrus.andrew.cmu.edu > with such a message. (Well, the multipart part contained two > text/plain parts instead of just one - close enough.) > 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. I'd like to see the exact text of the message that you claim works that way. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
