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!
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.
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.
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.
The problems are entirely at the Outlook end. The best way to get them
resolved is to file problem reports with Microsoft.