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

vaibhav singh <vaibhavsinghacads@gmail.com> Mon, 13 November 2017 15:10 UTC

Return-Path: <vaibhavsinghacads@gmail.com>
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 8DFA4129571 for <imapext@ietfa.amsl.com>; Mon, 13 Nov 2017 07:10:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 1r1rbbW35jF6 for <imapext@ietfa.amsl.com>; Mon, 13 Nov 2017 07:10:05 -0800 (PST)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (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 14843129A84 for <imapext@ietf.org>; Mon, 13 Nov 2017 07:10:05 -0800 (PST)
Received: by mail-io0-x234.google.com with SMTP id g73so5360404ioj.8 for <imapext@ietf.org>; Mon, 13 Nov 2017 07:10:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=zCzPS3cR/aWt1UHXEq45YMb1sMr7IP8DeAE/oMTnYO0=; b=DdRTy24H7HZV4wr+3jdgVqeflu0b8RDEBbPPd6Ezm2cpW5GotuCvgF1Sgl+7JEBebJ ovMOEnhBQI+Beo7P1D6/z7pMSizPmILK/EliEX75eVeJ53HQ2yN0+5KRo54E2Vd6wtfw hyDI3vdNAEYrzXyNPRT2bWpOpyivfmAviLbhsFuDG00eLs3uDw+XeajXDb7XMbZrQ0Fk n4EHOnBqX/Lu/PmE7D+P/5p8UKqYtHLq8r03GjIJVWKkCXVsHCAFdlCuHX7vMsKqVOpZ zzghEqKNHZdDnCGYBAwH9fTOBo6e8UuXAi40Y0jBLetxclyJKau1Mu+RRDNHKzpAp/DV ZjOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=zCzPS3cR/aWt1UHXEq45YMb1sMr7IP8DeAE/oMTnYO0=; b=iRPU1Fx9PsLhl4KSJyCegjvBb88yesZ6itdCony+V8yikOTQMIQ1Q6U/JvxVnnjee/ TE1JVi58vRJC157WxhhgufKfpZ8F2B3H1NUBhCEVa98GLAXy4Fg0emN08xSUkoi/Az0o 0Fo7WII+OYL8PGHE+Pt5F3rcAt6pZyTaUbNW+MIFc0USV/29u67cjvB0BjIfn5i4WXJl 5OcHU2W+rLhVbPSmQoEye8MMa2URLMhuh7jnr03IQWpG2xypnZGETRw/QmPSB2TO19zQ /BXCLqMpoxC1q3CtL8+mcN+DmJ6EXDjgiUtZ4wIk2eWOQkNTsPCj0vpF329BprKrOLCW cHow==
X-Gm-Message-State: AJaThX5KMZt34v97JhQthvzk+Xr3YJjoscdIU5QXDfPeiZ7Pryi/+sL8 /0xyWM1JzB/+ru8bY154WGCe+X7GRD/JXkTj7XVHQw==
X-Google-Smtp-Source: AGs4zMY3/rz6HzH5nT/Q2ZClcEKYS7vunqh0yUB8zDrVs/i7Hi2+YM/VbbRl/91sUex6SiyOFtogiphUIpX6HMjXhnI=
X-Received: by 10.107.178.135 with SMTP id b129mr559442iof.276.1510585804073; Mon, 13 Nov 2017 07:10:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.79.31.3 with HTTP; Mon, 13 Nov 2017 07:10:03 -0800 (PST)
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Mon, 13 Nov 2017 20:40:03 +0530
Message-ID: <CACZ1GipM4+91KL00_YDcUHSF0eVnjh8vZAddbk869O4J1w9ZfA@mail.gmail.com>
To: imapext@ietf.org
Content-Type: multipart/alternative; boundary="001a114c9d0c412f9f055ddeaabd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/yPe7HegE6WYo7x7XQOoChPJr_Cg>
Subject: [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: Mon, 13 Nov 2017 15:10:11 -0000

Hello,

In order to optimize the way attachments inside encrypted mail are treated
by the MUA, I am suggesting the registration of a "$HasEncryptedAttachment"
to the IMAP Keywords registry[RFC5788].

Please find details of the original proposal below:

> Type of Assignment:
>  Requesting for addition of a keyword "$HasEncryptedAttachment" to the
> IMAP Keywords registry[RFC5788].
>
> Registry:
> The registration request is being made for IMAP Keywords
> registry[RFC5788].
>
> Description:
>     This flag can be useful so that the MUA can display an attachment
> icon when displaying
>    messages in the folder, without it having to decrypt the message.
> This flag can also be used to filter
>    encrypted emails with attachments.
>
> Additional Info:
>  The $HasEncryptedAttachment IMAP keyword will be used by IMAP/JMAP
> MUA to
>    specify that the marked encrypted message contains an attachment.
> A MUA-with-keys
>    sets this keyword when it sees a message having an attachment
> before encryption.
>     This flag can be useful so that the MUA can display an attachment
> icon when displaying
>    messages in the folder, without it having to decrypt the message.
> This flag can also be used to filter
>    encrypted emails with attachments.
>
> Once set, any entity (be it the MDA or receiver's MUA) SHOULD not edit
> the flag.
>
> JMAP Message Stores SHOULD be able to store the
> $HasEncryptedAttachment keyword.
> They MUST preserve it on the COPY operation.  The servers MUST
> support the SEARCH KEYWORD $HasEncryptedAttachment.

Please find comments by Mr. Barry Leiba, and my answers below (marked as
<vs>):

1.) There should also be a “has no attachment” keyword, so the MUA doesn’t
have to check either way and only needs to check if neither is set.

 <vs>  Agreed. </vs>

2.) The keyword is poorly named: it’s not about an encrypted attachment,
but about any attachment.  I suppose that in the end there no reason to
mention encryption at all, because it could be used for any message, though
it’s less important for unencrypted ones.

 <vs> Not really sure. </vs>

3.) How will the server know to set the keyword?  The server also can’t
decrypt an incoming message, and so it can’t check.  Where does the
knowledge come from?  It seems that it could only work for messages that
are created locally, with the keyword set at creation.

  <vs> A better use case for the flag could be: the server could set this
flag to true when it sees the mime being decrypted the first time, so that
any scans later on would not have to decrypt the mail again to know the
presence of the attachment inside it </vs>

Will this be useful?

-- 

Regards,
Vaibhav Singh