JMAP extension for S/MIME signing and encryption

is a JSON based application protocol for synchronising email data between a client and a server. This document describes an extension to JMAP for sending S/MIME signed and encrypted messages . It allows JMAP server to sign/encrypt messages on user's behalf.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

The capabilities object is returned as part of the standard JMAP Session object; see the JMAP spec. Servers supporting _this_ specification MUST add a property called "urn:ietf:params:jmap:smime-advanced" to the capabilities object. The value of this property is an empty object in both the JMAP session _capabilities_ property and an account's _accountCapabilities_ property.

defines Email/set method for creating new email messages. This document defines the following additional request arguments that can be used to create S/MIME signed and/or encrypted messages: smimeSign: "Boolean" (default: false). If included and has the value "true", this requests the JMAP server to create an S/MIME signed message from the message constructed according to other specified arguments (the "original message"). This is done by encapsulating the original message either inside application/pkcs7-mime or multipart/signed container. (smimeSignOpaque argument (see below) controls which of the two mechanisms is used.) The signature's private key/certificate is associated with the email address in the Sender header field, if present; otherwise, it is associated with the email address in the From header field, if present. If multiple addresses are present in one of these header fields, or there is more than one Sender/From header field, the server SHOULD reject the Email/set as invalid with the "invalidEmail" error code; otherwise, it MUST take the first address in the last Sender/From header field. If JMAP account is not authorized to sign message as the selected sender (as above), it SHOULD return "signedSenderNotAllowed" error code. smimeEncrypt: "Boolean" (default: false). If included and has the value "true", this requests the JMAP server to create an S/MIME encrypted message from the constructed message. This is done by encapsulating the message inside application/pkcs7-mime media type. The message MUST be encrypted to the sender and all To/Cc/Bcc recipients. This extension assumes that there is some kind of per user or organizational addressbook, that can be used to lookup public keys of recipients. If lookup of a particular public key fails, or results in an expired or revoked certificate, the Email/set operation MUST fail with the "validEncryptionKeyNotFound" error code. smimeHeaderProtect: "Boolean" (default: true). If has the value "true", this requests the JMAP server to use S/MIME header protection as specified in when at least one of smimeEncrypt/smimeSign is true. smimeSignOpaque: "Boolean" (default: true). If has the value "true", this requests the JMAP server to use application/pkcs7-mime media type for S/MIME signing, otherwise multipart/signed media type. If both "smimeSign" and "smimeEncrypt" are set to true, the message is first signed and then the signed version is encrypted (in that order). (Note that this extension doesn't allow management of private keys/certificates. How private keys are managed or configured for a particular user is out of scope for this document.)

defines Email/get method for retrieving information about email messages. This document defines the following additional request arguments of the "bodyProperties" object that can be used to facilitate decryption of S/MIME encrypted messages: smimeBlobId: "Id|null". The id representing the raw octets of the decrypted contents of the part. When processing this request argument, the server first removes the Content-Transfer-Encoding (see then "blobId" request argument in RFC 8621). If the Content-Transfer-Encoding is supported by the server, the content is then S/MIME decrypted. The resulting Id can be used in Email/parse method to import the decrypted message. If the body part is not encrypted, the returned smimeBlobId attribute has the same value as the "blobId" attribute.

IANA is requested to register the "smime" JMAP Capability as follows: Capability Name: "urn:ietf:params:jmap:smime-advanced" Specification document: this document Intended use: common Change Controller: IETF Security and privacy considerations: this document,

JMAP Error Code: signedSenderNotAllowed Intended use: common Change controller: IETF Reference: This document, Description: JMAP account is not authorized to S/MIME sign message as the specified sender.

JMAP Error Code: validEncryptionKeyNotFound Intended use: common Change controller: IETF Reference: This document, Description: S/MIME encrypted message can't be generated because no valid certificate (non expired and non revoked) can be found for one of recipients.

This JMAP extension assumes trust between the user and the JMAP server for purposes of signing and encrypting messages on user's behalf. This JMAP extension also relies on access to user's (or organization's) addressbook which contain up-to-date certificates for recipients. This JMAP extension doesn't support management of user's private keys and corresponding certificates.