Search K
Appearance
Appearance
The editheader extension (RFC 5293) enables Sieve scripts to delete and add message header fields, thereby allowing interaction with other components that consume or produce header fields.
The editheader extension is not available by default and needs to be enabled explicitly by adding it to sieve_extensions
.
WARNING
Invalid values for these settings will make the Sieve interpreter log a warning and revert to the default values.
sieve_editheader_forbid_add
Default | [None] |
---|---|
Value | string |
See Also |
A space-separated list of headers that cannot be added to the message header.
Addition of the Subject:
header cannot be prohibited, as required by
the RFC specification. Therefore, adding this header to this setting has no
effect.
sieve_editheader_forbid_delete
Default | [None] |
---|---|
Value | string |
See Also |
A space-separated list of headers that cannot be deleted from the message header.
Deleting the Received:
and Auto-Submitted:
fields is always
forbidden, while removing the Subject:
header cannot be prohibited, as
required by the RFC specification. Therefore, adding one of these headers
to this setting has no effect.
sieve_editheader_max_header_size
Default | 2048 |
---|---|
Value | unsigned integer |
See Also |
The maximum size in bytes of a header field value passed to the addheader command.
The minimum value for this setting is 1024
bytes.
sieve_editheader_protected
Default | [None] |
---|---|
Value | string |
See Also |
A space-separated list of headers that cannot be added to or deleted from the message header.
This setting is provided for backwards compatibility.
It is a combination of the sieve_editheader_forbid_add
and
sieve_editheader_forbid_delete
settings. The same limitations
apply.
plugin {
# Use editheader
sieve_extensions = +editheader
# Header fields must not exceed one kilobyte
sieve_editheader_max_header_size = 1k
# Protected special headers
sieve_editheader_forbid_add = X-Verified
sieve_editheader_forbid_delete = X-Verified X-Seen
}