Movatterモバイル変換
[0]ホーム
element); if so, it SHOULD be encapsulated as the value of an XMPP SHIM (Stanza Headers and Internet Metadata) [SHIM] header named "Urgency", where the XML character of that header is "high" if the value of the ":importance" tag is "1", "medium" if the value of the ":importance" tag is "2", and "low" if the value of the ":importance" tag is "3".2.5. Notify Tag ":message" If the ":message" tag is included, that string MUST be transformed into the XML character data of an XMPP element (where the string is generated according to the guidelines specified in Section 3.6 of [NOTIFY]).2.6. Notify Tag ":options" The ":options" tag has no special meaning for this notification mechanism. Any handling of this tag is the responsibility of an implementation.2.7. XMPP Syntax The xmpp mechanism results in the sending of an XMPP message to notify a recipient about an email message. The general XMPP syntax is as follows: o The notification MUST be an XMPP stanza.Saint-Andre & Melnikov Standards Track [Page 4] RFC 5437 Sieve Notify Method: XMPP January 2009 o The value of the XMPP 'from' attribute SHOULD be the XMPP address of the notification service associated with the Sieve engine or the XMPP address of the entity to be notified. The value of the XMPP 'from' attribute MUST NOT be generated from the Sieve ":from" tag. o The value of the XMPP 'to' attribute MUST be the XMPP address specified in the XMPP URI contained in the "method" notify parameter. o The value of the XMPP 'type' attribute MUST be 'headline' or 'normal'. o The XMPP stanza MUST include a child element. If the ":message" tag is included in the Sieve script, that string MUST be used as the XML character data of the element. If not and if the XMPP URI contained in the "method" notify parameter specified a "body" key in the query component, that value SHOULD be used. Otherwise, the XML character data SHOULD be some configurable text indicating that the message is a Sieve notification. o The XMPP stanza MAY include a child element. If the XMPP URI contained in the "method" notify parameter specified a "subject" key in the query component, that value SHOULD be used as the XML character data of the element. Otherwise, the XML character data SHOULD be some configurable text indicating that the message is a Sieve notification. o The XMPP stanza SHOULD include a URI, for the recipient to use as a hint in locating the message, encapsulated as the XML character data of a child element of an element qualified by the 'jabber:x:oob' namespace, as specified in [OOB]. If included, the URI SHOULD be an Internet Message Access Protocol [IMAP] URL that specifies the location of the message, as defined in [IMAP-URL], but MAY be another URI type that can specify or hint at the location of an email message, such as a URI for an HTTP resource [HTTP] or a Post Office Protocol Version 3 (POP3) mailbox [POP-URL] at which the message can be accessed. It is not expected that an XMPP user agent shall directly handle such a URI, but instead that it shall invoke an appropriate helper application to handle the URI. o The XMPP stanza MAY include an XMPP SHIM (Stanza Headers and Internet Metadata) [SHIM] header named "Resent-From". If the Sieve script included a ":from" tag, the "Resent-From"Saint-Andre & Melnikov Standards Track [Page 5] RFC 5437 Sieve Notify Method: XMPP January 2009 value MUST be the value of the ":from" tag; otherwise, the "Resent-From" value SHOULD be the envelope recipient address of the original email message that triggered the notification.3. Examples In the following examples, the sender of the email has an address of, the entity to be notified has an email address of and an XMPP address of romeo@im.example.com (resulting in an XMPP URI of), and the notification service associated with the Sieve engine has an XMPP address of notify.example.com. Note: In the following examples, line breaks are included in XMPP URIs solely for the purpose of readability.3.1. Basic Action The following is a basic Sieve notify action with only a method. The XML character data of the XMPP and elements are therefore generated by the Sieve engine based on configuration. In addition, the Sieve engine includes a URI pointing to the message. Basic action (Sieve syntax) notify "xmpp:romeo@im.example.com" The resulting XMPP stanza might be as follows: Basic action (XMPP syntax)SIEVE <juliet@example.com> You got mail. imap://romeo@example.com/INBOX;UIDVALIDITY=385759043/;UID=18Saint-Andre & Melnikov Standards Track [Page 6] RFC 5437 Sieve Notify Method: XMPP January 20093.2. Action with "body" The following action contains a "body" key in the query component of the XMPP URI but no ":message" tag in the Sieve script. As a result, the XML character data of the XMPP element in the XMPP notification is taken from the XMPP URI. In addition, the Sieve engine includes a URI pointing to the message. Action with "body" (Sieve syntax) notify "xmpp:romeo@im.example.com?message ;body=Wherefore%20art%20thou%3F" The resulting XMPP stanza might be as follows. Action with "body" (XMPP syntax)SIEVE Wherefore art thou? imap://romeo@example.com/INBOX;UIDVALIDITY=385759044/;UID=193.3. Action with "body", ":importance", ":message", and "subject" The following action specifies an ":importance" tag and a ":message" tag in the Sieve script, as well as a "body" key and a "subject" key in the query component of the XMPP URI. As a result, the ":message" tag from the Sieve script overrides the "body" key from the XMPP URI when generating the XML character data of the XMPP element. In addition, the Sieve engine includes a URI pointing to the message. Action with "body", ":importance", ":message", and "subject" (Sieve syntax) notify :importance "1" :message "Contact Juliet immediately!" "xmpp:romeo@im.example.com?message ;body=You%27re%20in%20trouble ;subject=ALERT%21"Saint-Andre & Melnikov Standards Track [Page 7] RFC 5437 Sieve Notify Method: XMPP January 2009 The resulting XMPP stanza might be as follows. Action with "body", ":importance", ":message", and "subject" (XMPP syntax)ALERT! Contact Juliet immediately! imap://romeo@example.com/INBOX;UIDVALIDITY=385759045/;UID=203.4. Action with ":from", ":message", ":importance", "body", and "subject" The following action specifies a ":from" tag, an ":importance" tag, and a ":message" tag in the Sieve script, as well as a "body" key and a "subject" key in the query component of the XMPP URI. As a result, the ":message" tag from the Sieve script overrides the "body" key from the XMPP URI when generating the XML character data of the XMPP element. In addition, the Sieve engine includes a URI pointing to the message, as well as an XMPP SHIM (Stanza Headers and Internet Metadata) [SHIM] header named "Resent-From" (which encapsulates the value of the ":from" tag). Action with ":from", ":importance", ":message", "body", and "subject" (Sieve syntax) notify :from "romeo.my.romeo@example.com" :importance "1" :message "Contact Juliet immediately!" "xmpp:romeo@im.example.com?message ;body=You%27re%20in%20trouble ;subject=ALERT%21" The resulting XMPP stanza might be as follows.Saint-Andre & Melnikov Standards Track [Page 8] RFC 5437 Sieve Notify Method: XMPP January 2009 Action with ":from", ":importance", ":message", "body", and "subject" (XMPP syntax)ALERT! Contact Juliet immediately!
[8]ページ先頭