Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
"No messages found" error with courier imap #2870
Reported by maharaja on 27 May 2010 14:25 UTC as Trac ticket #1486761
there is a timeout issue when accessing a imap mailbox on a courier server.
what i noticed is:
rc 0.3 did 1 call to
rc 0.4 does 2 calls:
another thing i noticed is that this error is more likely to occur when
is there any way to test this two requests in a serial fashion?
Comment by maharaja on 28 May 2010 09:53 UTC
my setting already is reasonably high and i encounter no issues with multiple computers, each running multiple thunderbird accounts.
mysql as a backend allows 1000 concurrent connections. there currently are around 100 in use, so this shouldn't be an issue either.
there is no information regarding any maxdeamon hit.
of course, roundcube does not use persistent connections as thunderbird.
Comment by @alecpl on 28 May 2010 14:01 UTC
What if you increase the new imap_timeout option? Now I see, one request tooks more than 10 seconds, so it times out. For me the issue doesn't looks like concurrent sessions limit, but SLOW concurrent sessions. How long is running list request when you click on INBOX?
Comment by maharaja on 28 May 2010 14:55 UTC
first of all, it seems to work when increasing the timeout. i have to test a little more though before i can say if the new option fixes this issue.
what i did:
refreshing the inbox takes 37.68 seconds but works. see rc-imap-timeout-2500s.png
Comment by maharaja on 28 May 2010 15:10 UTC
mhm - i did not test with a fresh export and therefore had a couple of leftovers from my patch, which would set imap_timeout to a default value of 10.
so it definitely seems to be a slow imap server.
but using the procedure as described above using rc 0.3.1 works fast.
Comment by @alecpl on 28 May 2010 17:00 UTC
Enable imap_debug and you'll see what's changed. The getunread action will be probably extended in the future, also if you have more folders it will be more performance expensive. So, I don't think we can improve something here. Changing order of these ajax calls is not a solution.