IMAP timeout and more

Question

Hi all, I have recently started getting countless "Your IMAP server closed the connection" error messages in Outlook 2010.  Increasing the timeout in settings didn't help.  Sometimes my email quits refreshing at all until I close Outlook and re-open it.  It used to work seamlessly. Also, my iPhone says it sometimes say the Comcast password is wrong (even though it isn't and it eventually downloads the emails)? From the error message:   resmail-po-136v.sys.comcast.net Zimbra IMAP4rev1 server closing connection; service busy
Protocol: IMAP
Server: imap.comcast.net
Port: 993
Error Code: 0x800CCCDD Have others experience these or found solutions?   Thanks!

Answer 1

Looks like Comcast banned my user name from the forum for my previous posts.  I am it sure why, but guess they do not like negative feedback.  Some mental giant called me at 8:30 PM last night and said my case had been escalated and that someone would be contacting me tomorrow.  They just wanted to let me know that they, "cared about my problem and would work on it, when a representative called me tomorrow, because now it is in the executive office."  I am not holding my breath; they always say the same thing and absolutely never call.   Here it is nearly 11 Am and still no call, some executive attention.  I love the calls from Comcast that tell me they care, they make me feel so much better when I can't get my email. As an IT professional, I find it pathetic that Comcast cannot implement the IMAP protocol error free on its mail servers.  It's done every day by so many.  It's easy to reach a simpleton, who knows how to check a script of trouble shooting settings, but beyond that it is impossible to reach anyone who can actually get things done.  The Peter Principle is functioning extremely well at Comcast.  Xfinity, what does that mean anyways?  X and infinity?  It think it is x_x is for how you feel after you get off the phone with Comcast and infinity means it's forever.  Here's another good one, they say I am supposed to use port 465 on smtp outbound with SSL, but it does not work.  It fails, so I changed it to 587 TLS and I can send mail.  The guy on the phone was flabbergasted, and said "that shouldn't work." 465 will not work at all!  It's the only way I can send and rec mail currently, but it's full of problems.  Funny thing is they have these setting plastered all over their website. Peter Principle. Comcast has had capacity issues on servers in the past, but never admits wrongdoing.  I caught them packet shaping VOIP services a few years back.  I had deductive proof using packet sniffers during calls.  They swore they didn't do that, but when senior managers in my area actually saw the evidence, they fessed up.  It's hard to argue with real solid evidence when it is presented in a scientific method.  I was so easy to prove, three minutes into calls and packet contention would surface, like a throttle governor on a go cart at an amusement park.   They did it to Netflix too.  It was so bad that Netflix caved and cut a deal.  http://www.washingtonpost.com/blogs/the-switch/wp/2014/02/23/comcasts-deal-with-netflix-makes-network-neutrality-obsolete/ Hey Comcast, have a nice day!  I care about you too! NOT