Hello Alto, Thursday, November 24, 2011, 12:06:04 PM, you wrote:
AS> 1.) About 20 minutes after start of TheBat status messages begin to AS> appear "connection unexpectedly closed" (or similar.) This is AS> individual for each connection, meaning that of the 10 configured AS> connections, only 3 may still be up after half an hour while 7 have AS> been terminated this way. I've analyzed the logs on my side and found out that sometimes, very rarely, some connections are dropped this way when there is no communication for 2 minutes, and some connections are even dropped when three is no communication for 1 minute. This is very suspicious, since the timeout is exactly 60 or 120 seconds, not random. The Bat! internally doesn't have such a timeout. The server that I'm using is sending messages to the client each 2 minutes during the IDLE, so I don't have any experience of longer inactivity period. 02.11.2011 20:10:42 C: 00225 IDLE 02.11.2011 20:10:42 S: + Waiting for DONE 02.11.2011 20:11:42 S: * OK Timeout in 30 minutes 02.11.2011 20:12:42 C: Connection unexpectedly closed I suspect that there are routers in between that drop the connections. Are the connections closed in your case also after a fixed period of inactivity? If you also have your connections dropped after one minute, make The Bat! to send something before that minute expire. Could you please put on the option "When online, refresh counters every 55 seconds" in the "IMAP Fine-Tune Section" of the account properties? AS> Since the remaining 3 connections seem to be fixed to a certain folder, AS> other folders (including INBOX) never get any updates again, even when AS> selecting other messages. While this could be a server issue (possible AS> the server has a shorter IDLE-keep-the-line-open timeout than TheBat AS> expects), this time is not configurable (as much as I was able to AS> discover), so it actually becomes TheBat's problem. We can make it configurable if it is the case, and in the meanwhile you can use the option "refresh counters every N seconds" to investigate the matter. AS> At the very least the connection should be reestablished after breakup, AS> if it can't be refreshed while it is still active. The connections are automatically reestablished when needed. The Bat! uses connections to execute particular tasks, like get messages or refresh flags or counters, it is not supposed to use connections for IDLE watching inside particular folders, that's why there is no option to tell what folders should be IDLEd, we simply have a option to refresh counters in the entire account. Although it can be costly to rescan all the folders and not as efficient as IDLE in particular folders, but that's what we have currently in our design. -- Best regards, Maxim mailto:m...@ritlabs.com ________________________________________________________ Current beta is 5.0.26.12 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
