A crash in Guam / #EImap does not result in a NO response, rather closes the connection on the client.
Authenticated. Security strength factor: 128 . LIST "" "*" Connection closed.
I suspect this may be caused by some sort of buffer overrun or similar, because a user with a smaller number of folders does succeed executing this command.
same reason T903 was re-opened, and not a buffer overrun or any other security-related issue -> there was a check using a variable which had already been bound with a value, so instead of binding the new value it tested for equality and that would fail.
A crash seems to result in the client connection getting closed still, rather than a NO response.
Today's crash is a different one, but the idea for this ticket remains the same -- it's not the individual error itself that needs resolving (different ticket), but the handling of any such and subsequent error should not cause the client connection to be closed.
10:19:40.380 [error] gen_fsm <0.140.0> in state wait_response terminated with reason: no function clause matching eimap:wait_response(process_command_queue, {state,"kolab.kolabsys.com",143,starttls,true,{sslsocket,{gen_tcp,#Port<0.1447>,tls_connection,undefined},...},...}) line 217
10:19:40.380 [error] CRASH REPORT Process <0.140.0> with 0 neighbours exited with reason: no function clause matching eimap:wait_response(process_command_queue, {state,"kolab.kolabsys.com",143,starttls,true,{sslsocket,{gen_tcp,#Port<0.1447>,tls_connection,undefined},...},...}) line 217 in gen_fsm:terminate/7 line 611