Re: [Imap-protocol] IMAP part numbering corner case
Timo Sirainen <[email protected]>
| Newsgroups | gmane.mail.imap.general |
|---|---|
| Message-ID | <[email protected]> |
On 17.8.2012, at 7.51, Philip Guenther wrote: >>> 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. Yes, after thinking about it for a while I agree. Added it to my tests. Anyway, [1.MIME] isn't a valid request in Joshua's test mail. I also changed Dovecot to return an empty string for it and for [1.1.1], maybe it'll help to avoid client developer confusion in future. :) _______________________________________________ Imap-protocol mailing list [email protected] http://mailman2.u.washington.edu/mailman/listinfo/imap-protocol