[Dovecot] Managesieve with local accounts
Hello,
I've got a problem using the plugin managsieve in dovecot (1.0.10 on
gentoo linux). I use local unix accounts on a linux machine, one for
each user with a .maildir in there home directory. Here is a snippet
of the logging.
Feb 14 20:17:48 obelix dovecot: Dovecot v1.0.10 starting up
Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out
Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out
Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out
Feb 14 20:18:00 obelix dovecot: imap-login: Login: user=<michael>,
method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
Feb 14 20:18:00 obelix dovecot: IMAP(michael): Disconnected: Logged out
Feb 14 20:19:04 obelix dovecot: managesieve-login: Disconnected:
user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
I don't get the sieve script and can't also save a script. It looks
quite ugly "login: Disconnected" in the last line.
Here is my config file (without the comments):
protocols = imap managesieve listen = * disable_plaintext_auth = yes ssl_disable = no ssl_cert_file = /etc/ssl/dovecot/server.pem ssl_key_file = /etc/ssl/dovecot/server.key mail_location = maildir:~/.maildir mail_debug = no verbose_proctitle = yes first_valid_uid = 10 protocol imap { } protocol pop3 { } protocol managesieve { sieve=~/.dovecot.sieve sieve_storage=~/sieve listen = *:2000 } protocol lda { postmaster_address = postmaster@baecker.com mail_plugins = cmusieve } auth default { mechanisms = plain passdb pam { args = "*" } userdb passwd { args = blocking=yes } user = root socket listen { client { path = /var/spool/postfix/auth/dovecot mode = 0666 user = postfix group = postfix } master { path = /var/spool/postfix/auth/auth-master mode = 0666 user = postfix group = postfix } } } dict { } plugin { }
The client worked already with pysieved over xinetd (Horde Ingo and
squirrelmail with avelsieve worked). But this isn't realy a solution.
Can anybody help me? Do you need anything, I didn't wrote her?
Thanks in advance
Michael Baecker
I've got a problem using the plugin managsieve in dovecot (1.0.10 on gentoo linux). I use local unix accounts on a linux machine, one for each user with a .maildir in there home directory. Here is a snippet of the logging.
Feb 14 20:19:04 obelix dovecot: managesieve-login: Disconnected: user=<michael>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS
I don't get the sieve script and can't also save a script. It looks quite ugly "login: Disconnected" in the last line. You should first turn on auth_debug (http://wiki.dovecot.org/Debugging/Authentication) and mail_debug for
Michael Baecker wrote: the managesieve service to get more log messages. The 'Disconnected' reason occurs when the client abruptly terminates the connection, without issueing a LOGOUT command. This might be caused by a failed login, but something else might be the problem as well.
Here is my config file (without the comments):
auth default { mechanisms = plain passdb pam { args = "*" } I notice that you are using pam and that your args is set to '*'. This means that dovecot authenticates with pam using the servicename of the service involvend; e.g. imap or pop3. So, did you add a managesieve service to your pam configuration? My experience with pam is close to zero unfortunately, but you can read http://wiki.dovecot.org/PasswordDatabase/PAM for a few pointers.
If all this isn't the problem, try disabling TLS and sniff (e.g. using ngrep) the ManageSieve TCP session to see what is going on between client and server.
Regards,
Stephan Bosch
Stephan Bosch stephan@rename-it.nl schrieb:
auth default { mechanisms = plain passdb pam { args = "*" } I notice that you are using pam and that your args is set to '*'. This means that dovecot authenticates with pam using the servicename of the service involvend; e.g. imap or pop3. So, did you add a managesieve service to your pam configuration? My experience with pam is close to zero unfortunately, but you can read http://wiki.dovecot.org/PasswordDatabase/PAM for a few pointers.
That was the simple problem and solution. I added a pam file that was
linked to imap and all worked like a charm.
Thanks a lot!
Michael Baecker
participants (2)
-
Michael Baecker
-
Stephan Bosch