Re: [Dovecot] problems and dovecot & manegesieve
On Wed, 2010-09-29 at 13:53 +0100, Jose Luis Faria wrote: > > Add "sieve" to protocols setting. > > I did this add yesterday but it still not working. Show your full doveconf -n output then.
Re: [Dovecot] problems and dovecot & manegesieve
Hello, Em 28-09-2010 18:10, Timo Sirainen escreveu: On Tue, 2010-09-28 at 16:19 +0100, Jose Luis Faria wrote: 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! Add "sieve" to protocols setting. I did this add yesterday but it still not working. -- :) cumprimentos -- José Luís Faria Network Eng./Administrador de Sistemas Departamento de Informática Universidade do Minho Braga, Portugal smime.p7s Description: S/MIME Cryptographic Signature
Re: [Dovecot] problems and dovecot & manegesieve
On Tue, 2010-09-28 at 16:19 +0100, Jose Luis Faria wrote: > 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! Add "sieve" to protocols setting.
[Dovecot] problems and dovecot & manegesieve
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
#}
# Number of connections to handle before starting a new process.
Typically
# the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0
# is faster.
#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 {
# Maximum ManageSieve command line length in bytes. ManageSieve
usually does
# not involve overly long command lines, so this setting will not
normally need
# adjustment
#managesieve_max_line_length = 65536
# Maximum number of ManageSieve connections allowed for a user from
each IP address.
# NOTE: The username is compared case-sensitively.
#mail_max_userip_connections = 10
# Space separated list of plugins to load (none known to be useful so
far). Do NOT
# 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
# To fool ManageSieve clients that are focused on CMU's timesieved
you can specify
# the IMPLEMENTATION capability that the dovecot reports to clients.
# For example: 'Cyrus timsieved v2.2.13'
#managesieve_implementation_string = Dovecot Pigeonhole
# 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
# on the user).
#managesieve_sieve_capability =
#managesieve_notify_capability =
# The maximum number of compile errors that are returned to the
client upon script
# upload or script verification.
#managesieve_max_compile_errors = 5
# Refer to 90-sieve.conf for script quota configuration and
configuration of
# Sieve execution limits.
}
--
:) cumprimentos
--
José Luís Faria
Network Eng./Administrador de Sistemas
Departamento de Informática
Universidade do Minho
Braga, Portugal
smime.p7s
Description: S/MIME Cryptographic Signature
