Re: IMAP BODY STRUCTURE

On 01/09/2015 04:51, Jamie Nicolson wrote:
> As far as I can tell, RFC 3501 only requires the server to parse 
> internal messages of type message/rfc822. In fact, it might be 
> considered a violation of the IMAP protocol to provide such details 
> about a message/cpim part in the bodystructure response.
Agreed, it would be a violation without a client enabled extension.
> On Fri, Aug 28, 2015 at 7:26 PM, Nigar Sultana 
> <[email protected] <mailto:[email protected]>> wrote:
>
>     Hello All,
>
>     As per RCS5.3 recommendation the IMAP message archived on server
>     includes MIME content-type Message/CPIM. CPIM wrapped MIME can
>     have attachment content-type=multipart/related.
>
>     Eg:
>     From: tel:+4917112345678 <tel:%2B4917112345678>
>     To: Joe User <[email protected] <mailto:[email protected]>>, tel:0401234567
>     Cc: tel:+358501234567 <tel:%2B358501234567>
>
These are not even email addresses, so I don't think this will work very 
well with IMAP.
>
>     Date: Tue, 27 01 2015 17:57:16 +0100
>     Subject: This is an example
>     Message-Context: multimedia-message
>     Content-Type: Message/CPIM
>     From: tel:+4917112345678 <tel:%2B4917112345678>
>     To: Joe User <[email protected] <mailto:[email protected]>>
>     To: tel:0401234567
>     cc: tel:+358501234567 <tel:%2B358501234567>
>     DateTime: 2015-01-27T16:32:55+01:00
>     Subject: This is an example
>     NS: imdn <urn:ietf:params:imdn>
>     NS: rcs <http://www.gsma.org>
>     imdn.Message-ID: 654131a654131a654131a654131a8994123
>     imdn.Disposition-Notification: display
>     rcs.Mms-Message-Class: "Personal"
>     Content-Type:
>     Multipart/Related;boundary="example-1";start=<950118>;
>     type=application/smil
>     --example-1
>     Content-Type: application/smil
>     Content-ID: <950118>"
>      [presentation]
>     --example-1
>     Content-Type: text/plain
>     Content-ID: <950119>
>     [text]
>     --example-1
>     Content-Type: image/jpeg
>     Content-ID: <950120>
>     [image]
>     --example-1--
>
>
>     The question we have is the Body Structure is returning only
>     Message/CPIM body part information and it is not sending sub body
>     structure information. Due to which on client side CPIM message
>     parsing has to be developed.
>
>     Wanted clarification from the group whether it is server issue.
>     Ideally sub body part info server has to pass
>
>     Regards
>     Nigar Sultana
>
>
>
>     _______________________________________________
>     imapext mailing list
>     [email protected] <mailto:[email protected]>
>     https://www.ietf.org/mailman/listinfo/imapext
>
>
>
>
> _______________________________________________
> imapext mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/imapext

_______________________________________________
imapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imapext