192 |
- |
1 |
##
|
|
|
2 |
## ManageSieve specific settings
|
|
|
3 |
##
|
|
|
4 |
|
|
|
5 |
# Uncomment to enable managesieve protocol:
|
|
|
6 |
#protocols = $protocols sieve
|
|
|
7 |
|
|
|
8 |
# Service definitions
|
|
|
9 |
|
|
|
10 |
#service managesieve-login {
|
|
|
11 |
#inet_listener sieve {
|
|
|
12 |
# port = 4190
|
|
|
13 |
#}
|
|
|
14 |
|
|
|
15 |
#inet_listener sieve_deprecated {
|
|
|
16 |
# port = 2000
|
|
|
17 |
#}
|
|
|
18 |
|
|
|
19 |
# Number of connections to handle before starting a new process. Typically
|
|
|
20 |
# the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0
|
|
|
21 |
# is faster. <doc/wiki/LoginProcess.txt>
|
|
|
22 |
#service_count = 1
|
|
|
23 |
|
|
|
24 |
# Number of processes to always keep waiting for more connections.
|
|
|
25 |
#process_min_avail = 0
|
|
|
26 |
|
|
|
27 |
# If you set service_count=0, you probably need to grow this.
|
|
|
28 |
#vsz_limit = 64M
|
|
|
29 |
#}
|
|
|
30 |
|
|
|
31 |
#service managesieve {
|
|
|
32 |
# Max. number of ManageSieve processes (connections)
|
|
|
33 |
#process_limit = 1024
|
|
|
34 |
#}
|
|
|
35 |
|
|
|
36 |
# Service configuration
|
|
|
37 |
|
|
|
38 |
protocol sieve {
|
|
|
39 |
# Maximum ManageSieve command line length in bytes. ManageSieve usually does
|
|
|
40 |
# not involve overly long command lines, so this setting will not normally
|
|
|
41 |
# need adjustment
|
|
|
42 |
#managesieve_max_line_length = 65536
|
|
|
43 |
|
|
|
44 |
# Maximum number of ManageSieve connections allowed for a user from each IP
|
|
|
45 |
# address.
|
|
|
46 |
# NOTE: The username is compared case-sensitively.
|
|
|
47 |
#mail_max_userip_connections = 10
|
|
|
48 |
|
|
|
49 |
# Space separated list of plugins to load (none known to be useful so far).
|
|
|
50 |
# Do NOT try to load IMAP plugins here.
|
|
|
51 |
#mail_plugins =
|
|
|
52 |
|
|
|
53 |
# MANAGESIEVE logout format string:
|
|
|
54 |
# %i - total number of bytes read from client
|
|
|
55 |
# %o - total number of bytes sent to client
|
|
|
56 |
# %{put_bytes} - Number of bytes saved using PUTSCRIPT command
|
|
|
57 |
# %{put_count} - Number of scripts saved using PUTSCRIPT command
|
|
|
58 |
# %{get_bytes} - Number of bytes read using GETCRIPT command
|
|
|
59 |
# %{get_count} - Number of scripts read using GETSCRIPT command
|
|
|
60 |
# %{get_bytes} - Number of bytes processed using CHECKSCRIPT command
|
|
|
61 |
# %{get_count} - Number of scripts checked using CHECKSCRIPT command
|
|
|
62 |
# %{deleted_count} - Number of scripts deleted using DELETESCRIPT command
|
|
|
63 |
# %{renamed_count} - Number of scripts renamed using RENAMESCRIPT command
|
|
|
64 |
#managesieve_logout_format = bytes=%i/%o
|
|
|
65 |
|
|
|
66 |
# To fool ManageSieve clients that are focused on CMU's timesieved you can
|
|
|
67 |
# specify the IMPLEMENTATION capability that Dovecot reports to clients.
|
|
|
68 |
# For example: 'Cyrus timsieved v2.2.13'
|
|
|
69 |
#managesieve_implementation_string = Dovecot Pigeonhole
|
|
|
70 |
|
|
|
71 |
# Explicitly specify the SIEVE and NOTIFY capability reported by the server
|
|
|
72 |
# before login. If left unassigned these will be reported dynamically
|
|
|
73 |
# according to what the Sieve interpreter supports by default (after login
|
|
|
74 |
# this may differ depending on the user).
|
|
|
75 |
#managesieve_sieve_capability =
|
|
|
76 |
#managesieve_notify_capability =
|
|
|
77 |
|
|
|
78 |
# The maximum number of compile errors that are returned to the client upon
|
|
|
79 |
# script upload or script verification.
|
|
|
80 |
#managesieve_max_compile_errors = 5
|
|
|
81 |
|
|
|
82 |
# Refer to 90-sieve.conf for script quota configuration and configuration of
|
|
|
83 |
# Sieve execution limits.
|
|
|
84 |
}
|