Internet Assigned Numbers Authority
JSON Meta Application Protocol (JMAP)
Created
2019-03-28
Last Updated
2025-05-02
Available Formats
[IMG]
XML [IMG]
HTML [IMG]
Plain text
Registries Included Below
??JMAP Capabilities
??JMAP Error Codes
??JMAP Data Types
JMAP Capabilities
Expert(s)
Neil Jenkins, Chris Newman, Arnt Gulbrandsen, Joris Baum
Reference
[RFC8620]
Available Formats
[IMG]
CSV
Range Registration Procedures
intended use field is ¡°common" or ¡°placeholder¡± Specification Required
all other values Expert Review
Capability Name Intended Use Change Controller Security and Privacy Considerations Reference
urn:ietf:params:jmap:core common IETF [RFC8620, Section 8] [RFC8620, Section 2]
urn:ietf:params:jmap:error: placeholder IETF [RFC8620, Section 8] [RFC8620, Section 9.5]
urn:ietf:params:jmap:mail common IETF [RFC8621, Section 9] [RFC8621]
urn:ietf:params:jmap:mdn common IETF [RFC9007, Section 5] [RFC9007]
urn:ietf:params:jmap:smimeverify common IETF [RFC9219, Section 6] [RFC9219]
urn:ietf:params:jmap:submission common IETF [RFC8621, Section 9] [RFC8621]
urn:ietf:params:jmap:vacationresponse common IETF [RFC8621, Section 9] [RFC8621]
urn:ietf:params:jmap:blob common IETF [RFC9404, Section 5] [RFC9404]
urn:ietf:params:jmap:quota common IETF [RFC9425, Section 7] [RFC9425]
urn:ietf:params:jmap:sieve common IETF [RFC9661, Section 5] [RFC9661]
urn:ietf:params:jmap:principals common IETF [RFC9670, Section 6] [RFC9670]
urn:ietf:params:jmap:principals:owner common IETF [RFC9670, Section 6] [RFC9670]
urn:ietf:params:jmap:contacts common IETF [RFC9610, Section 6] [RFC9610]
urn:ietf:params:jmap:calendars common IETF [RFC-ietf-jmap-calendars-22, Section [RFC-ietf-jmap-calendars-22]
1.5.1]
urn:ietf:params:jmap:principals:availability common IETF [RFC-ietf-jmap-calendars-22, Section [RFC-ietf-jmap-calendars-22]
1.5.2]
urn:ietf:params:jmap:webpush-vapid common IETF [RFC9749, Section 6] [RFC9749]
JMAP Error Codes
Registration Procedure(s)
Expert Review
Expert(s)
Neil Jenkins, Chris Newman, Arnt Gulbrandsen, Joris Baum
Reference
[RFC8620]
Available Formats
[IMG]
CSV
JMAP Error Code Intended Use Change Description Reference
Controller
accountNotFound common IETF The accountId does not correspond to a valid account. [RFC8620, Section 3.6.2]
The accountId given corresponds to a valid account,
accountNotSupportedByMethod common IETF but the account does not support this method or data [RFC8620, Section 3.6.2]
type.
This method modifies state, but the account is
accountReadOnly common IETF read-only (as returned on the corresponding Account [RFC8620, Section 3.6.2]
object in the JMAP Session resource).
anchorNotFound common IETF An anchor argument was supplied, but it cannot be [RFC8620, Section 5.5]
found in the results of the query.
The server forbids duplicates, and the record already
alreadyExists common IETF exists in the target account. An existingId property [RFC8620, Section 5.4]
of type Id MUST be included on the SetError object
with the id of the existing record.
cannotCalculateChanges common IETF The server cannot calculate the changes from the state [RFC8620, Section 5.2 and 5.6]
string given by the client.
forbidden common IETF The action would violate an ACL or other permissions [RFC8620, Section 3.6.2, 5.3, and
policy. 7.2.1]
fromAccountNotFound common IETF The fromAccountId does not correspond to a valid [RFC8620, Section 5.4 and 6.3]
account.
The fromAccountId given corresponds to a valid
fromAccountNotSupportedByMethod common IETF account, but the account does not support this data [RFC8620, Section 5.4]
type.
invalidArguments common IETF One of the arguments is of the wrong type or otherwise [RFC8620, Section 3.6.2]
invalid, or a required argument is missing.
invalidPatch common IETF The PatchObject given to update the record was not a [RFC8620, Section 5.3]
valid patch.
invalidProperties common IETF The record given is invalid. [RFC8620, Section 5.3]
notFound common IETF The id given cannot be found. [RFC8620, Section 5.3]
The content type of the request was not
notJSON common IETF application/json, or the request did not parse as [RFC8620, Section 3.6.1]
I-JSON.
notRequest common IETF The request parsed as JSON but did not match the type [RFC8620, Section 3.6.1]
signature of the Request object.
overQuota common IETF The create would exceed a server-defined limit on the [RFC8620, Section 5.3]
number or total size of objects of this type.
Too many objects of this type have been created
rateLimit common IETF recently, and a server-defined rate limit has been [RFC8620, Section 5.3]
reached. It may work if tried again later.
The total number of actions exceeds the maximum number
requestTooLarge common IETF the server is willing to process in a single method [RFC8620, Section 5.1 and 5.3]
call.
invalidResultReference common IETF The method used a result reference for one of its [RFC8620, Section 3.6.2]
arguments, but this failed to resolve.
An unexpected or unknown error occurred during the
serverFail common IETF processing of the call. The method call made no [RFC8620, Section 3.6.2]
changes to the server's state.
Some, but not all, expected changes described by the
serverPartialFail limited IETF method occurred. The client MUST resynchronise [RFC8620, Section 3.6.2]
impacted data to determine the server state.
Some internal server resource was temporarily
serverUnavailable common IETF unavailable. Attempting the same operation later [RFC8620, Section 3.6.2]
(perhaps after a backoff with a random factor) may
succeed.
singleton common IETF This is a singleton type, so you cannot create another [RFC8620, Section 5.3]
one or destroy the existing one.
stateMismatch common IETF An ifInState argument was supplied, and it does not [RFC8620, Section 5.3]
match the current state.
The action would result in an object that exceeds a
tooLarge common IETF server-defined limit for the maximum size of a single [RFC8620, Section 5.3]
object of this type.
tooManyChanges common IETF There are more changes than the client's maxChanges [RFC8620, Section 5.6]
argument.
The client included a capability in the "using"
unknownCapability common IETF property of the request that the server does not [RFC8620, Section 3.6.1]
support.
unknownMethod common IETF The server does not recognise this method name. [RFC8620, Section 3.6.2]
unsupportedFilter common IETF The filter is syntactically valid, but the server [RFC8620, Section 5.5]
cannot process it.
The sort is syntactically valid but includes a
unsupportedSort common IETF property the server does not support sorting on or a [RFC8620, Section 5.5]
collation method it does not recognise.
The client requested an object be both updated and
willDestroy common IETF destroyed in the same /set request, and the server has [RFC8620, Section 5.3]
decided to therefore ignore the update.
The Mailbox still has at least one child Mailbox. The
mailboxHasChild common IETF client MUST remove these before it can delete the [RFC8621, Section 2.5]
parent Mailbox.
mailboxHasEmail common IETF The Mailbox has at least one message assigned to it, [RFC8621, Section 2.5]
and the onDestroyRemoveEmails argument was false.
blobNotFound common IETF At least one blob id referenced in the object doesn't [RFC8621, Section 4.6]
exist.
tooManyKeywords common IETF The change to the Email's keywords would exceed a [RFC8621, Section 4.6]
server-defined maximum.
tooManyMailboxes common IETF The change to the set of Mailboxes that this Email is [RFC8621, Section 4.6]
in would exceed a server-defined maximum.
invalidEmail common IETF The Email to be sent is invalid in some way. [RFC8621, Section 7.5]
The envelope [RFC-ietf-emailcore-rfc5321bis-43]
tooManyRecipients common IETF (supplied or generated) has more recipients than the [RFC8621, Section 7.5]
server allows.
The envelope [RFC-ietf-emailcore-rfc5321bis-43]
noRecipients common IETF (supplied or generated) does not have any rcptTo email [RFC8621, Section 7.5]
addresses.
The rcptTo property of the envelope
invalidRecipients common IETF [RFC-ietf-emailcore-rfc5321bis-43] (supplied or [RFC8621, Section 7.5]
generated) contains at least one rcptTo value that is
not a valid email address for sending to.
The server does not permit the user to send a message
forbiddenMailFrom common IETF with this envelope From address [RFC8621, Section 7.5]
[RFC-ietf-emailcore-rfc5321bis-43].
The server does not permit the user to send a message
forbiddenFrom common IETF with the From header field [RFC8621, Sections 6.3 and 7.5]
[RFC-ietf-emailcore-rfc5322bis-12] of the message to
be sent.
forbiddenToSend common IETF The user does not have permission to send at all right [RFC8621, Section 7.5]
now.
The message has the "$mdnsent" keyword already set.
mdnAlreadySent common IETF The client MUST NOT try again to send an MDN for this [RFC9007, Section 2.1]
message.
The server does not recognise this data type, or the
unknownDataType common IETF capability to enable it is not present in the current [RFC9404]
Request Object.
The SieveScript violates the Sieve grammar [RFC5228],
invalidSieve common IETF and/or one or more extensions mentioned in the [RFC9661, Section 2.4]
script's "require" statement(s) are not supported by
the Sieve interpreter.
sieveIsActive common IETF The client tried to destroy the active SieveScript. [RFC9661, Section 2.4]
The AddressBook has at least one ContactCard assigned
addressBookHasContents common IETF to it, and the "onDestroyRemoveContents" argument was [RFC9610, Section 2.3]
false.
The Calendar has at least one CalendarEvent assigned [RFC-ietf-jmap-calendars-22,
calendarHasEvent common IETF to it, and the "onDestroyRemoveEvents" argument was Section 4.3]
false.
The server was requested to send scheduling messages, [RFC-ietf-jmap-calendars-22,
noSupportedScheduleMethods common IETF but does not support any of the methods available for Section 5.8]
at least one of the recipients.
cannotCalculateOccurrences common IETF The server cannot expand a recurrence required to [RFC-ietf-jmap-calendars-22,
return the results for the requested query. Section 5.10]
JMAP Data Types
Registration Procedure(s)
Specification Required
Expert(s)
Ken Murchison, Neil Jenkins, Arnt Gulbrandsen, Joris Baum
Reference
[RFC9404]
Available Formats
[IMG]
CSV
Type Name Can Reference Blobs Can Use for State Change Capability Reference
Core No No urn:ietf:params:jmap:core [RFC8620]
PushSubscription No No urn:ietf:params:jmap:core [RFC8620]
Mailbox Yes Yes urn:ietf:params:jmap:mail [RFC8621]
Thread Yes Yes urn:ietf:params:jmap:mail [RFC8621]
Email Yes Yes urn:ietf:params:jmap:mail [RFC8621]
EmailDelivery No Yes urn:ietf:params:jmap:mail [RFC8621]
SearchSnippet No No urn:ietf:params:jmap:mail [RFC8621]
Identity No Yes urn:ietf:params:jmap:submission [RFC8621]
EmailSubmission No Yes urn:ietf:params:jmap:submission [RFC8621]
VacationResponse No Yes urn:ietf:params:jmap:vacationresponse [RFC8621]
MDN No No urn:ietf:params:jmap:mdn [RFC9007]
Quota No Yes urn:ietf:params:jmap:quota [RFC9425]
SieveScript Yes Yes urn:ietf:params:jmap:sieve [RFC9661]
Principal No Yes urn:ietf:params:jmap:principals [RFC9670]
ShareNotification No Yes urn:ietf:params:jmap:principals [RFC9670]
AddressBook No Yes urn:ietf:params:jmap:contacts [RFC9610]
ContactCard Yes Yes urn:ietf:params:jmap:contacts [RFC9610]
Calendar No Yes urn:ietf:params:jmap:calendars [RFC-ietf-jmap-calendars-22]
CalendarEvent Yes Yes urn:ietf:params:jmap:calendars [RFC-ietf-jmap-calendars-22]
CalendarEventNotification No Yes urn:ietf:params:jmap:calendars [RFC-ietf-jmap-calendars-22]
ParticipantIdentity No Yes urn:ietf:params:jmap:calendars [RFC-ietf-jmap-calendars-22]
Licensing Terms
Presently we were in a very dark road, and at a point where it dropped suddenly between steep sides we halted in black shadow. A gleam of pale sand, a whisper of deep flowing waters, and a farther glimmer of more sands beyond them challenged our advance. We had come to a "grapevine ferry." The scow was on the other side, the water too shoal for the horses to swim, and the bottom, most likely, quicksand. Out of the blackness of the opposite shore came a soft, high-pitched, quavering, long-drawn, smothered moan of woe, the call of that snivelling little sinner the screech-owl. Ferry murmured to me to answer it and I sent the same faint horror-stricken tremolo back. Again it came to us, from not farther than one might toss his cap, and I followed Ferry down to the water's edge. The grapevine guy swayed at our side, we heard the scow slide from the sands, and in a few moments, moved by two videttes, it touched our shore. Soon we were across, the two videttes riding with us, and beyond a sharp rise, in an old opening made by the swoop of a hurricane, we entered the silent unlighted bivouac of Ferry's scouts. Ferry got down and sat on the earth talking with Quinn, while the sergeants quietly roused the sleepers to horse. Plotinus is driven by this perplexity to reconsider the whole theory of Matter.477 He takes Aristotle¡¯s doctrine as the groundwork of his investigation. According to this, all existence is divided into Matter and Form. What we know of things¡ªin other words, the sum of their differential characteristics¡ªis their Form. Take away this, and the unknowable residuum is their Matter. Again, Matter is the vague indeterminate something out of which particular Forms are developed. The two are related as Possibility to Actuality, as the more generic to the more specific substance through every grade of classification and composition. Thus there are two Matters, the one sensible and the other intelligible. The former constitutes the common substratum of bodies, the other the common element of ideas.478 The general distinction between Matter and Form was originally suggested to Aristotle by Plato¡¯s remarks on the same subject; but he differs325 from his master in two important particulars. Plato, in his Timaeus, seems to identify Matter with space.479 So far, it is a much more positive conception than the ?λη of the Metaphysics. On the other hand, he constantly opposes it to reality as something non-existent; and he at least implies that it is opposed to absolute good as a principle of absolute evil.480 Thus while the Aristotelian world is formed by the development of Power into Actuality, the Platonic world is composed by the union of Being and not-Being, of the Same and the Different, of the One and the Many, of the Limit and the Unlimited, of Good and Evil, in varying proportions with each other. The Lawton woman had heard of an officer's family at Grant, which was in need of a cook, and had gone there. [See larger version] On the 8th of July an extraordinary Privy Council was summoned. All the members, of whatever party, were desired to attend, and many were the speculations as to the object of their meeting. The general notion was that it involved the continuing or the ending of the war. It turned out to be for the announcement of the king's intended marriage. The lady selected was Charlotte, the second sister of the Duke of Mecklenburg-Strelitz. Apart from the narrowness of her education, the young princess had a considerable amount of amiability, good sense, and domestic taste. These she shared with her intended husband, and whilst they made the royal couple always retiring, at the same time they caused them to give, during their lives, a moral air to their court. On the 8th of September Charlotte arrived at St. James's, and that afternoon the marriage took place, the ceremony being performed by the Archbishop of Canterbury. On the 22nd the coronation took place with the greatest splendour. Mother and girls were inconsolable, for each had something that they were sure "Si would like," and would "do him good," but they knew Josiah Klegg, Sr., well enough to understand what was the condition when he had once made up his mind. CHAPTER V. THE YOUNG RECRUITS Si proceeded to deftly construct a litter out of the two guns, with some sticks that he cut with a knife, and bound with pawpaw strips. His voice had sunk very low, almost to sweetness. A soft flurry of pink went over her face, and her eyelids drooped. Then suddenly she braced herself, pulled herself taut, grew combative again, though her voice shook. HoME²Ô¾®Ïè̫ʲôÐÇ×ù
ENTER NUMBET 0016www.jbchain.com.cn
www.ipingo.com.cn
langnest.com.cn
jkpa.com.cn
www.j-xing.com.cn
syfyfz.com.cn
www.mlcygs.org.cn
oldjohn.com.cn
sybn100.com.cn
www.sheatour.com.cn