Sieve notify extension

New in MS 7.0.5, the MTA supports RFC 5435 (Sieve Email Filtering: Extension for Notifications) and RFC 5436 (Sieve Notification Mechanism: mailto). As of MS 8.0, a private  system-level action is also provided. And finally, as of MS 8.0.2.3, the File Carbon Copy (Fcc) described in the Internet-Draft draft-ietf-extra-sieve-fcc-02.txt is also supported.

The notify extension
The capability identifier for the notify extension defined in RFC 5435 is " ". This support extends, rather than replaces, the MTA&#x27;s existing support (since MS 6.2) for a subset of the " " action defined in draft-martin-sieve-notify-01.txt.

The limitations on the implementation of draft-martin-sieve-notify-01.txt are:



 The message parameter is not optional. 

 The "$...$" substitutions defined in section 3.1 are not supported. (Sieve variables may be used to provide this functionality.) 

 The "denotify" action is not supported. 



Both forms of " " can be used simultaneously; e.g.: require &#x5b;"enotify","notify"&#x5d;; notify :message "subject-text" "mailto:a@b?body=body-text"; notify :method "email" :options "a@b" "subject-text" "body-text"; If both " " extensions are enabled, the action arguments are examined to determine which extension is being used.
 * 1) New, standard form -- the enotify capability
 * 1) Equivalent older form from the Martin draft -- the notify capability

New in 7.0.5, " " actions in user-level Sieves are  automatically cancelled when the overall Sieve verdict  is " ",  " ", " ", or " ". " " in a system-level Sieve was treated the same, but no longer: such " " actions will now be honored, making it possible to use " " for some limited administrative auditing functions.

Note that by default, the " " action (both types) is disabled; to enable use of it, the   MTA option must be set to a positive value. Also note that as of 7.0.5, the MTA tracks uses of " " and limits successive (repeated) such actions within some time period; configuration of this is controlled by various autoresponse periodicity MTA options.

Normally, specifying a syntactically invalid recipient address, or syntactically invalid " " address, in a " " action results in the Sieve script aborting with an error. New in Messaging Server 7.0.5, the  MTA option may be enabled to cause such syntactic errors to be silently ignored.

The notify_method_capability and valid_notify_method tests
The  extension also adds two new tests,   and. takes an argument consisting of a list of notification methods and returns true if they are supported and syntactically valid, or false otherwise. takes three arguments, a notification-uri, a notification-capability, and a list of keywords, and succeeds if a match occurs; this is intended to permit checking whether a desired form of notification can be performed as desired.

The  extension also adds a modifier   to the   action of the   extension. causes percent-encoding of any octet in the string that doesn&#x27;t belong to the "unreserved" set for URIs, as described in RFC 3986 (Uniform Resource Identifier (URI): Generic Syntax).

The nonotify action
New in 8.0, the MTA supports a private action for system-level Sieves " ", which suppresses all applications of either form of the " " action. (Technical note: " " affects those Sieves which are both: attached to the same recipient address, and evaluated later.)

The :mime nonpositional parameter
Both forms of the notify support support the nonpositional :mime parameter. If specified this parameter has the same semantics as with the vacation action: The causes the specified message body to be treated as a MIME entity as defined in RFC 2045 section 2.4, including both MIME headers and content.

The fcc extension
The  extension defines a new optional tagged argument "":fcc"  that can be used with the notify and vacation actions to allow a copy of the vacation or notification message to be filed into a target mailbox belonging to the sieve owner. The mailbox argument to :fcc is analogous has the same semantics as the mailbox argument to the fileinto action; in effect it is as if a copy of the message was sent to the sieve owner with a user sieve specifying a fileinto action.

Support for the  extension was added in MS 8.0.2.3.

See also:
 * max_notifys MTA Option
 * notify_ignore_errors MTA Option
 * notify_maximum_timeout MTA Option
 * notify_minimum_timeout MTA Option
 * notify_timeout_default MTA Option
 * Autoresponse periodicity MTA options
 * Sieve filter limit MTA options
 * Sieve filter interpretation MTA options
 * Sieve hierarchy
 * Sieve variables extension
 * Sieve supported extensions