IETF Logo Mail Archive

[imapext] IMAP BODY STRUCTURE

Nigar Sultana <nigarsultana_n@yahoo.co.in> Sat, 29 August 2015 02:28 UTC

Return-Path: <nigarsultana_n@yahoo.co.in>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41B981B2CCC for <imapext@ietfa.amsl.com>; Fri, 28 Aug 2015 19:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.508
X-Spam-Level: *
X-Spam-Status: No, score=1.508 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SUBJ_ALL_CAPS=1.506] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id USlRK09ezE9h for <imapext@ietfa.amsl.com>; Fri, 28 Aug 2015 19:28:49 -0700 (PDT)
Received: from nm37.bullet.mail.ne1.yahoo.com (nm37.bullet.mail.ne1.yahoo.com [98.138.229.30]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 068461B2C51 for <imapext@ietf.org>; Fri, 28 Aug 2015 19:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.in; s=s2048; t=1440815328; bh=CQsfoCF8SLJSHxDU4KtLBbkviN5ZUaewymQqv6WoOt4=; h=Date:From:Reply-To:To:Subject:From:Subject; b=M1EY8vJFVB/qG4I+RPnRQ1Dn9co+dJcFk4dKBSzW5jDDzY4JfeLTvW4J0nlR+kJ86xhLwEQyEIFIcp+8EU1TXlDcQfmjSqEJ6bOosCeBbEXCSF9XIzqmQxofHYFX63nI1BWaduWeZzfGlzjSR57bPdK94/+L4lF1dCctskraR4pKK5sBL5zIvGTH9f+JeptfPY+h9gV1xKXWYtYmDL1jHS9qS8mdi+7OzRdgrMDHgzX4+nbK7LzLj6OR3Qv0Y3IXR+73AP8uZTEt9BARtp0nWfDMM9anZoflPBS1dpBcCIPyeLkC9gP8/ncZBMama20HVs/3fZHdKSaNHxTa4SZR0A==
Received: from [127.0.0.1] by nm37.bullet.mail.ne1.yahoo.com with NNFMP; 29 Aug 2015 02:28:48 -0000
Received: from [98.138.100.102] by nm37.bullet.mail.ne1.yahoo.com with NNFMP; 29 Aug 2015 02:26:08 -0000
Received: from [106.10.166.121] by tm101.bullet.mail.ne1.yahoo.com with NNFMP; 29 Aug 2015 02:26:07 -0000
Received: from [106.10.151.155] by tm10.bullet.mail.sg3.yahoo.com with NNFMP; 29 Aug 2015 02:26:06 -0000
Received: from [127.0.0.1] by omp1009.mail.sg3.yahoo.com with NNFMP; 29 Aug 2015 02:26:06 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 895042.31055.bm@omp1009.mail.sg3.yahoo.com
X-YMail-OSG: Spd.GR8VRDvqibgG_awM1M4Qrn3J_3o4JIvhhFHmalD.TsEli34O
Received: by 106.10.197.99; Sat, 29 Aug 2015 02:26:06 +0000
Date: Sat, 29 Aug 2015 02:26:06 +0000
From: Nigar Sultana <nigarsultana_n@yahoo.co.in>
To: "tss@iki.fi" <tss@iki.fi>, "chris.newman@oracle.com" <chris.newman@oracle.com>, "cyrus@daboo.name" <cyrus@daboo.name>, "imapext@ietf.org" <imapext@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, Brandon Long <blong@google.com>, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, "imapext@ietfa.amsl.com" <imapext@ietfa.amsl.com>, "imapext-request@ietf.org" <imapext-request@ietf.org>
Message-ID: <504503638.2022586.1440815166041.JavaMail.yahoo@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_2022585_145985936.1440815166031"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/LvYkG_adcwjgYWOCM5QB7-8oerc>
Subject: [imapext] IMAP BODY STRUCTURE
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Nigar Sultana <nigarsultana_n@yahoo.co.in>
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Aug 2015 02:28:51 -0000

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

To:Joe User <joe@user.org>, tel:0401234567

Cc:tel:+358501234567

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

To:Joe User <joe@user.org>

To:tel:0401234567

cc:tel:+358501234567

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 
RegardsNigar Sultana

v2.23.0 | Report a Bug | By Email