[Dovecot] problems and dovecot & manegesieve

[Jose Luis Faria]

Hello,

my server is working with dovecot-2.0.2+dovecot-2.0-pigeonhole-0.2.0.

but if activate managesieve, is not listening in 4190!

any help?


I setup this:
----------------------------------
##
## ManageSieve specific settings
##

# Service definitions

service managesieve-login {
  inet_listener sieve {
    port = 4190
  }

  #inet_listener sieve_deprecated {
  #  port = 2000
  #}


  # the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0
  # is faster. <doc/wiki/LoginProcess.txt>
  #service_count = 1

  # Number of processes to always keep waiting for more connections.
  #process_min_avail = 0

  # If you set service_count=0, you probably need to grow this.
  #vsz_limit = 64M
}
service managesieve {
  # Max. number of ManageSieve processes (connections)
  #process_count = 1024
}

# Service configuration

protocol sieve {

  # adjustment
  #managesieve_max_line_length = 65536


  # NOTE: The username is compared case-sensitively.
  #mail_max_userip_connections = 10


  # try to load IMAP plugins here.
  #mail_plugins =

  # MANAGESIEVE logout format string:
  #  %i - total number of bytes read from client
  #  %o - total number of bytes sent to client
  #managesieve_logout_format = bytes=%i/%o


  # the IMPLEMENTATION capability that the dovecot reports to clients.
  # For example: 'Cyrus timsieved v2.2.13'
  #managesieve_implementation_string = Dovecot Pigeonhole


  # on the user).
  #managesieve_sieve_capability =
  #managesieve_notify_capability =


  # upload or script verification.
  #managesieve_max_compile_errors = 5


  # Sieve execution limits.
}




--
   :)   cumprimentos
----------------------
José Luís Faria
Network Eng./Administrador de Sistemas
Departamento de Informática
Universidade do Minho
Braga, Portugal

# Number of connections to handle before starting a new process. Typically # Maximum ManageSieve command line length in bytes. ManageSieve usually does # not involve overly long command lines, so this setting will not normally need # Maximum number of ManageSieve connections allowed for a user from each IP address. # Space separated list of plugins to load (none known to be useful so far). Do NOT # To fool ManageSieve clients that are focused on CMU's timesieved you can specify # Explicitly specify the SIEVE and NOTIFY capability reported by the server before # login. If left unassigned these will be reported dynamically according to what # the Sieve interpreter supports by default (after login this may differ depending # The maximum number of compile errors that are returned to the client upon script # Refer to 90-sieve.conf for script quota configuration and configuration of

smime.p7s
Description: S/MIME Cryptographic Signature