Hi, everyone. I found a couple of threads on this already but they both seemed to peter out, so I thought it best to start a new one.
I maintain the Roundcube packages for Mandriva. Ever since I updated the packages to 0.3.1 and updated my own server, as soon as I log in to Roundcube from any browser on any machine (it seems), I get logged out again. I can see my inbox for a few seconds, then get dumped back out to the login screen.
The web server roundcube is running on and the mail server it talks to are both Mandriva Linux 2009.0 boxen. Roundcube is set to talk to an imapproxy instance running on the mailserver, which in turn talks to the actual mail server application, which is courier-imap. There doesn't appear to be anything wrong with the courier configuration, I can log in to the server directly as usual, and I haven't changed it at all for months. imapproxy is imapproxy-1.2.6-5mdv2009.0 and courier-imap is courier-imap-4.4.0-1mdv2009.0.
After turning on all logging settings I can find, the logs I get are as follows. Roundcube's 'error' log shows nothing. Roundcube's 'imap' log shows this interesting stanza at the end:
[26-Jan-2010 11:51:55 -0800]: C: QUOT1 GETQUOTAROOT "INBOX"
[26-Jan-2010 11:51:55 -0800]: S: * QUOTAROOT "INBOX" "ROOT"
[26-Jan-2010 11:51:55 -0800]: S: * QUOTA "ROOT"
[26-Jan-2010 11:51:55 -0800]: S: QUOT1 OK GETQUOTAROOT Ok.
[26-Jan-2010 11:51:55 -0800]: C: I LOGOUT
The courier-imap 'errors' and 'warnings' logs show nothing relevant. The 'info' log just shows:
Jan 26 11:51:53 mailserver in.imapproxyd[4331]: LOGIN: '"adamw"' (192.168.1.4:44750) on existing sd [9]
Jan 26 11:51:53 mailserver in.imapproxyd[4331]: LOGOUT: '"adamw"' from server sd [9]
Jan 26 11:51:53 mailserver in.imapproxyd[4331]: LOGIN: '"adamw"' (192.168.1.4:44751) on existing sd [9]
Jan 26 11:51:55 mailserver in.imapproxyd[4331]: LOGOUT: '"adamw"' from server sd [9]
I think that's two attempts.
That's all the info I can find. It started behaving like this on upgrade from 0.2.2 to 0.3.1 (I skipped 0.3), without migrating database or config files. After I migrated the database and config files according to upstream changes, it continues to behave this way. I can't absolutely guarantee it wasn't happening right before the upgrade, but it definitely worked with 0.2.2 during the time I had it installed.
Any ideas, anyone? Thanks!
UPDATE: tried taking imapproxy out of the loop, changed nothing in behaviour (obviously the logs say something different now, but the behaviour's the same). There do actually appear to be *two* login / logouts for each single attempt, that log snippet wasn't two attempts as I thought.