This is a bit of a weird problem. I have 2 primary email accounts, they work fine. I also have 4 supplementary email accounts all from the same free email service. I decided to get 4 to separate all the mail I get from gaming-related sites, auto-notifiers on BB, and a special one for mailing lists, plus the original one I got when I was checking the service out. The thing about the free webmail service is that it supports IMAP4 and POP as well, so I don't have to mess with webmail ads and popups and logins. Anyway, it was happily chirping along (the first account I opened with them that is) for many months. However when I got another three, I noticed that if it tried to check all of them at once, one of them would always hang in the connecting to..... bit. It was usually the same account. Thinking that account was corrupted, I would disable auto checking on startup for that one, and KILL the bat process (ever noticed that if mail checking hangs or takes forever to timeout you can't quit the bat? I hate that). Upon restarting the bat, since it wouldn't check THAT account right away, it'd do all the others, and sure enough ONE of the others would time out. So I tried to set it up so that the original timing-out one would not check upon startup and would check at an interval different from the others, etc. Seemed to help, but every so often (a few times a day) one of those accounts hangs, sometimes the CC says it's been trying for over 5 hrs. In that case if I KILL the bat from task manager and restart it, it seems to work fine. Now this is probably a problem with the mail service not liking simultaneous connections from the same IP maybe... or some sort of limit on service like that. But I think the Bat should deal with it gracefully. If it would time out the connection then when it retried it would get through fine (as witnessed by my KILL-RESTART trick). Note CC already does this with my other two primary accounts if they ever become unreachable, but for some reason not with this. The problem is probably that in their case, when the bat tries to connect and can't because the server is down, it knows how to deal with that, but when the server is UP (in the case of the multiple free accounts) and simply not responding, the bat just sits there forever, waiting. Is that a correct guess? Any solutions? I suppose I could set them all not to check upon startup, and have them each check with a different interval, to minimize those polling hangs, but I don't know.... (replies would be appreciated cc'ed to me, if possible... I have trouble reading the TB list in digest form) -- Kiyan Azarbar M.A. Program in Linguistics University of Ottawa -- ______________________________________________________ Archives : <http://tbudl.thebat.dutaint.com> Moderators : <mailto:[EMAIL PROTECTED]> TBTech List: <mailto:[EMAIL PROTECTED]> Unsubscribe: <mailto:[EMAIL PROTECTED]> You are subscribed as : archive@jab.org