[Dovecot] Managesieve: Remote login fails

Brainkiller - Tom brainkiller at gmail.com
Sun Nov 9 22:17:25 EET 2008

Stephan Bosch schreef:
> Brainkiller 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 
> 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



More information about the dovecot mailing list