IETF Logo Mail Archive

Re: [imapext] General Request for Assignment (imap-keywords) (was: [JMAP] SMIME Attachments)

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Tue, 14 November 2017 08:25 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 171F9129A96 for <imapext@ietfa.amsl.com>; Tue, 14 Nov 2017 00:25:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 1Seu-kExw9vj for <imapext@ietfa.amsl.com>; Tue, 14 Nov 2017 00:25:28 -0800 (PST)
Received: from strange.aox.org (strange.aox.org [IPv6:2001:4d88:100c::1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80ABB128D19 for <imapext@ietf.org>; Tue, 14 Nov 2017 00:25:28 -0800 (PST)
Received: from fri.gulbrandsen.priv.no (localhost [127.0.0.1]) by strange.aox.org (Postfix) with ESMTP id 47A4FFA0076; Tue, 14 Nov 2017 08:25:25 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1510647925; bh=rCzNKEhXzLq7nLFMUHX5jomC07AFjNlfafWJyEMC2To=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ZgGyKcnd2I25oZ3NWATXdaATZI9v2C9HC3MAwiNcNnKkEPdkUagqPenWSnTVOeXYH BIMsJzQeQpVQavXWVvg5LuATxoXAExsHhaRcxRfZuH2WcPpaD4NnD/nE+wrgeH3PVa HK3zqxRKoiyqMj3kcJGfWrQ6f3Al00wVydKqEhTk=
Received: from arnt@gulbrandsen.priv.no by fri.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1510647924-20834-22429/11/24; Tue, 14 Nov 2017 08:25:24 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: vaibhav singh <vaibhavsinghacads@gmail.com>
Cc: imapext@ietf.org
Date: Tue, 14 Nov 2017 08:25:23 +0000
User-Agent: Trojita/v0.5-9-g8961725; Qt/4.8.6; X11; Linux; Devuan GNU/Linux 1.0 (jessie)
Mime-Version: 1.0
Message-Id: <c2f0b35e-1925-4769-9a22-c6663db1eb53@gulbrandsen.priv.no>
In-Reply-To: <CACZ1GipM4+91KL00_YDcUHSF0eVnjh8vZAddbk869O4J1w9ZfA@mail.gmail.com>
References: <CACZ1GipM4+91KL00_YDcUHSF0eVnjh8vZAddbk869O4J1w9ZfA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/eq34FPFCkwLnF6JYak7xArpAhZk>
Subject: Re: [imapext] General Request for Assignment (imap-keywords) (was: [JMAP] SMIME Attachments)
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.22
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, 14 Nov 2017 08:25:30 -0000

Hi,

sorry about the late response. I suck at the moment.

I don't understand the semantics here.

If present, it means that someone has checked and found an encrypted 
attachment. And if absent, it means nothing. There may or may not be an 
encrypted attachment.

So my question is, what advantage does this provide over checking the 
bodystructure?

Arnt

v2.23.0 | Report a Bug | By Email