rfc9979v1.txt		rfc9979.txt
	skipping to change at line 251 ¶		skipping to change at line 251 ¶
	message structure. This is particularly useful for displaying		message structure. This is particularly useful for displaying
	attachment indicators in message lists or implementing attachment-		attachment indicators in message lists or implementing attachment-
	based filtering.		based filtering.
	The $hasattachment and $hasnoattachment keywords are mutually		The $hasattachment and $hasnoattachment keywords are mutually
	exclusive. A message MUST NOT have both keywords set simultaneously.		exclusive. A message MUST NOT have both keywords set simultaneously.
	4.1. $hasattachment		4.1. $hasattachment
	The $hasattachment keyword indicates that a message has one or more		The $hasattachment keyword indicates that a message has one or more
	attachments. It is set by the server during message delivery or by		attachments. It is set by the server during message delivery;
	the client (if neither $hasattachment nor $hasnoattachment is		otherwise, it is set by the client (if neither $hasattachment nor
	currently set).		$hasnoattachment is currently set).
	This keyword enables clients to indicate attachments (e.g., paperclip		This keyword enables clients to indicate attachments (e.g., paperclip
	icons) in message lists without having to fetch the full MIME		icons) in message lists without having to fetch the full MIME
	structure for each message. It also facilitates attachment-based		structure for each message. It also facilitates attachment-based
	filtering and search operations.		filtering and search operations.
	When using JMAP, the "hasAttachment" Email property MUST reflect the		When using JMAP, the "hasAttachment" Email property MUST reflect the
	same information as this keyword for consistency across protocols.		same information as this keyword for consistency across protocols.
	4.2. $hasnoattachment		4.2. $hasnoattachment
	The $hasnoattachment keyword explicitly indicates that a message does		The $hasnoattachment keyword explicitly indicates that a message does
	not have any attachments. It is set by the server during message		not have any attachments. It is set by the server during message
	delivery or by the client (if neither $hasattachment nor		delivery; otherwise, it is set by the client (if neither
	$hasnoattachment is currently set).		$hasattachment nor $hasnoattachment is currently set).
	This keyword complements $hasattachment by providing definitive		This keyword complements $hasattachment by providing definitive
	information about messages that have been analyzed but found to		information about messages that have been analyzed but found to
	contain no attachments. The absence of $hasattachment alone is		contain no attachments. The absence of $hasattachment alone is
	inconclusive, as it might simply mean the message hasn't been		inconclusive, as it might simply mean the message hasn't been
	processed for attachment detection.		processed for attachment detection.
	This explicit distinction is important for clients that need to know		This explicit distinction is important for clients that need to know
	whether attachment detection has been performed on a message. When		whether attachment detection has been performed on a message. When
	using JMAP, the "hasAttachment" Email property MUST reflect the same		using JMAP, the "hasAttachment" Email property MUST reflect the same
	skipping to change at line 397 ¶		skipping to change at line 397 ¶
	The $autosent keyword identifies messages that were automatically		The $autosent keyword identifies messages that were automatically
	generated and sent by the system on behalf of the user, typically in		generated and sent by the system on behalf of the user, typically in
	response to user-defined filtering rules or settings.		response to user-defined filtering rules or settings.
	This keyword is set by the server on the user's copy of vacation		This keyword is set by the server on the user's copy of vacation
	auto-replies, automated responses, or other system-generated messages		auto-replies, automated responses, or other system-generated messages
	sent on behalf of the user. It allows clients to clearly distinguish		sent on behalf of the user. It allows clients to clearly distinguish
	these messages from those directly composed and sent by the user.		these messages from those directly composed and sent by the user.
	Supporting clients can present these messages differently in the sent		Supporting clients can present these messages differently in the
	items folder, such as with a distinct indicator (e.g., icon or label)		\Sent mailbox, such as with a distinct indicator (e.g., icon or
	indicating their automated nature. This helps prevent user confusion		label) indicating their automated nature. This helps prevent user
	when they encounter messages they don't remember writing,		confusion when they encounter messages they don't remember writing,
	particularly in the case of vacation responses or other automated		particularly in the case of vacation responses or other automated
	replies that may have been configured and then forgotten.		replies that may have been configured and then forgotten.
	7.2. $followed		7.2. $followed
	The $followed keyword indicates that a user is particularly		The $followed keyword indicates that a user is particularly
	interested in future messages in a specific thread. This enables		interested in future messages in a specific thread. This enables
	special handling to ensure these messages receive appropriate		special handling to ensure these messages receive appropriate
	attention.		attention.
	skipping to change at line 750 ¶		skipping to change at line 750 ¶
	IMAP/JMAP keyword name: $hasattachment		IMAP/JMAP keyword name: $hasattachment
	Purpose: Indicate to the client that a message has an attachment.		Purpose: Indicate to the client that a message has an attachment.
	Private or Shared on a server: SHARED		Private or Shared on a server: SHARED
	Is it an advisory keyword or may it cause an automatic action: This		Is it an advisory keyword or may it cause an automatic action: This
	keyword is advisory.		keyword is advisory.
	When/by whom the keyword is set/cleared: It is set by the server		When/by whom the keyword is set/cleared: It is set by the server
	during message delivery or by the client (if neither		during message delivery; otherwise, it is set by the client (if
	$hasattachment nor $hasnoattachment is currently set).		neither $hasattachment nor $hasnoattachment is currently set).
	Related keywords: $hasnoattachment		Related keywords: Mutually exclusive with $hasnoattachment
	Related IMAP capabilities: None		Related IMAP capabilities: None
	Security considerations: None		Security considerations: None
	Published specification: RFC 9979		Published specification: RFC 9979
	Intended usage: COMMON		Intended usage: COMMON
	Scope: BOTH		Scope: BOTH
	skipping to change at line 810 ¶		skipping to change at line 810 ¶
	Purpose: Indicate to the client that a message does not have an		Purpose: Indicate to the client that a message does not have an
	attachment.		attachment.
	Private or Shared on a server: SHARED		Private or Shared on a server: SHARED
	Is it an advisory keyword or may it cause an automatic action: This		Is it an advisory keyword or may it cause an automatic action: This
	keyword is advisory.		keyword is advisory.
	When/by whom the keyword is set/cleared: It is set by the server		When/by whom the keyword is set/cleared: It is set by the server
	during message delivery, or by the client (if neither		during message delivery; otherwise, it is set by the client (if
	$hasattachment nor $hasnoattachment is currently set).		neither $hasattachment nor $hasnoattachment is currently set).
	Related keywords: None		Related keywords: Mutually exclusive with $hasattachment
	Related IMAP capabilities: None		Related IMAP capabilities: None
	Security considerations: None		Security considerations: None
	Published specification: RFC 9979		Published specification: RFC 9979
	Intended usage: COMMON		Intended usage: COMMON
	Scope: BOTH		Scope: BOTH
	skipping to change at line 896 ¶		skipping to change at line 896 ¶
	9.1.9. $MailFlagBit0 Keyword Registration		9.1.9. $MailFlagBit0 Keyword Registration
	IMAP/JMAP keyword name: $MailFlagBit0		IMAP/JMAP keyword name: $MailFlagBit0
	Purpose: Bit 0 part of a 3-bit bitmask that defines the color of the		Purpose: Bit 0 part of a 3-bit bitmask that defines the color of the
	flag when the message has the system flag \Flagged set. See		flag when the message has the system flag \Flagged set. See
	Section 3 for details.		Section 3 for details.
	Private or Shared on a server: SHARED		Private or Shared on a server: SHARED
	Is it an advisory keyword or may it cause an automatic action: No		Is it an advisory keyword or may it cause an automatic action: This
			keyword is advisory.
	When/by whom the keyword is set/cleared: This keyword is set by a		When/by whom the keyword is set/cleared: This keyword is set by a
	client as the result of a user action to "flag" a message as		client as the result of a user action to "flag" a message as
	urgent / in need of special attention.		urgent / in need of special attention.
	Related keywords: $MailFlagBit1, $MailFlagBit2		Related keywords: $MailFlagBit1, $MailFlagBit2
	Related IMAP capabilities: None		Related IMAP capabilities: None
	Security considerations: None		Security considerations: None
	skipping to change at line 926 ¶		skipping to change at line 927 ¶
	9.1.10. $MailFlagBit1 Keyword Registration		9.1.10. $MailFlagBit1 Keyword Registration
	IMAP/JMAP keyword name: $MailFlagBit1		IMAP/JMAP keyword name: $MailFlagBit1
	Purpose: Bit 1 part of a 3-bit bitmask that defines the color of the		Purpose: Bit 1 part of a 3-bit bitmask that defines the color of the
	flag when the message has the system flag \Flagged set. See		flag when the message has the system flag \Flagged set. See
	Section 3 for details.		Section 3 for details.
	Private or Shared on a server: SHARED		Private or Shared on a server: SHARED
	Is it an advisory keyword or may it cause an automatic action: No		Is it an advisory keyword or may it cause an automatic action: This
			keyword is advisory.
	When/by whom the keyword is set/cleared: This keyword is set by a		When/by whom the keyword is set/cleared: This keyword is set by a
	client as the result of a user action to "flag" a message as		client as the result of a user action to "flag" a message as
	urgent / in need of special attention.		urgent / in need of special attention.
	Related keywords: $MailFlagBit0, $MailFlagBit2		Related keywords: $MailFlagBit0, $MailFlagBit2
	Related IMAP capabilities: None		Related IMAP capabilities: None
	Security considerations: None		Security considerations: None
	skipping to change at line 956 ¶		skipping to change at line 958 ¶
	9.1.11. $MailFlagBit2 Keyword Registration		9.1.11. $MailFlagBit2 Keyword Registration
	IMAP/JMAP keyword name: $MailFlagBit2		IMAP/JMAP keyword name: $MailFlagBit2
	Purpose: Bit 2 part of a 3-bit bitmask that defines the color of the		Purpose: Bit 2 part of a 3-bit bitmask that defines the color of the
	flag when the message has the system flag \Flagged set. See		flag when the message has the system flag \Flagged set. See
	Section 3 for details.		Section 3 for details.
	Private or Shared on a server: SHARED		Private or Shared on a server: SHARED
	Is it an advisory keyword or may it cause an automatic action: No		Is it an advisory keyword or may it cause an automatic action: This
			keyword is advisory.
	When/by whom the keyword is set/cleared: This keyword is set by a		When/by whom the keyword is set/cleared: This keyword is set by a
	client as the result of a user action to "flag" a message as		client as the result of a user action to "flag" a message as
	urgent / in need of special attention.		urgent / in need of special attention.
	Related keywords: $MailFlagBit0, $MailFlagBit1		Related keywords: $MailFlagBit0, $MailFlagBit1
	Related IMAP capabilities: None		Related IMAP capabilities: None
	Security considerations: None		Security considerations: None
	skipping to change at line 999 ¶		skipping to change at line 1002 ¶
	server on delivery.		server on delivery.
	Related keywords: None		Related keywords: None
	Related IMAP capabilities: None		Related IMAP capabilities: None
	Security considerations: None		Security considerations: None
	Published specification: RFC 9979		Published specification: RFC 9979
	Intended usage: LIMITED		Intended usage: LIMITED USE
	Scope: BOTH		Scope: BOTH
	Owner/Change controller: IESG		Owner/Change controller: IESG
	9.1.13. $memo Keyword Registration		9.1.13. $memo Keyword Registration
	IMAP/JMAP keyword name: $memo		IMAP/JMAP keyword name: $memo
	Purpose: Indicate to the client that a message is a note-to-self		Purpose: Indicate to the client that a message is a note-to-self
	skipping to change at line 1098 ¶		skipping to change at line 1101 ¶
	server. Clients can clear the keyword based on user interaction.		server. Clients can clear the keyword based on user interaction.
	Related keywords: None		Related keywords: None
	Related IMAP capabilities: None		Related IMAP capabilities: None
	Security considerations: None		Security considerations: None
	Published specification: RFC 9979		Published specification: RFC 9979
	Intended usage: LIMITED		Intended usage: LIMITED USE
	Scope: BOTH		Scope: BOTH
	Owner/Change controller: IESG		Owner/Change controller: IESG
	9.1.16. $notify Keyword Registration		9.1.16. $notify Keyword Registration
	IMAP/JMAP keyword name: $notify		IMAP/JMAP keyword name: $notify
	Purpose: Indicate to the client that a notification should be		Purpose: Indicate to the client that a notification should be
End of changes. 12 change blocks.
	20 lines changed or deleted		23 lines changed or added
This html diff was produced by rfcdiff 1.48.