Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.
 
 
 
 
 
 

232 строки
11 KiB

  1. ##
  2. ## Settings for the Sieve interpreter
  3. ##
  4. # Do not forget to enable the Sieve plugin in 15-lda.conf and 20-lmtp.conf
  5. # by adding it to the respective mail_plugins= settings.
  6. # The Sieve interpreter can retrieve Sieve scripts from several types of
  7. # locations. The default `file' location type is a local filesystem path
  8. # pointing to a Sieve script file or a directory containing multiple Sieve
  9. # script files. More complex setups can use other location types such as
  10. # `ldap' or `dict' to fetch Sieve scripts from remote databases.
  11. #
  12. # All settings that specify the location of one ore more Sieve scripts accept
  13. # the following syntax:
  14. #
  15. # location = [<type>:]path[;<option>[=<value>][;...]]
  16. #
  17. # If the type prefix is omitted, the script location type is 'file' and the
  18. # location is interpreted as a local filesystem path pointing to a Sieve script
  19. # file or directory. Refer to Pigeonhole wiki or INSTALL file for more
  20. # information.
  21. plugin {
  22. # The location of the user's main Sieve script or script storage. The LDA
  23. # Sieve plugin uses this to find the active script for Sieve filtering at
  24. # delivery. The "include" extension uses this location for retrieving
  25. # :personal" scripts. This is also where the ManageSieve service will store
  26. # the user's scripts, if supported.
  27. #
  28. # Currently only the 'file:' location type supports ManageSieve operation.
  29. # Other location types like 'dict:' and 'ldap:' can currently only
  30. # be used as a read-only script source ().
  31. #
  32. # For the 'file:' type: use the ';active=' parameter to specify where the
  33. # active script symlink is located.
  34. # For other types: use the ';name=' parameter to specify the name of the
  35. # default/active script.
  36. sieve = file:~/sieve;active=~/.dovecot.sieve
  37. # The default Sieve script when the user has none. This is the location of a
  38. # global sieve script file, which gets executed ONLY if user's personal Sieve
  39. # script doesn't exist. Be sure to pre-compile this script manually using the
  40. # sievec command line tool if the binary is not stored in a global location.
  41. # --> See sieve_before for executing scripts before the user's personal
  42. # script.
  43. #sieve_default = /var/lib/dovecot/sieve/default.sieve
  44. # The name by which the default Sieve script (as configured by the
  45. # sieve_default setting) is visible to the user through ManageSieve.
  46. #sieve_default_name =
  47. # Location for ":global" include scripts as used by the "include" extension.
  48. #sieve_global =
  49. # The location of a Sieve script that is run for any message that is about to
  50. # be discarded; i.e., it is not delivered anywhere by the normal Sieve
  51. # execution. This only happens when the "implicit keep" is canceled, by e.g.
  52. # the "discard" action, and no actions that deliver the message are executed.
  53. # This "discard script" can prevent discarding the message, by executing
  54. # alternative actions. If the discard script does nothing, the message is
  55. # still discarded as it would be when no discard script is configured.
  56. #sieve_discard =
  57. # Location Sieve of scripts that need to be executed before the user's
  58. # personal script. If a 'file' location path points to a directory, all the
  59. # Sieve scripts contained therein (with the proper `.sieve' extension) are
  60. # executed. The order of execution within that directory is determined by the
  61. # file names, using a normal 8bit per-character comparison.
  62. #
  63. # Multiple script locations can be specified by appending an increasing number
  64. # to the setting name. The Sieve scripts found from these locations are added
  65. # to the script execution sequence in the specified order. Reading the
  66. # numbered sieve_before settings stops at the first missing setting, so no
  67. # numbers may be skipped.
  68. #sieve_before = /var/lib/dovecot/sieve.d/
  69. #sieve_before2 = ldap:/etc/sieve-ldap.conf;name=ldap-domain
  70. #sieve_before3 = (etc...)
  71. # Identical to sieve_before, only the specified scripts are executed after the
  72. # user's script (only when keep is still in effect!). Multiple script
  73. # locations can be specified by appending an increasing number.
  74. #sieve_after =
  75. #sieve_after2 =
  76. #sieve_after2 = (etc...)
  77. sieve_after = /etc/dovecot/sieve-after
  78. # Which Sieve language extensions are available to users. By default, all
  79. # supported extensions are available, except for deprecated extensions or
  80. # those that are still under development. Some system administrators may want
  81. # to disable certain Sieve extensions or enable those that are not available
  82. # by default. This setting can use '+' and '-' to specify differences relative
  83. # to the default. For example `sieve_extensions = +imapflags' will enable the
  84. # deprecated imapflags extension in addition to all extensions were already
  85. # enabled by default.
  86. #sieve_extensions = +notify +imapflags
  87. # Which Sieve language extensions are ONLY available in global scripts. This
  88. # can be used to restrict the use of certain Sieve extensions to administrator
  89. # control, for instance when these extensions can cause security concerns.
  90. # This setting has higher precedence than the `sieve_extensions' setting
  91. # (above), meaning that the extensions enabled with this setting are never
  92. # available to the user's personal script no matter what is specified for the
  93. # `sieve_extensions' setting. The syntax of this setting is similar to the
  94. # `sieve_extensions' setting, with the difference that extensions are
  95. # enabled or disabled for exclusive use in global scripts. Currently, no
  96. # extensions are marked as such by default.
  97. #sieve_global_extensions =
  98. # The Pigeonhole Sieve interpreter can have plugins of its own. Using this
  99. # setting, the used plugins can be specified. Check the Dovecot wiki
  100. # (wiki2.dovecot.org) or the pigeonhole website
  101. # (http://pigeonhole.dovecot.org) for available plugins.
  102. # The sieve_extprograms plugin is included in this release.
  103. #sieve_plugins =
  104. sieve_plugins = sieve_imapsieve sieve_extprograms
  105. # The separator that is expected between the :user and :detail
  106. # address parts introduced by the subaddress extension. This may
  107. # also be a sequence of characters (e.g. '--'). The current
  108. # implementation looks for the separator from the left of the
  109. # localpart and uses the first one encountered. The :user part is
  110. # left of the separator and the :detail part is right. This setting
  111. # is also used by Dovecot's LMTP service.
  112. #recipient_delimiter = +
  113. # The maximum size of a Sieve script. The compiler will refuse to compile any
  114. # script larger than this limit. If set to 0, no limit on the script size is
  115. # enforced.
  116. #sieve_max_script_size = 1M
  117. # The maximum number of actions that can be performed during a single script
  118. # execution. If set to 0, no limit on the total number of actions is enforced.
  119. #sieve_max_actions = 32
  120. # The maximum number of redirect actions that can be performed during a single
  121. # script execution. If set to 0, no redirect actions are allowed.
  122. #sieve_max_redirects = 4
  123. # The maximum number of personal Sieve scripts a single user can have. If set
  124. # to 0, no limit on the number of scripts is enforced.
  125. # (Currently only relevant for ManageSieve)
  126. #sieve_quota_max_scripts = 0
  127. # The maximum amount of disk storage a single user's scripts may occupy. If
  128. # set to 0, no limit on the used amount of disk storage is enforced.
  129. # (Currently only relevant for ManageSieve)
  130. #sieve_quota_max_storage = 0
  131. # The primary e-mail address for the user. This is used as a default when no
  132. # other appropriate address is available for sending messages. If this setting
  133. # is not configured, either the postmaster or null "<>" address is used as a
  134. # sender, depending on the action involved. This setting is important when
  135. # there is no message envelope to extract addresses from, such as when the
  136. # script is executed in IMAP.
  137. #sieve_user_email =
  138. # The path to the file where the user log is written. If not configured, a
  139. # default location is used. If the main user's personal Sieve (as configured
  140. # with sieve=) is a file, the logfile is set to <filename>.log by default. If
  141. # it is not a file, the default user log file is ~/.dovecot.sieve.log.
  142. #sieve_user_log =
  143. # Specifies what envelope sender address is used for redirected messages.
  144. # The following values are supported for this setting:
  145. #
  146. # "sender" - The sender address is used (default).
  147. # "recipient" - The final recipient address is used.
  148. # "orig_recipient" - The original recipient is used.
  149. # "user_email" - The user's primary address is used. This is
  150. # configured with the "sieve_user_email" setting. If
  151. # that setting is unconfigured, "user_mail" is equal to
  152. # "recipient".
  153. # "postmaster" - The postmaster_address configured for the LDA.
  154. # "<user@domain>" - Redirected messages are always sent from user@domain.
  155. # The angle brackets are mandatory. The null "<>" address
  156. # is also supported.
  157. #
  158. # This setting is ignored when the envelope sender is "<>". In that case the
  159. # sender of the redirected message is also always "<>".
  160. #sieve_redirect_envelope_from = sender
  161. ## TRACE DEBUGGING
  162. # Trace debugging provides detailed insight in the operations performed by
  163. # the Sieve script. These settings apply to both the LDA Sieve plugin and the
  164. # IMAPSIEVE plugin.
  165. #
  166. # WARNING: On a busy server, this functionality can quickly fill up the trace
  167. # directory with a lot of trace files. Enable this only temporarily and as
  168. # selective as possible.
  169. # The directory where trace files are written. Trace debugging is disabled if
  170. # this setting is not configured or if the directory does not exist. If the
  171. # path is relative or it starts with "~/" it is interpreted relative to the
  172. # current user's home directory.
  173. #sieve_trace_dir =
  174. # The verbosity level of the trace messages. Trace debugging is disabled if
  175. # this setting is not configured. Possible values are:
  176. #
  177. # "actions" - Only print executed action commands, like keep,
  178. # fileinto, reject and redirect.
  179. # "commands" - Print any executed command, excluding test commands.
  180. # "tests" - Print all executed commands and performed tests.
  181. # "matching" - Print all executed commands, performed tests and the
  182. # values matched in those tests.
  183. #sieve_trace_level =
  184. # Enables highly verbose debugging messages that are usually only useful for
  185. # developers.
  186. #sieve_trace_debug = no
  187. # Enables showing byte code addresses in the trace output, rather than only
  188. # the source line numbers.
  189. #sieve_trace_addresses = no
  190. # From elsewhere to Junk folder
  191. imapsieve_mailbox1_name = INBOX.Junk
  192. imapsieve_mailbox1_causes = COPY
  193. imapsieve_mailbox1_before = file:/etc/dovecot/sieve/learn-spam.sieve
  194. # From Junk folder to elsewhere
  195. imapsieve_mailbox2_name = *
  196. imapsieve_mailbox2_from = INBOX.Junk
  197. imapsieve_mailbox2_causes = COPY
  198. imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve
  199. sieve_pipe_bin_dir = /etc/dovecot/sieve
  200. sieve_global_extensions = +vnd.dovecot.pipe
  201. }