20-managesieve.conf.erb 2.3 KB

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