Re: [Jmap] Jmap Digest, Vol 9, Issue 6

vaibhav singh <vaibhavsinghacads@gmail.com> Fri, 11 August 2017 04:54 UTC

MIME-Version: 1.0
In-Reply-To: <mailman.36.1502305207.14660.jmap@ietf.org>
References: <mailman.36.1502305207.14660.jmap@ietf.org>
From: vaibhav singh <vaibhavsinghacads@gmail.com>
Date: Fri, 11 Aug 2017 10:24:14 +0530
Message-ID: <CACZ1Gir1381pCZciQm_3QpSkUcqJO534v7YfbvE9=Pyt5T1sag@mail.gmail.com>
To: jmap@ietf.org
Content-Type: multipart/alternative; boundary="001a1144d62cde51b80556731a4a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/ZnNU1STbJ_7RFr1Okf38wZwSk5k>
Subject: Re: [Jmap] Jmap Digest, Vol 9, Issue 6
Precedence: list

On Thu, Aug 10, 2017 at 12:30 AM, <jmap-request@ietf.org> wrote:

>
>
>
> ---------- Forwarded message ----------
> From: Alexey Melnikov <alexey.melnikov@isode.com>
> To: Neil Jenkins <neilj@fastmailteam.com>, jmap@ietf.org
> Cc:
> Bcc:
> Date: Wed, 9 Aug 2017 11:53:38 +0100
> Subject: Re: [Jmap] S/MIME for JMAP
> On 07/08/2017 09:05, Neil Jenkins wrote:
>
> On Wed, 2 Aug 2017, at 06:23 AM, vaibhav singh wrote:
>>
>>> I have one straight question though; how is S/MIME going to be supported
>>> for JMAP?
>>>
>>
>> A client can fetch the raw RFC5322 message to decrypt and/or verify
>> S/MIME; this is really the only option if the client has the private keys.
>>
>
> Right.
>
> If the private keys are on the server (some corporate systems sign/verify
>> at the gateway) the server can transparently decrypt and could add a
>> keyword to say this message has been verified. This is outside the scope of
>> the JMAP spec itself though (any keyword(s) you added to the IANA registry
>> can be used in either IMAP or JMAP of course).
>>
>
> There is a similar case of webmail which can access use keys on behalf of
> a user.
>
> If people are interested in thinking about/experimenting with possible
> JMAP extensions for S/MIME for the latter case, please let me know.
>

+1

-Vaibhav

>
> Best Regards,
> Alexey
>
>
>
>

Re: [Jmap] Jmap Digest, Vol 9, Issue 6 vaibhav singh