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.



"Your IMAP server closed the connection. This can occur if you leave the
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

In message "Kent Moore"
wrote:

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.

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"?

"Your IMAP server closed the connection. This can occur if you leave the
connection idle for too long."

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

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

"Jason Dunn" www.jasondunn.com wrote in message
...
"Your IMAP server closed the connection. This can occur if you leave the
connection idle for too long."

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

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...

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



"compdoc" wrote in message
...
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...

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

"Kent Moore" wrote in message
...
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



"compdoc" wrote in message
...
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...

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" wrote:

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

Thanks. I'll 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

"compdoc" wrote in message
...
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" wrote:

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