rfc9007v3.txt		rfc9007.txt
	skipping to change at line 310 ¶		skipping to change at line 310 ¶
	rateLimit: Too many MDNs or email messages have been created		rateLimit: Too many MDNs or email messages have been created
	recently, and a server-defined rate limit has been reached. It		recently, and a server-defined rate limit has been reached. It
	may work if tried again later.		may work if tried again later.
	invalidProperties: The record given is invalid in some way.		invalidProperties: The record given is invalid in some way.
	The following is a new SetError:		The following is a new SetError:
	mdnAlreadySent: The message has the "$mdnsent" keyword already set.		mdnAlreadySent: The message has the "$mdnsent" keyword already set.
	If the accountId or identityId given cannot be found, the method call		If the "accountId" or "identityId" given cannot be found, the method
	is rejected with an "invalidArguments" error.		call is rejected with an "invalidArguments" error.
	The client MUST NOT issue an "MDN/send" request if the message has		The client MUST NOT issue an "MDN/send" request if the message has
	the "$mdnsent" keyword set.		the "$mdnsent" keyword set.
	When sending the MDN, the server is in charge of generating the		When sending the MDN, the server is in charge of generating the
	"originalRecipient" and "originalMessageId" fields according to		"originalRecipient" and "originalMessageId" fields according to
	[RFC8098]. "finalRecipient" will also generally be generated by the		[RFC8098]. "finalRecipient" will also generally be generated by the
	server based on the provided identity, but if specified by the client		server based on the provided identity, but if specified by the client
	and allowed (see Section 5), the server will use the client-provided		and allowed (see Section 5), the server will use the client-provided
	value.		value.
	skipping to change at line 381 ¶		skipping to change at line 381 ¶
	A list of blob ids given that could not be found or null if none.		A list of blob ids given that could not be found or null if none.
	The following additional errors may be returned instead of the "MDN/		The following additional errors may be returned instead of the "MDN/
	parse" response:		parse" response:
	requestTooLarge: The number of ids requested by the client exceeds		requestTooLarge: The number of ids requested by the client exceeds
	the maximum number the server is willing to process in a single		the maximum number the server is willing to process in a single
	method call.		method call.
	invalidArguments: If the given accountId cannot be found, the MDN		invalidArguments: If the given "accountId" cannot be found, the MDN
	parsing is rejected with an "invalidArguments" error.		parsing is rejected with an "invalidArguments" error.
	3. Samples		3. Samples
	3.1. Sending an MDN for a Received Email Message		3.1. Sending an MDN for a Received Email Message
	A client can use the following request to send an MDN back to the		A client can use the following request to send an MDN back to the
	sender:		sender:
	[[ "MDN/send", {		[[ "MDN/send", {
	skipping to change at line 567 ¶		skipping to change at line 567 ¶
	5. Security Considerations		5. Security Considerations
	The same considerations regarding MDN (see [RFC8098] and [RFC3503])		The same considerations regarding MDN (see [RFC8098] and [RFC3503])
	apply to this document.		apply to this document.
	In order to reinforce trust regarding the relation between the user		In order to reinforce trust regarding the relation between the user
	sending an email message and the identity of this user, the server		sending an email message and the identity of this user, the server
	SHOULD validate in conformance to the provided Identity that the user		SHOULD validate in conformance to the provided Identity that the user
	is permitted to use the "finalRecipient" value and return a		is permitted to use the "finalRecipient" value and return a
	forbiddenFrom error if not.		"forbiddenFrom" error if not.
	6. Normative References		6. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119,		Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<https://www.rfc-editor.org/info/rfc2119>.		<https://www.rfc-editor.org/info/rfc2119>.
	[RFC3503] Melnikov, A., "Message Disposition Notification (MDN)		[RFC3503] Melnikov, A., "Message Disposition Notification (MDN)
	profile for Internet Message Access Protocol (IMAP)",		profile for Internet Message Access Protocol (IMAP)",
End of changes. 3 change blocks.
	4 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/