Sieve redirect action

The Sieve " " action performs a type of forwarding of a message. It cannot be combined with any of " ", " ", or " ", whose semantics all imply no retention of the message (including no forwarding). The   MTA option imposes a limit on the maximum number of " " actions that a user Sieve script is allowed to apply. As of 8.0, this limit applies only to user-level Sieves. Note that when the MTA performs a " " action, it generates the new message (the redirected, that is, forwarded message) via enqueue to (prior to 8.0) the  channel or (as of 8.0) the   channel.

A number of extensions can modify the effect of the standard Sieve " " action.

The " " extension  defined in RFC 3894 adds the " " parameter to permit " " to take effect without cancelling the default action of saving the message to the "INBOX".

Added in MS 6.3p1, the " " and " "    arguments are supported on the  Sieve " " action,  for controlling    whether Sieve " " actions cause addition of    Resent-&#x2a; header lines. The   MTA option may be used to control the MTA&#x27;s default behavior. See also the   MTA option, which controls whether Sieve filters see added headers on redirected messages.

New in MS 6.3p1, the Sieve   " " action supports the " " and     " " parameters, to control whether the  envelope FROM for the redirected message  is reset to match the Sieve owner, vs. the "original" envelope FROM address being retained for use on the redirected message. Note that by DSN rules, " " cannot be used when " " or " " are also specified on a " " action.

As of Messaging Server 7.0u2, the  extension (capability name " ") defined in RFC 6009 allows control over delivery status notification (DSN) parameters, adding two new parameters " " and " ". (The " " parameter support was actually added for MS 6.3p1, prior to standardization; standardization in RFC 6009 occurred in time for Messaging Server 7.0u2.)

The Sieve " " extension may be used in conjunction with a " " action, to redirect a message to (an externally stored) list of recipients. The  MTA option imposes a limit on how many such externally stored recipients will be used from the external list.

Note that when the Sieve environment extension is used, the " " item is available, and one of its possible values is " " -- which will be the case if and when the prior Sieve script that applied  performed an explicit handling action of " ".

See also:
 * Process and reprocess channels
 * max_redirects MTA Option
 * sieve_redirect_add_resent MTA Option
 * defer_header_addition MTA Option
 * max_redirect_addresses MTA Option
 * Sieve copy extension
 * Sieve external lists
 * Sieve environment extension
 * Sieve hierarchy
 * Sieve supported extensions