One of my user's mailboxin my exchange 2007 server is giving me the following error massage when I am trying to configure his mail account on his Microsoft outlook or MS Outlook Express mail client. Error massage is: "Your IMAP server has closed the connection. This may occur if you have left the connection for too long". I have more then 500 user mailboxes and all are working fine only one mailbox is giving this error massage. Actually,this user has two mailboxeson two different exchange servers one with my company and another with his client company and he want to use my exchange server's mailbox as a IMAPaccount and his client company's account as an excahnge account (MAPI).I am able to configure my other mailboxes using IMAP on both the mail clients i.e. MS outlook and outlook express but onlythis mailbox is giving me the error. I am able to access this mailbox on OWA and able to configure this as an exchange server account (mapi a/c) but not able to configure this as an IMAP account with an existing exchange account. Currently, my user is using OWA to receive and send mails through this account. --Vinod

VS Indore wrote: I am able to access this mailbox on OWA and able to configure this as an exchange server account (mapi a/c) but not able to configure this as an IMAP account with an existing exchange account. Currently, my user is using OWA to receive and send mails through this account. --Vinod You are saying you are not able to add a 2nd account to MS Outlook, when there is already an Exchange account in the same profile? This should not be. I do this all the time. What error are you getting in Outlook? But about the other issue, thats strange. I wonder if there is a firewall doing something between this user's IMAP server and his workstation. Are there any errors in the Application log on the server or his workstation? Also, perhaps a dumb question, but how long is his IMAP session? Does thisuser ever logoff the computer? What version of Outlook Express does this person have?

Iam getting the error massage "Your IMAP server has closed the connection. This may occur if you have left the connection for too long" after configuring an IMAP account. User has already shutdown his workstation twice today. There is noting in application log for this. Outlook express version is 6.0

You are getting that error in both Outlook and Express and full Outlook? What is the issue with the full version of Outlook?

In outlook express the complete error massage which i am getting is: Your 'Inbox' folder was not polled for its unread count. Your IMAP server has closed the connection. This may occur if you have left the connection idle for too long. Account: '192.168.x.x', Server: '192.168.x.x', Protocol: IMAP, Server Response: 'Connection is closed. 15', Port: 143, Secure(SSL): No, Error Number: 0x800CCCDD --Vinod

Yes, i am getting errors on both MS Outlook and MS Outlook express.

http://portal.itauth.com/2007/11/16/addressing-outlook-express-imap-timeouts-and-disconnects Maybe adjust the timeout in the Exchange configuration: http://www.msexchange.org/articles_tutorials/exchange-server-2007/mobility-client-access/using-pop3-imap4-access-exchange-2007-part2.html o http://www.msexchange.org/img/upl/image0111184593884210.JPG o http://www.eggheadcafe.com/software/aspnet/29925397/imap-server-closed-the-co.aspx Do you have antivirus software perhaps interfering? On the server and/or workstation?

Ultimately, I have resolved the issue. Let me explain it step-by-step: 1.Installed the thunderbird mail client and configure the user mailbox on it. 2. It has given me the error: "The current command did not succeed. The mail server responded: Duplicate folders "Junk E-Mail" were detected in the mailbox. Therefore the user's connection was disconnected." 3. Checked the server log and found error: Duplicate folders "Junk E-mail" were detected in the mailbox for user: xyz. Therefore the user's connection was disconnected. User Action: To resolve this problem, the user should manually delete the duplicate folders by logging on to the mailbox using Outlook Web Access or a MAPI client such as Outlook. 4. Login onto the user's mailbox using OWA and deleted the "Junk E-Mail" Folder. 5. Problem resolved. --Vinod Sharma

Great question for you. I am using Thunderbird 2.0.0.19 to access my mailbox in a freshly converted Exchange 2007 server. Since the conversion I have been experiencing the same error but the duplicate folder is "Sent Items." I don't believe that I can delete this folder using OWA. Any idea what I should do?Thanks,EdEDIT: I had previously been unable to delete my "Sent Items" folder and had assumed that it was because "Sent Items" is a standard folder in Outlook. This was not the case. Upon logging in to my web based mail using Internet Explorer rather than Firefox I was able to delete the offending folder.

Awesome fix! I beat my head against the wall for days. Very good work!!!!--Ben

I am unable to DELETE the "Junk E-Mail Folder". It is locked for deletion. What should I do? PS. This is in regards to getting the message "Your IMPA server closed the connection"

It's incredible. I didn't believe it would be the problem. As soon I deleted the junk mail folder, the inbox was populated.

Hi How do you delete the junk mail ? I can't to do this Nadim

I ran into this problem recently and was able to resolve it. In case someone needs help in the future.... This message appears when Outlook cannot retrieve an e-mail from AOL's server within a specified period. You might also see an error, as I did- Your IMAP server wants to alert you to the following: (NUMBER) That mail is not currently available. The latter of the two errors is the cause for both. Outlook is finding a corrupt e-mail on AOL's server, cannot accept it and then times out. The hard part is finding the e-mail, possibly amongst thousands like my client had. Here's the best way I could think of to track down the culprit: Get Outlook on another PC with a clean, empty profile set up for the AOL account in question. As mail is retrieved for the first time, pay close attention to the dates. Because it is IMAP and not POP3 you don't need to worry about removing mail from AOL's server that the Outlook we're trying to fix is going to miss. In my case there were 3,000 items in this person's Inbox. After about half way through the retrieval process Outlook produced the error. You have to pay attention during the first send/receive in the clean Outlook profile because you'll then know the date of the corrupt e-mail (at the time the error pops up, look at the date of the incoming messages!). When you know the approximate date you can close Outlook. You need to know this date because you now have to login to the AOL account at http://webmail.aol.com, go to that date and delete the e-mail(s). Since the error popped up when retrieving e-mail that was nearly two years old and no longer important, I deleted a week's worth of messages from the AOL Webmail Inbox, deleted them from the Webmail Deleted Items folder, and the problem was solved. Opened Outlook, no more errors. I hope this information can help someone down the road!