IETF Logo Mail Archive

Re: [imapext] IMAP BODY STRUCTURE

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Wed, 02 September 2015 09:21 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
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 E93731A6FA3 for <imapext@ietfa.amsl.com>; Wed, 2 Sep 2015 02:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.801
X-Spam-Level:
X-Spam-Status: No, score=-0.801 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 VmqXba5ogIHT for <imapext@ietfa.amsl.com>; Wed, 2 Sep 2015 02:21:46 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4B661B366F for <imapext@ietf.org>; Wed, 2 Sep 2015 02:21:45 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 7454AFA0035; Wed, 2 Sep 2015 09:21:43 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1441185703; bh=YJRaLoDfs4ujYmw35FfereFtNJ7Ls8I+I7F5CcscQ6k=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ltjzIuZH7uZEXs0gpG08L/cu64ixNgAm//R8dNt8HC38T0S2BSQXWAt1WnTLz5+zH k+iL0zMDbOvWLYZqBK4WHii9Aw9+MugwRPxf6NwBX/lucO32aHtMDBnqBUj2e36m8e SKoqlBlyJaeeCAcnv1hXgvYQxYQCgAVf4CuMGhF8=
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1441185702-32696-32695/11/10; Wed, 2 Sep 2015 09:21:42 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: imapext@ietf.org
Date: Wed, 02 Sep 2015 10:27:11 +0100
User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Debian GNU/Linux 8.1 (jessie)
Mime-Version: 1.0
Message-Id: <5500265b-34c8-4338-9236-165aabcfc1f6@gulbrandsen.priv.no>
In-Reply-To: <2100501727.323720.1441185169146.JavaMail.yahoo@mail.yahoo.com>
References: <55E57BA2.1080309@isode.com> <2100501727.323720.1441185169146.JavaMail.yahoo@mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/WfKwDGf6q_ivQl-GBNZoDjtjGjU>
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: Wed, 02 Sep 2015 09:21:48 -0000

Nigar Sultana writes:
> support based on client enabled extension, does it mean client 
> and server should use extension commands for BODYSTRUCTURE. 
> Instead of using standard command, should client use command 
> something like XBODYSTRUCTURE. please provide your feedback
>
> The extension are usually published by server in capabilities. 

Some extensions are advertised by servers but enabled by clients, RFC6855 
is an example. Your proposal is like 6855 in that if a server were to use 
it unilaterally, a strictly parsing client would see a syntax error.

The conventional way is to use a command such as "ENABLE CPIM" to enable 
the extra bodystructure processing in the server, where CPIM is the name of 
the IMAP capability.

Arnt

v2.23.0 | Report a Bug | By Email