[Dovecot] Managesieve: Remote login fails
Hello,
I've been trying to get managesieve to work for our LAN, but when I try to login from a remote host i always get the following line in the log file: dovecot: child 26014 (login) killed with signal 11
When i enable debuging, it just gives me that line, nothing more. I can only login from the localhost through telnet but not from a remote host. My conf: # 1.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26.5.2008.10.03 i686 Debian lenny/sid ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps managesieve listen(default): * listen(imap): * listen(managesieve): *:12000 ssl_listen(default): * ssl_listen(imap): * ssl_listen(managesieve): ssl_cert_file: /etc/dovecot/mail.lan-cert.pem ssl_key_file: /etc/dovecot/mail.lan-key.pem ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_process_size: 80 login_processes_count: 6 login_max_processes_count: 256 login_max_connections: 1024 mail_access_groups: mail mail_location: maildir:/home/mail/%u mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota trash imap_quota fts fts_squat mail_plugins(imap): quota trash imap_quota fts fts_squat mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): tb-extra-mailbox-sep imap_client_workarounds(imap): tb-extra-mailbox-sep imap_client_workarounds(managesieve): dict_db_config: /etc/dovecot/dovecot-db.conf managesieve_implementation_string(default): dovecot managesieve_implementation_string(imap): dovecot managesieve_implementation_string(managesieve): Cyrus timsieved v2.2.13 sieve_storage(default): sieve_storage(imap): sieve_storage(managesieve): /home/mail/sieve/%u/scripts sieve(default): sieve(imap): sieve(managesieve): /home/mail/sieve/%u/dovecot.sieve namespace: type: private separator: / inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login cache_negative_ttl: 60 passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 438 user: dovecot group: mail plugin: fts: squat sieve: ~/.dovecot.sieve quota: maildir quota_rule: *:storage=190M quota_rule2: Trash:storage=50M acl: vfile:/etc/dovecot/dovecot-acls trash: /etc/dovecot/dovecot-trash.conf
Hello,
I've been trying to get managesieve to work for our LAN, but when I try to login from a remote host i always get the following line in the log file: dovecot: child 26014 (login) killed with signal 11
When i enable debuging, it just gives me that line, nothing more. I can only login from the localhost through telnet but not from a remote host. This is a segmentation fault (crash) and therefore definitely a bug in
Brainkiller schreef: the ManageSieve service. But without more information I cannot fix find and fix this bug. You should try to obtain a core dump or a gdb trace as explained at http://dovecot.org/bugreport.html . Debugging the login daemons can be a little more tricky. I usually attach gdb to the managesieve-login process that is handling my connection (using the gdb attach command). Be sure to compile dovecot with debugging symbols enabled (default Debian packages are stripped).
It is also interesting to know when exactly during the login process it crashes. If you login manually from a remote host (as explained in section 6 of http://wiki.dovecot.org/ManageSieve) you will be able to check where it crashes. If you do not use TLS, you can also sniff the traffic between client and server using ngrep to see where the login process dies.
Regards,
-- Stephan Bosch stephan@rename-it.nl
Stephan Bosch schreef:
Hello,
I've been trying to get managesieve to work for our LAN, but when I try to login from a remote host i always get the following line in the log file: dovecot: child 26014 (login) killed with signal 11
When i enable debuging, it just gives me that line, nothing more. I can only login from the localhost through telnet but not from a remote host. This is a segmentation fault (crash) and therefore definitely a bug in
Brainkiller schreef: the ManageSieve service. But without more information I cannot fix find and fix this bug. You should try to obtain a core dump or a gdb trace as explained at http://dovecot.org/bugreport.html . Debugging the login daemons can be a little more tricky. I usually attach gdb to the managesieve-login process that is handling my connection (using the gdb attach command). Be sure to compile dovecot with debugging symbols enabled (default Debian packages are stripped).
It is also interesting to know when exactly during the login process it crashes. If you login manually from a remote host (as explained in section 6 of http://wiki.dovecot.org/ManageSieve) you will be able to check where it crashes. If you do not use TLS, you can also sniff the traffic between client and server using ngrep to see where the login process dies.
Regards,
The segmentationfault happens right after sending the authentication action. As soon as I send any authentication it terminates. I'll try to go through the whole bugreport as soon as possible but maybe this can help you get started. Sniffing the network also doesn't bring up any other relavent information. It doesn't recieve any other packages after sending the authentication. I use LDAP for authenticating my clients, maybe thats the problem
Regards,
Tom
participants (3)
-
Brainkiller
-
Brainkiller - Tom
-
Stephan Bosch