IETF Logo Mail Archive

Re: [imapext] IMAP BODY STRUCTURE

Jamie Nicolson <nicolson@google.com> Tue, 01 September 2015 03:51 UTC

Return-Path: <nicolson@google.com>
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 1E6A71B7A15 for <imapext@ietfa.amsl.com>; Mon, 31 Aug 2015 20:51:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 kOQEf2B8sRqa for <imapext@ietfa.amsl.com>; Mon, 31 Aug 2015 20:51:47 -0700 (PDT)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A83801B7A18 for <imapext@ietf.org>; Mon, 31 Aug 2015 20:51:47 -0700 (PDT)
Received: by vkbc123 with SMTP id c123so49339812vkb.3 for <imapext@ietf.org>; Mon, 31 Aug 2015 20:51:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=NvGAvgBadR/++WzC7eoYhsv4vkIBOr4IaVbIoL3Urr8=; b=SygR1m3W+tZ8YHpEKQfeTR+SlsfjdsGvfIF9+1r0q3zbWp6rmbJ8EGC9n8gZSifYEE 6aqqg6mUdhXIyjgcQtDdsqyJvhTBjZHTMBPwTWIiLHCk/7fOg6S0AdAUWKW1aqPqHQCD qqNkGXosk3JWiLVf/v7ofWwtNM2JRMvU+4kITbx8N/nGH+tHrauBTSijqCvdCWku53Ms wJc6ULQJa0aZegCALTOTFFHTw/IGSjazjLIhoEgNvgUWAqTMWRIrcsC4RNy0qNHk9/g9 Ubs+UFEYwAzVNfelF5B9JpkB60JM5xCqDAwG57h17GzDITLbrVZRtW62jEgyIpX//d2U 05SA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=NvGAvgBadR/++WzC7eoYhsv4vkIBOr4IaVbIoL3Urr8=; b=BfnD5mxCWYmIi/WG0nYniqw2w4Q7CNNRg0RmcI02OzuqFlh47JomRwx5PtpBtyxDWk stvWjP0GflpGJ1O9900qVfDc0tRhcsA8NXa1s510yUTh7t0suv5oDxhxgUuC5M8a6m16 EvQYxArngJl42KKL+HjTnRAj8SWxPqDNJPVzQjgtnMsoM71fwX6OuZpARNfGA+TKrLVe bPa3UAwTBDo/RwXilVwULwL22uADo+r9GGDw7QoiIQCZpU9QiQzMxRgEzBvSIkg+S4AE ayoWl0r9ahTMsBiwQ2MbSM4uehaTkxYL+ZDm1qBK3gLKY3HJjmt+1EYmnG5Qf1b+yYk0 Zfvg==
X-Gm-Message-State: ALoCoQnoxRYkZc8zXp84km9wDaqmS4SESgkmu4RqxQkwIG/wA0koKSkIxkcqIQue0M8p2y3VaVu+
X-Received: by 10.53.13.33 with SMTP id ev1mr25522658vdd.69.1441079506716; Mon, 31 Aug 2015 20:51:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.189.12 with HTTP; Mon, 31 Aug 2015 20:51:16 -0700 (PDT)
In-Reply-To: <504503638.2022586.1440815166041.JavaMail.yahoo@mail.yahoo.com>
References: <504503638.2022586.1440815166041.JavaMail.yahoo@mail.yahoo.com>
From: Jamie Nicolson <nicolson@google.com>
Date: Mon, 31 Aug 2015 20:51:16 -0700
Message-ID: <CACU8CfRFyUeYkkQQxi=p9mmSUepOsw3oE5sFhzSVwe8Pw44pOA@mail.gmail.com>
To: Nigar Sultana <nigarsultana_n@yahoo.co.in>
Content-Type: multipart/alternative; boundary="001a1135f274177c90051ea77874"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/tgCVRF590fgMabebP9GVAkO-FAM>
Cc: "imapext@ietf.org" <imapext@ietf.org>
Subject: Re: [imapext] IMAP BODY STRUCTURE
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: Tue, 01 Sep 2015 03:51:50 -0000

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.

On Fri, Aug 28, 2015 at 7:26 PM, Nigar Sultana <nigarsultana_n@yahoo.co.in>
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
> 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
>
> Regards
> Nigar Sultana
>
>
>
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext
>
>

v2.23.0 | Report a Bug | By Email