Implemented in guam 91f1f2e5c7b2fb2d5c32ac463f37cac3b1ff078d

The keepalive patch is available sine 0.9.7.

Unfortunately missed this for 0.9.6, so I'll pick it up in the next release.

This has been resolved in packaging as far as I know.

Available since 0.9.5.

Now available in 0.9.6

I will look into integrating the patches.

This ticket is both old, as well as appears to be out-dated, in the sense that further updates to guam have been made available that also, supposedly, work, and was originally reported by an employee for another one of our then-employees to address.

The application can't address having run out of file descriptors.

Up?

This issue appears to be fixed on the client side, so I'm closing it.
On my test system, Kontact 5.7.3 identifies as "Kontact Kolab Resource 5/KOLAB".

Thanks for the detailed report. I'm working on getting this fixed.

First I tried to branch guam like it's common on github (pull requests, you know...). I'm not allowed to do so so I opened a ticket^H^H... task. But it seems it's not possible to add files here either. So here it is:

I also miss this feature as this would enable log based intrusion detection/prevention on IMAP accounts. Cyrus logs are only logging 127.0.0.1 as client IP because of Guam proxying, and Guam is not logging authentication events with IP.

Hello,
i reported the problem by the beginning of 2017 using the mailing list.
Since it hasn't been resolved, i disabled guam by changing the cyrus config.
This was with version 0.9.2-1.
Now, today i gave it a try and installed version 0.9.2-3. (Running on debian jessie).
Thunderbird can get the mails in the inbox, but when it starts to index the folders, thunderbird hangs.
On the server i strace the guam process and see, that there are unjoined threads and they never join.
Perhaps a hint, since erlang is based on threads.
As for now, i disabled guam again.

I have pushed a commit to the feature/autodetect_ipv6 branch which turns on keepalive for the socket; there is a corresponding fix on the eimap (imap server connection code) side as well, though I'm not sure that is needed. Hopefully that will resolve the issue as it will try to keep the socket up as long as the other side is still there according to the OS settings for these timeouts. by default on Linux it is 2 hours, which should be plenty.

Hi.
We have the same problem. Is there a workaround available?

see /usr/lib64/erlang/lib/guam-0.9.0/erl_crash.dump

So same issue, with slightly different results: multiple commands sent together, which is allowed by the IMAP spec indeed, and then the client ends up waiting for responses that do not come as expected. Thanks for the report.

I've encountered another bug with guam. This time It's "eM Client" for Windows. I've activated the client debug log (in eM Client) and after sending a XLIST and SELECT command in TLS/SSL mode (it looks like the client sends 2 commands at once) the connections gets into some kind of stale mode. It's no longer working. Hard to tell without decrypting network traffic.