Currently I'm following the thread "RoundCube session aborting" very attentively for one reason: It's the main show stopper why we can't finally kick Squirrel from our server yet.
I'm using RC intensively (I do not even have a local mail client installed), and I had to face lots of aborted seesions and lost server connections during "normal" usage of RC, in the worst case even in the middle of composing a message (losing most of the already written text, as the "Automatically save draft every x minutes" function does sometimes also not work too reliable - in the beginning it's working, but after a while - I'm sometimes writing longer messages which may take an hour or more - it often seems just to quit it's job).
I can't describe every single scenario here, as they are simply too many and hard to replicate. It happens just out of the blue, and you can't predict when.
But: My impression in the meantime is that this might be an issue between RC and the browser (in my case IE8). And no hints such as "use FF" or the like, please, this wouldn't solve the problem.
One interesting scenario that I had (and that's why I believe that it may be an RC<->Browser issue):
After sending a message (from a new window, compose_newwindow 3.00 plugin installed, option activated), RC did not react at all anymore to any click or key after I tried to change from the INBOX to the Sent folder. After a while the error message "Request timed out!" was thrown. From this point on, RC was completely unusable.
I'm skipping some details now:
Even worse, I couldn't load the RC login page again. Entering the appropriate URL, IE8 did not even attempt to contact the server (no progress bar in the status bar seen at all), displayed a blank page, and said "Finished" or "Ready" in the lower left corner of the status bar (not sure how the term for the German term "Fertig" in an English version of IE is).
Even more worse: I couldn't even load ANY web page of the domain in question anymore. So if your webmail URL is www.do.main/webmail/, and your home page is accessible under www.do.main/, even the latter one could not be loaded.
BUT: Then, for the first time in my life and just for testing purposes, I used the "InPrivate" mode of IE8. What can I tell ... it worked instantly, I could load the RC login page and all other web pages of the same domain, could login into RC and work with it (while the still open parallel IE window in standard mode was still not attempting to contact the server).
Huh...?
Any comments and input welcome.
TIA, Michael
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany