Windows 7 - "Your IMAP server closed the connection."

Asked By Kent Moore on 31-May-07 05:41 PM
Hi:



I am using Outlook 2007 on Windows XP SP2 Home and I am getting the
following pop up message fairly frequently.  It is annoying because when I
get the message it comes to the foreground and interrupts whatever work I am
doing.



connection idle for too long."



I don't have any other e-mail programs open.  I know you can receive this
message when other e-mail programs are open.  I talked to my ISP and they
said there is nothing they can do but that they have the same problem when
using Outlook 2007.  I never received this message with 2003 unless I had
another e-mail program open.  The only thing that is better with 2007 is
that the same message does not pile up like it did with 2003 where you could
get dozens of the same message and would have to close them all.



I have also changed "server timeouts" to 10 minutes and this does not help.
I wish Outlook would have an option to allow this message to be turned off.



Thanks for any suggestions.  Kent




DevilsPGD replied on 31-May-07 06:51 PM
You have identified the crux of the problem -- The IMAP protocol
specifically allows the server to drop the connection, and suggests that
clients handle it gracefully rather then whining to the user.

Outlook doesn't.

Microsoft was informed of this as far back as the 90s, and has decided
to opt for user-unfriendliness.

All that being said, if your IMAP server leaves connections for at least
30 minutes (the IMAP spec's suggested minimum idle time) then you
shouldn't see this issue much unless you have some networking gear that
kills idle connections (many cheapo SOHO NAT boxes do, unfortunately)

--
If quitters never win, and winners never quit,
what fool came up with, "Quit while you're ahead"?
Jason Dunn replied on 31-May-07 11:15 PM
I'm using Outlook 2007 and Vista, with six IMAP accounts on a dedicated
server I run, and I can leave Outlook open for days and never seen this
message. There's something that Outlook doesn't like about your IMAP server,
or your IMAP server is configured to kill connections somehow. I'd look to
the server and see if there's a way to change it...

Jason Dunn
www.digitalmediathoughts.com
Kent Moore replied on 01-Jun-07 01:10 AM
Thanks Jason.  Yes you are correct in that it has something to do with my
school's server.  I think it is an older type but they will not upgrade so I
am stuck with it.  I did ask them if there was anything they could do and so
far they said no but they are researching it and will let me know if they
find anything.  They just started testing Outlook 2007.  Kent
compdo replied on 10-Jun-07 10:14 AM
I was going crazy from all the IMAP server connection errors in 2007. But,
even though the connections were timing out, (or whatever) I noticed the mail
was still appearing in my IMAP folders.

I was about to switch back to Outlook 2003, when I got this idea. My IMAP
accounts are in a separate send/receive group than my pop3 accounts. Since
mail appears in the IMAP accounts even when the connection was lost, I
disabled "Schedule an automatic send/receive every X minutes" for that
send/receive group, and all the problems went away.

There's no need for Outlook to constantly retrieve mail from the IMAP
accounts since its a 'live' connection. The mail appears when it arrives with
no need for Outlook to do automatic send/receives.

Give it a try...
Kent Moore replied on 11-Jun-07 01:26 PM
Hi compdoc:



You may have hit on something big here for me and others.  I did have it set

to send/receive every minute because I like getting messages ASAP.  I turned

that off and so far so good.  I didn't realize messages would still come in

if it didn't automatically send/receive.  That part is working well and I am

getting messages.  Now I will wait to see if I still get any of the pop ups.

If this works consistently, this fix should be published because I know the

pop up is a major problem for many people.  Thanks for your help!  Kent
Kent Moore replied on 11-Jun-07 04:21 PM
With Compdoc's idea everything is working for me so far.  I just have to
remember to keep my IMAP folder "live" and open because if I am on another
folder, I won't receive my messages immediately.  Thank again, Kent
compdo replied on 13-Jun-07 12:05 PM
I generally click Send/Receive once when I first open Outlook, and that seems
to get it going. You can also just click on the IMAP inbox once or twice as
well.

After that, there doesnt seem to be a need to keep the account highlighted
or anything to keep it live.
Kent Moore replied on 13-Jun-07 02:45 PM
Thanks.  I will give that a try.  I have also been experimenting with longer
send/receive times such as 10 minutes and so far so good but time will tell.
Kent
Rich Gierman replied to Kent Moore on 03-Sep-10 08:08 PM
No.  No.  No.  Don't muck with the timeout.  Leave the polling for mail delivery alone.  It isn't any of those things.  I drove myself nuts dinking with those.  If you read AOL's page on IMAP and AOL mail, the solution is right there.



http://about.aol.com/faq/openmailaccess#OL0203



Go into the advanced properties for the account.  Go to  the Outgoing Server tab.



PLACE A CHECKMARK IN THE BOX THAT SAYS "My outgoing server (SMTP) requires authentication".  Then back out gracefully.  THAT INSTANTLY FIXES THE PROBLEM!  No restart, no close Outlook and re-open it.



In fact, after I did that, I was immediately able to move incoming e-mails from the inbox to any of my saved mail folders (which was where most of the problems were occurring).  However, it took forever for it to happen.



As soon as I went back into advanced properties and moved that stupid slider from 10 minutes back down to its lowest setting - 10 seconds - my response time for moving an email to a folder or even opening a new email dropped to almost instantly!



I was having the problem on a completely fresh install of XP SP3, so I figured it either had to be some unannounced change by AOL on their mail servers - and we all know that never happens, right? - or it had to be a configuration option.  In spite of the fact that it just started a couple of months ago and I hadn't changed anything in a year or two.



Anyway, problem REALLY solved!



Rich
Frank Cope replied to Rich Gierman on 08-Sep-10 06:47 PM
Rich,



I followed your instructions (and the AOL). Got XP/SP3 and still cannot move items from the inbox folder without getting the error.  The second error was "Can't move the item.  The server did not respond to this IMAP command before the connection was terminated.
DivaVocals replied to Frank Cope on 31-Dec-10 07:09 PM
That's because compdoc was ABSOLUTELY dead on!!! Turning off the automatic send receive settings for all of my IMAP accounts stopped this annoying little error IMMEDIATELY.. and his reasons why are SPOT on.. IMAP accounts by their nature are LIVE connections.. no need to keep pinging the daggone server..



I just followed his suggestions 30 minutes ago, and not only is my PC FINALLY (after a year of this nonsense) QUIET, it actually seems to be running better, and Outlook is not FREEZING all the daggone time (Outlook had a "shelf life" of 30 minutes on my PC before I had to often shut it down and restart it.. this was more annoying than the stupid error messages)



If you have multiple e-mail accounts enabled and have both POP3 and IMAP protocols, segregating the POP3 ones for the automatic send and receive settings while turning it off for the IMAP accounts will stop these annoying little messages..



Too bad AOL fails to include this information in their setup IMAP setup instructions.. (Which I have memorized as I have been using AOL --with either POP3 or IMAP protocols-- with Outlook and other mail clients LONG before AOL FINALLY shared with the public how to do this..)
Bill Fink replied to Kent Moore on 15-Feb-12 02:14 PM
Here is the issue: Outlook's error reporting that: "Your IMAP server closed the connection."



This occurs when an end-user has their Outlook client open and then their other devices (i.e. iOS phones, Android phones, etc) check their mail for the end-user at the same time.



I've been searching for a solution to this problem for quite some time and I'm getting exhausted just searching for a solution.



While everyone at my organization uses one version or another of Outlook there are many organizations that cannot afford an Exchange Server. (We'd like to but for now this is not an option in this economy.) Too, I'm a consultant and my clients who also do not have an exchange server complain about this issue.



Can this be fixed??? If it's been fixed or there is an Outlook work around, I'd like to know please?



If it's not fixed the only alternative for me is to recommend to my customers to NOT use Outlook where there is an IMAP server.



See what's causing this below. I've pasted the answer from the University Of Washington's IT department and why/what's causing this issue.



... Please help?! Thanks!





Issue (1):



Certain IMAP clients, including Outlook, have a tendency to open multiple

IMAP sessions simultaneously to the same mailbox unless it is carefully

configured (and used!) to avoid this.  The traditional UNIX mailbox format

is not ameniable to multiple read-write sessions being open

simultaneously, and each open of a mailbox in this format kills any

previous session that is open on that mailbox.



Issue (2):



Certain IMAP clients, including Outlook, have a tendency to close the

IMAP session without first issuing a proper LOGOUT command.  This causes a


misleads people into believing that there is some server-based problem.



Issue (3):



Outlook and Outlook Express use the IMAP IDLE extension to go into a mode

in which the client is alerted to new messages automatically without

having to transmit a periodic NOOP to cycle the protocol (effectively

polling the server).  This isn't surprising; Microsoft instigated the

development of that extension.



Unfortunately, Outlook and Outlook Express violate a part of the IDLE

specification which requires that the client end the IDLE within 29

minutes (and, if appropriate, issue a new IDLE), in order to renew the

session and avoid the IMAP inactivity autologout which occurs at 30

minutes of no activity from the client.



Since Outlook and Outlook Express do not do anything to renew the session,

it dies at the 30 minute autologout as per the specification.



As noted above, clients that do not use IDLE typically send a NOOP every

few minutes, which keeps the session active and avoids the autologout. So

why not just disable IDLE in the server?  Unfortunately, disabling server

support for the IDLE extension does not cause Outlook and Outlook Express

to revert to the NOOP behavior; they just don't send anything at all.



Microsoft acknowledged the problem in Outlook Express, but since Outlook

Express is effectively a dead product it is unlikely that it will ever be

fixed.  I don't know what the plans are to deal with this in Outlook.



To summarize:



The problems are entirely at the Outlook end.  The best way to get them

resolved is to file problem reports with Microsoft.