Rebop2015, I figured you're chances of updating Outlook 2003 would be slim to none, just wanted to point out something you may not have been aware of. Your situation is dicey given that only 1 of 7 of your accts don't work. I would say you're right that it's not likely an Outlook or IE update issue, sounds more like an acct config issue. But I'm sure you've checked the acct and matched its config to your working accts, which kind of sets your issue apart from most. Maybe the acct's config data was corrupted, might be worth temporarily disabling the acct and creating a new acct using the same config info, if you can do that in Outlook.
Peggy, all I can suggest is to see if you're using a secure connection (TLS/SSL). When I switched from port 110 to 995 that option was disabled by default, I had to tic a checkbox to enable it.
Good luck to both of you.
... View more
The port number and incoming mail server name are not the only changes comcast made.
In an earlier post, I wrote about the sudden changes to my mail server on Nov 19th. I also called a comcast tech a jerk for telling me my email client was to blame because, as he 'emphatically' said "NO CHANGES WERE MADE TO THE MAIL SERVER".
Well, it turned out he is still a jerk for lying to me about the server, but was right about the client. Changes were made to the server, but not the blocking of port 110 that comcast announced would be made in Nov. That didn't occur until Dec, something else happened in Nov.
So what could make my Forte Agent email client suddenly stop working on Nov 19, 2018 when it worked perfectly since 2007, and also worked perfectly on port 995 since August 2018?
The only possible answer is.... the Internet Engineering Task Force (IETF) made changes to the POP3 protocol in Jan 2018 and on Nov 19th comcast eventually updated their server to comply with the new standard, before blocking port 110 in Dec. Why else would so many people have had so many issues with port 995 starting on Nov 19 while port 110 was still working? Simply put, comcast decided to update their server software in Nov and waited for feedback before blocking port 110 in Dec. So IMO it wasn't just the port number and incoming mail server name they changed, see the below link for details.....
The POP3 protocol doesn't change very often. The last time it changed was in 2011 and before that 2007, and before that 1999. But not all changes will render a client unusable, as was the case for me.
I tested using the latest free version of the Thunderbird client and it worked. I have since paid to upgrade my Forte Agent v4.2 client (circa 2007) to v8.0 and now have no issues retrieving mail. Although you appear to have different issues than I, it's possible your Outlook 2003 client fell out of compliance with current standards, as did the older version of my client. Don't know that for sure, but it is 4 years older than my client was:-)
... View more
Thanks for you suggestion, I don't use a VPN. No bottlenecks on this side. Apart from the mail server I'm getting an avg of 65mb/s downloads in my browser using comcast speed test, which is actually slightly faster than my performance tier. Uploads are what I'd expect and avg 5.8mb/s. Mail server names make no difference at all.
... View more
I've tried them all without success on port 995 w/SSL.....
mail.comcast.net pop3.comcast.net imap.ge.xfinity.com
During my troubleshooting I have made the following curious observations:
-The 4 step process of connecting to the server, logging in, checking for new mail, and retrieving new mail is painfully slow. It takes 30-60 seconds before the checking operation is complete, then another 60 seconds while retrieving new messages before the error appears "Failed: Connection closed unexpectedly by server". The whole process usually takes 90 seconds from start-to-error.
-When there is no new mail on the server, my client does notify me... No New Mail. But it takes 30 to 60 seconds instead of 2 seconds like it did from August to Nov 19 on port 995, and recently on 110 before it was blocked today.
-With test emails I've sent to one of my comcast addresses, messages containing 11kb of text are retrieved in 81 seconds. The same happens when the text file itself is sent as an attachment (instead of being pasted into the email message body). The only exception is when a message takes a little longer to retrieve, probably at the whim of connection/download speeds, at which time the error appears.
-The last 60 seconds spent on just the retrieval operation is consistent, as if it were a timeout of sorts, before the connection is closed unexpectedly by the server. Operations prior to the retrieval often varied in time, from 30 to 60 seconds.
-If the first new email to be retrieved takes more than 90 seconds, the error prevents access to any other messages. Have to go to web mail to clear the jam. Unfortunately I haven't received a real email that took less than 90 seconds.
My conclusion is that something with my Comcast server changed on Nov 19th that, a) caused the handshaking between server & client to slow down dramatically, and b) a message retrieval time of more than 60 seconds causes the server to close the connection. Given that port 995 w/SSL worked fine from August until that date, and that nothing whatsoever changed on my side of the wire, there's no other resonable explanation.
From what Again says, I'll be using pop3.comcast.net as my default instead of mail.comcast.net, even though all of them produced the same results for me. Why waste time chasing ghosts.
Now that port 110 is blocked I'm SOL with POP. I have only one more thing to try before throwing in the towel.
... View more
Just got the email shown below from comcast dated Dec 3 .
Port 995 with SSL still doesn't work, I get the same error message as before (Failed: connection to server closed unexpectedly). Port 110 works perfectly.
The incoming mail server makes no difference whether it is set to mail.comcast.net or pop3.comcast.net
This feels too much like Ground Hog Day. Are we going to have a repeat of what happened a couple of weeks ago?
On 12/6/18 I expect to have error messages on both ports unless Comcast gets it act together. THEN WHAT?
Subject: Final Reminder: Upcoming changes to your Xfinity email Date: Mon, 3 Dec 2018 14:22:58 -0800
Update your settings by December 6th. Remember to update your Xfinity email settings on your devices Beginning December 6, 2018, we are making changes to Xfinity email to increase your security. We’ve extended the deadline to give you a little extra time to update your settings. According to our systems, you access the email address email@example.com through a mail application other than Xfinity webmail, and you'll need to make a few updates to continue to use your Xfinity email with these other programs. If you don't make these changes to your settings, you will receive an error message after 12/6/18 when you check your Xfinity email. If you use Xfinity webmail or the Xfinity Connect app, you don't need to make any changes. Click here or visit xfinity.com/POPupdate for step-by-step instructions to change the security settings for the most common email applications. You can update the settings in just a few steps. You can also still access your Xfinity email via webmail by visiting https://connect.xfinity.com/ or by downloading the Xfinity Connect app here at any time. If you have any questions, click to chat with us. Our goal is to provide the best level of protection possible. Thank you for being an Xfinity customer.
... View more
pop3.comcast.net using port 995 w/SSL does not work for me. But oddly it depends on messages size, either way it's very slow. I'm in Phila BTW.
A simple 1 word test email DID get retrieved after 48 seconds.
A test email with a pdf attachment did NOT get retrieved, after 1 min 40 seconds I get the error msg "Failed: Connection closed unexpectedly by server."
pop3.comcast.net using port 110 w/o SSL works fine. Was finished retrieving test email with the attachment after 2 seconds.
I get the exact same behavior when using mail.comcast.net
... View more
I've seen several posts by you on this subject and have to applaud your personal efforts to fight misinformation spread by Comcast support. While you are not a Comcast employee, you certainly are a bright shining light in the midst of all the dim bulbs who are.
At the bottom of this post I pasted the content of an email sent to me by Comcast on August 2, 2018. The last sentence has led me to believe what you have been saying - users have a "preference" between IMAP & POP.
November 2018 is the month Comcast advertised the blocking of port 110 would take place, despite the September date in my email. I've had port 995 w/SSL active since August 2nd, when suddenly on Nov 19th that port stopped working. Unintuitively, the solution for me was to switch back to port 110 w/o SSL, while other folks had to resort to different solutions.
Now my anxiety is at a very uncomfortable level over which day in November the blocking of port 110 will actually take place. But more importantly, what will happen to users (like me) for which port 110 is their only working port. I guess we will have to wait and see.
Should the outcome be disappointing, Comcast needs to understand that for people who must store years of important email communications using their tried & true POP email client, that Verizon FIOS is a sensible alternative.
---Below is the text of the Comcast email--- We suggest you update your settings to improve the security of your email service. Since you use an email application (Outlook, Apple Mail, Thunderbird, etc.) with a ‘POP’ setting to access your Comcast.net email, you’ll need to update to your email settings by 9/12/18 so you can continue to receive your Comcast.net email through the application. Here’s how: Switch from POP to IMAP We recommend using IMAP for a more consistent way to access your email. Click here for step-by-step instructions on how to quickly make this change, and learn more about the differences between POP and IMAP. Update the POP port setting If you prefer to use your current POP settings to access your email, then you’ll need to update the Incoming Mail Server Port Number from 110 to 995.
... View more
I too had issues begin on November 19 while using my POP3 client. I spent most of the day wasting time with comcast and ended up with some jerk named Yves at comcast's Customer Solution Center. He tried to convince me it was an issue with my email client but had no answer for why my client worked perfectly since August when I first configured it to use port 995 w/SSL and then it suddenly stopped retrieving messages on Nov 19th. This guy had his head buried in the sand and couldn't face the reality that he was not smart enough to discover the issue with comcast's server and didn't have the motivation to escalate the issue to someone who did have the smarts. What's worse is that paying customers have to put up with a know-it-all who doesn't really know as much as he should to do his job. An amateur masquerading as a professional, what a waste of time that was.
What did work for me, at least for the time being, was to do exactly what another poster suggested, and what comcast said not to do. I changed my POP3 configuration to use port 110 without SSL. I couldn't believe how fast it downloaded all the messages, less than 3 seconds. With port 995 it took almost 2 minutes to get the error message that the connection was closed unexpectedly by server while attempting to download the 1st message. How messed up is it when comcast's recommended configuration doesn't work., but the configuration they've been telling people to avoid since August worked just fine.
... View more