2 ## Settings for the Sieve interpreter
5 # Do not forget to enable the Sieve plugin in 15-lda.conf and 20-lmtp.conf
6 # by adding it to the respective mail_plugins= settings.
9 # The path to the user's main active script. If ManageSieve is used, this the
10 # location of the symbolic link controlled by ManageSieve.
11 sieve = ~/.dovecot.sieve
13 # The default Sieve script when the user has none. This is a path to a global
14 # sieve script file, which gets executed ONLY if user's private Sieve script
15 # doesn't exist. Be sure to pre-compile this script manually using the sievec
17 # --> See sieve_before fore executing scripts before the user's personal
19 #sieve_default = /var/lib/dovecot/sieve/default.sieve
21 # Directory for :personal include scripts for the include extension. This
22 # is also where the ManageSieve service stores the user's scripts.
25 # Directory for :global include scripts for the include extension.
28 # Path to a script file or a directory containing script files that need to be
29 # executed before the user's script. If the path points to a directory, all
30 # the Sieve scripts contained therein (with the proper .sieve extension) are
31 # executed. The order of execution within a directory is determined by the
32 # file names, using a normal 8bit per-character comparison. Multiple script
33 # file or directory paths can be specified by appending an increasing number.
36 #sieve_before3 = (etc...)
38 # Identical to sieve_before, only the specified scripts are executed after the
39 # user's script (only when keep is still in effect!). Multiple script file or
40 # directory paths can be specified by appending an increasing number.
43 #sieve_after2 = (etc...)
45 # Which Sieve language extensions are available to users. By default, all
46 # supported extensions are available, except for deprecated extensions or
47 # those that are still under development. Some system administrators may want
48 # to disable certain Sieve extensions or enable those that are not available
49 # by default. This setting can use '+' and '-' to specify differences relative
50 # to the default. For example `sieve_extensions = +imapflags' will enable the
51 # deprecated imapflags extension in addition to all extensions were already
53 #sieve_extensions = +notify +imapflags
55 # Which Sieve language extensions are ONLY available in global scripts. This
56 # can be used to restrict the use of certain Sieve extensions to administrator
57 # control, for instance when these extensions can cause security concerns.
58 # This setting has higher precedence than the `sieve_extensions' setting
59 # (above), meaning that the extensions enabled with this setting are never
60 # available to the user's personal script no matter what is specified for the
61 # `sieve_extensions' setting. The syntax of this setting is similar to the
62 # `sieve_extensions' setting, with the difference that extensions are
63 # enabled or disabled for exclusive use in global scripts. Currently, no
64 # extensions are marked as such by default.
65 #sieve_global_extensions =
67 # The Pigeonhole Sieve interpreter can have plugins of its own. Using this
68 # setting, the used plugins can be specified. Check the Dovecot wiki
69 # (wiki2.dovecot.org) or the pigeonhole website
70 # (http://pigeonhole.dovecot.org) for available plugins.
71 # The sieve_extprograms plugin is included in this release.
74 # The separator that is expected between the :user and :detail
75 # address parts introduced by the subaddress extension. This may
76 # also be a sequence of characters (e.g. '--'). The current
77 # implementation looks for the separator from the left of the
78 # localpart and uses the first one encountered. The :user part is
79 # left of the separator and the :detail part is right. This setting
80 # is also used by Dovecot's LMTP service.
81 #recipient_delimiter = +
83 # The maximum size of a Sieve script. The compiler will refuse to compile any
84 # script larger than this limit. If set to 0, no limit on the script size is
86 #sieve_max_script_size = 1M
88 # The maximum number of actions that can be performed during a single script
89 # execution. If set to 0, no limit on the total number of actions is enforced.
90 #sieve_max_actions = 32
92 # The maximum number of redirect actions that can be performed during a single
93 # script execution. If set to 0, no redirect actions are allowed.
94 #sieve_max_redirects = 4
96 # The maximum number of personal Sieve scripts a single user can have. If set
97 # to 0, no limit on the number of scripts is enforced.
98 # (Currently only relevant for ManageSieve)
99 #sieve_quota_max_scripts = 0
101 # The maximum amount of disk storage a single user's scripts may occupy. If
102 # set to 0, no limit on the used amount of disk storage is enforced.
103 # (Currently only relevant for ManageSieve)
104 #sieve_quota_max_storage = 0