Sieve Vacation Extension: "Seconds" Parameter
Extracted elements (11)
':seconds 0' is permitted and means all auto-replies are sent with no suppression of consecutive replies. This differs from the base vacation specification which forbids ':days 0'; the change is necessary to allow operation of a pure auto-responder that must acknowledge every incoming message.
If both ':seconds' and ':days' are omitted, a site-defined default interval is used, consistent with the base RFC 5230 vacation extension behavior.
Implementations that support the 'vacation-seconds' capability MUST also support the base 'vacation' capability defined in RFC 5230.
Sites MAY define a minimum effective value and/or a maximum effective value for ':seconds'. If a site imposes a maximum effective value, that value MUST be at least 86400 (one day).
The ':seconds' time value MUST be greater than or equal to 0 and less than 2**31. All valid values from 0 to 2**31 MUST be accepted without error.
Use of both ':days' and ':seconds' in the same vacation action MUST result in a Sieve processing error. Only one of the two parameters is allowed.
The capability string for this extension is 'vacation-seconds'. A script with 'vacation-seconds' in a 'require' list implicitly includes 'vacation' and may omit it from the list.
The effective value v(eff) is determined by clamping the specified value v(spec) to the site-defined range [v(min), v(max)]: values below v(min) are raised to v(min), values above v(max) are lowered to v(max), and values within range are used as-is.
The ':seconds' parameter specifies the minimum time interval in seconds between consecutive auto-replies to a given sender. It is used instead of ':days' when finer granularity is needed, and works analogously to the ':days' parameter defined in RFC 5230.
This document registers the 'vacation-seconds' capability in the IANA Sieve extensions registry. The capability adds the ':seconds' parameter to the Sieve Vacation extension.
Implementations SHOULD consider the number of auto-replies that might be generated by allowing small values of ':seconds' (including 0), and MAY impose additional limits on that number. The Security Considerations of RFC 3834 apply.