Summary: This week Comcast Xfinity sent out an email warning about outgoing email issues relating to email clients still set to use port 25. Due to spambot abuse, Comcast has been gradually blocking this port over the past 3 months and this belated warning email indicates to me that they’ve had a lot of upset/confused customers experiencing sudden, seemingly unexplainable issues with sending email. Today we talk about why Comcast is making this change and show you how you can proactively adapt instead of panicking when suddenly your email stops working. Scroll to the bottom of this post for instructions on adjusting settings in your specific email client (Outlook, Windows mail, etc.) as well as specific instructions for Vermont Design Works clients.
Please tell us in the comments whether or not these instructions were helpful to you or if you have further questions.
*UPDATED 3-4-13 – Scroll for Simplified Instructions and Screenshots*
Comcast Xfinity to Block Port 25
As part of a lengthy and technical blog post about internet security on August 1 of this year, Comcast Voices mentioned that they’d be phasing out support for Port 25 as an option for customers’ outgoing email server (SMTP). The post, which few people likely ever saw, didn’t exactly convey a sense of urgency, but did link to another post written the same day, explaining specifically why Comcast Xfinity would soon be blocking of Port 25 (emphasis mine):
Over the past few years, Comcast has managed port 25 by selectively blocking its use in response to spam complaints. This made sense when spam was often sent by an end-user clicking a “send” button. But in this age of bot networks, malware is now responsible for sending the most spam and users are unaware that spam is being sent by their computer.
As a result, we are updating our management of port 25. In order to ensure a more secure network and email domain, Comcast will no longer by default allow access to port 25 for our residential Internet users. In addition, we are asking comcast.net email users to migrate to port 465, which offers SSL encryption. We will continue to support the industry standard port 587. Upon request to our Customer Security Assurance team this block can be removed, enabling access to use port 25 for other email domains, though the comcast.net email servers will no longer accept submission via port 25. These changes will occur gradually across our network beginning today.
Translation: Spambots take advantage of Port 25′s vulnerabilities and use it to send spam from user’s computers. For that reason, Comcast will soon block this outgoing email port for users that use an email client on their computers (rather than webmail), such as MS Outlook, Mozilla Thunderbird, etc. Many ISPs have blocked this port for some time, but it’s a new change for Comcast Xfinity users. It’s important note that this change has the potential to affect any Comcast Xfinity internet customers who use email software on their computer. While it’s probably a good idea to change your outgoing port settings to 465 or 587, as Comcast advised above, they do state that for non @comcast.net email accounts, they will unblock port 25 upon request. We would however just advise that you change your port settings to make things easier. *UPDATE – Many Comcast subscribers have found that 465 (Comcast’s recommended port) isn’t working, but 587 is*
To further bolster their case, Xfinity adds the following:
There are number of other influential bodies that recommend against the use of port 25.The Federal Trade Commission (FTC), an organization that has taken legal action against many spammers, also recommends that port 25 is blocked by ISPs. The recommendation is as follows: “block port 25 except for the outbound SMTP requirements of authenticated users of mail servers designed for client traffic. Explore implementing Authenticated SMTP on port 587 for clients who must operate outgoing mail servers.”
Comcast Xfinity Sends Out Email Warning
As I mentioned, those blog posts were from August 1 – So why are we just bringing this up now? Because for whatever reason, one of our employees just received an email notification about this change at their personal account yesterday. (I mention “personal account” to differentiate from Comcast Business Class, which is our ISP here in the office, and as Comcast stated in the excerpts above, the change is just supposed to impact “residential Internet users”). The one caveat I think users should be aware of here is that some offices probably use “residential” Comcast Xfinity internet service, so you may not be immune to the change just by virtue of the fact that you’re in a commercial setting.
Comcast Outgoing Email Problems?
Have you already experienced outgoing email problems? That wouldn’t be surprising given that despite this email only coming out yesterday, they did announce on their blog (which I’d be willing to bet is very rarely read) that they would start rolling out the change more than 3 months ago. But don’t feel bad if you hadn’t heard and were suddenly unable to send email – you’re not alone.
We’ve actually had a handful of clients call in after experiencing this issue, although in most cases the problem had more to do with people moving from Comcast (and using Port 25) to another ISP that already blocked Port 25. Just a few months ago, an ISP change like this would cause outgoing email issues, but this move by Comcast Xfinity seems geared toward following industry best practices and blocking the port that most others already block. It’s important to note, however, that not all ISPs are blocking and some specifically request that you use 25, as you can see in Fairpoint’s Thunderbird email setup instructions. Just some things worth being aware of in case you plan to move to/from Comcast soon, or even if you’re just an existing customer who uses old port settings.
Vermont Design Works Client Email Settings
If you’re a VDW client, the most important take-away comes in the line about who this impacts. From the second paragraph of the first excerpt above – “comcast.net email users”. If you’re one of our clients, you’ve most likely been set up with email addresses that end in @yourdomain.com. If this is the case and we host your email, we specifically recommend changing your outgoing port to 587 and unchecking the SSL box in your email program’s settings. Comcast’s recommendation of 465 is specifically for @comcast.net email accounts.
How to Fix Comcast Outgoing Mail Server Port Problems
If you’re already experiencing issues with outgoing mail, Comcast provided some helpful links in yesterday’s email for configuring outgoing port settings for various email clients, but remember they are recommending port 465 which still isn’t working for many people, so you should use 587 when you get to that step:
Email Program Users (Outlook Express, Outlook, MacMail, etc.):
If you use an email program, this action will disable your program’s ability to send email until you change your email program settings to send email on port465587. (*Again, despite Comcast’s official recommendation to use 465, it still doesn’t work for many users*)To protect your email security, click on the link for your current email software, then follow the step-by-step instructions to change your settings.
Don’t see your email software? Then locate the preferences for your mail account in the software you use and provide the settings listed on this page.
If you’re a Comcast Xfinity internet customer, please let us know in the comments below whether you’ve experienced any outgoing server issues in recent months.
*UPDATES 3-4-13 – Use Outgoing Port 587*
I’ve made note of this is several sections in this post, but I thought this update deserved it’s own dedicated section, given the mess Comcast Xfinity has made. Apparently Comcast is still rolling out the blocking of Port 25, so many people are just now experiencing email issues. Unfortunately for many users the problem isn’t solved even if they follow the recommendations to change their outgoing port to 465. We’ve heard from a lot of people who’ve had this issue and the real solution in most cases has been to change the outgoing port setting to 587 and checking the box for “My outgoing server (SMTP) requires authentication” within your email account settings. See the screenshots below:
Comcast’s *helpful* links above will help you navigate to your account settings if you haven’t already gotten that far, but once you’re there, the settings above are the key. I personally experienced the 587 works/465 doesn’t issue myself this weekend, as my parents suddenly couldn’t send mail. I tried 465 on both of their computers to no avail, but they were back in business as soon as I tried 587.
*UPDATE 3-11-13 – Set Up SMTP Manually for Non-Comcast.Net POP3 Email Addresses*
Is Comcast your ISP, but not your email provider? Carl in the comments section offers the following tips for these situations:
Carl says:
Just noticed this today. Outgoing Emails for the last two days were hung up in my Outlook 2010 outbox.
I use another service in Outlook for incoming POP3 mail. I don’t use a comcast.net account for that purpose. I think many comcast customers do the same.
So the instructions on Comcast’s website and in your screenshots are incorrect for users with non-Comcast pop3 accounts. I that’s the case, you do NOT want to check: “Confirm that Use same settings as my incoming mail server is selected.” Instead, configure the smtp account separately.
Basically Carl is saying that you’ll want to set up your outgoing server manually, rather than selecting “Use same settings as my incoming mail server”. The interesting this is, as a Gmail user (personally at home) my incoming server isn’t Comcast either – incoming is pop.gmail.com, outgoing is smtp.gmail.com. So I still wouldn’t think that I’d need to change more than the port number, but Carl’s suggestion is certainly worth trying if you’re still stuck.
Alternative Simplified Instructions for Non-Comcast.net Users
In the comments Minda offers the following directions that helped her. Give these a shot if you’ve tried everything else and you’re still stuck:
THANKS TO ALL,
A light finally went on after reading Kara’s email…
FOR NON comcast.net users:
1. In Internet Email Settings – Change the outgoing email (SMTP) to smtp.comcast.net
2. In More Settings/Outgoing Server – check the box “My outgoing server requires…” AND choose “Log on using” the username and password you use to log onto the comcast.net website. Check Remember password. This username and password is different than the one I used on the Internet Email Settings page.
3. Under the Advanced tab, use 110 for the incoming box and 587 for the outgoing box. You might have to try both ways as to whether your server requires encryption.
Tags: Comcast, Outgoing Email Server, Outlook, Port 25, SMTP, Thunderbird, Windows Mail, Xfinity
I have two NAS devices from different manufacturers. On my Synology DS1512+, I was able to successfully change the SMTP Port for email notifications to 465. However, I am unable to change the Port# for email notifications on my older Buffalo Terastation Live. My Google research tells me that Port 25 is hardcoded into the firmware on the TSLive.
Is there anyway to change the outgoing port via my router? My router is a Netgear R6300. Any other suggestions are welcome.
THANKS TO ALL,
A light finally went on after reading Kara’s email…
FOR NON comcast.net users:
1. In Internet Email Settings – Change the outgoing email (SMTP) to smtp.comcast.net
2. In More Settings/Outgoing Server – check the box “My outgoing server requires…” AND choose “Log on using” the username and password you use to log onto the comcast.net website. Check Remember password. This username and password is different than the one I used on the Internet Email Settings page.
3. Under the Advanced tab, use 110 for the incoming box and 587 for the outgoing box. You might have to try both ways as to whether your server requires encryption.
Thanks to ALL. This morning, a Comcast truck was at the pedestal outside our house. Suddenly ~ whammo, not able to send on Entourage for 5 of my 6 accounts (don’t ask). Or my iPhone 4s. Same bullshit from Comcast: the initial CSR said she can’t troubleshoot third party email clients. I tried to explain I tested it all at two restaurants today, and on 3G on the phone WITH NO PROBLEM, meaning it was on Comcast’s end. She shuttles me to “Signature Support” who immediately begins trying to sell me by painstakingly listing the “benefits” of the service … I finally had to ask her to cut to the chase and the $, which would be $39,95 set-up and $14.95/mo. Amazing! I’ve been using the service for 13 years with no issue, and suddenly the ONLY place it doesn’t work is in my home and they want to charge me. THANK GOODNESS for forums ~ found the solution in about 10 minutes. LESSON LEARNED ~ check w/the people first!
Now, I’m off to social media to lambast Comcast. I suggest others who were given poor customer service do the same.
Still having comcast outgoing mail issues,will not send. I have tried changing the port to 587, still not working.
I have a dell laptop running windows 7 with outlook 2007.
I receive mail fine, but can not send email, however I have been able to send email off and on, without changing settings.
Also- recently had a comcast email address all of a sudden start receiving a ton of spam type emails when I wasn’t before.
If anyone can be of assistance I would be very grateful.
Frustrated – Jenn
I am having the same issues for out going mail, however, the only problem is through a scanner for “scan to email.” Incoming and outgoing email traffic is through gmail, but the scanner is on a comcast network. What do I need to configure for the scanner to work? I do not have a comcast email account. Thanks so much!!!
Wow, that’s way above my pay grade slzmn… Anyone else?
I am using Outlook 2003 as my email client. I have two pop3 accounts. A xxxxx@msn.com one, and a xxxxx@mr2cents.com that is hosted by ipower. The @msn account I have set up with incoming port 995, out going set to 587 works perfect with “this server requires ssl connection” checked off for incoming and out going mail.
On my xxxxx@mr2cents account if I check off “this server requires ssl connection” no matter what ports I am set to, I keep getting a warning error:
“The server you are connected to is using a security certificate that could not be verified.
The certificate’s CN name does not match the passed value.
Do you want to continue using this server?”
I click yes and everything is fine. This warning comes up every time I open Outlook 2003.
Now, if I do not check off “this server requires ssl connection” then the xxxxx@mr2cents works fine. No error message, when I start Outlook 2003.
I trying to find out, if I am playing with fire by not checking off the “this server requires ssl connection” boxes. But again this is the only way I am able to get rid of the warning, CN name does not match the passed value.
Gary
Forgot to mention that my email problems started on 3-13-13
out of the blue nothing would leave my out box.
Gary
Please since again comcast changed their ports my outlook 2007 has been resolved. However, my husband uses gmail & the info I was given was type:pop incoming: pop.gmail.com outgoing: smtp.gmailcom incoming port:995 outgoing port 465 ssl should be turned on. Still no emails are going out. I called Microsoft they will not help me unless I pay them $100 bucks for 30 days. I also tried the port 587. He gets emails in but no emails go out.
Please can anybody help. My outlook out going emails with comcast have been resolved. However, my husband uses gmail & his out going emails on outlook 2007 are not going out. His setting type: pop incoming: pop.gmail.com outgoing: smtp.gmail.com incoming port 995 outgoing port 465 ssl turned on. Still no outgoing emails. Microsoft will not help unless I pay them $100! Comcast tells me it is a Microsoft issue. I have been on line for hours trying to resolve this issue.
They’ve stepped it up. Now Comcast has made this change on their business class customers and has taken at least one of my customers Exchange servers offline. After talking with Microsoft (who was not happy with this change)and working with Microsoft on making the appropriate changes, emails STILL are not going out or coming in.
The ports that they told us to use were 465 for incoming and 587 for sending. After ANOTHER call to another technician, he tried to give me a different port entirely. I don’t think Comcast has the slightest idea what they are doing.
Outlook wasn’t working with Comcast either. Incoming mail worked fine. Outgoing did not. Changed incoming server to 995 and outgoing server to 587. I also had to put in my email user and password to re-set configuration. File save changes. Now working. This is Comcastic!
zoz
I didn’t realize my emails weren’t going out for a few days. Spent hours trying to make all the suggested changes. Finally fixed it with the following post. Thanks Bill!
Bill Draper says:
March 11, 2013 at 3:10 pm
I have been dealing with this all morning and just got it to work……
key is: pop 3
Settings: incoming outgoing same
check requires log in auth.
More Settings: (check requires auth.)
advanced tab: Incoming 995 requires auth.
Outgoing (SMTP)465 Encrypted connection SSL
I lost the ability to send email Saturday 3/30/31.
I followed Comcast’s recommendation for Outlook 2002 (2003) exactly to change the ports to 995 and 465. That only made it worse. Now I can’t receive emails. If I leave it at 110, no SSL I can at least recieve email. I tried your suggestion of using port 587 to send. That didn’t work. I installed Thunderbird. I set it up exactly like Comcast recommends (995 and 465). I can’t send or recieve. I tried ports 110 and 587. Now I can receive, but still can’t send. (BTW (I spent over 90 minutes on the phone with Comcast. I spoke to 7-8 different people (same story as above with them promoting their signature service…) I verified with each that I had each config screen set up as they wanted. It doesn’t work.
Looks like Comcast finally got around to blocking port 25 on my home internet connection on April 1, 2013. I run my own Exchange 2010 server, and suddenly couldn’t send or receive e-mail (my volume is incredibly small–a handful sent and less than 100 received per day, average 80% spam).
I’ve successfully configured my firewall and the Exchange Send and Receive Connectors to support port 587, and then configured an SMTP Port Forwarding service (EasyDNS.com) to relay my mail via port 587. Mail’s flowing again.
Interesting that it took them so long to finally block the port in my area.
David Marcus
Frederick, MD
I have same issue – unable to send email but able to receive it. It stopped working suddenly.
I tried all the options as mentioned but no luck.
But it is working normally when I tested it at my friends house.
Sorry to hear that Reddy. The only thing I can recommend is trying various combinations of the instructions above and note the different settings that should be used by comcast.net users vs. others.
Your tips were clear and easy to follow, but I cannot send or receive. I have checked my set up numerous times to no avail. Any ideas?
Well….
something was changed
using 529 for a while, now that doesn’t work
may cancel service and go with a hot spot AT&T
I have spent the last 2 days dealing with the most inept Comcast techs. My incoming email stopped suddenly. It’s been working fine all along (years). Several people have told me they sent emails, one especially a hotel confirmation, was never received. To get around this issue for now, I had all mail forwarded to my gmail account. The techs had me uninstall and reinstall Chrome, “that will work.” No it didn’t. Now I know why I’ll never have any bills sent email……….just won’t get them. What do I do short of changing from Comcast to something else?????
Thanks for your replies and assistance.
Can’t blame you Dave, this is ridiculous. You’d be shocked at how many visits this post gets because Comcast royally screwed up here.
Sorry Peggy, not sure I can help – this post is all about outgoing email issues. Incoming email problems is another problem.
Both POP3 995 and SMTP 465 ports work for me when using Outlook and Comcast mail. I tested both incoming and outgoing. Make sure you have both the boxes checked for incoming and outgoing mail: “This Server Requires an Encrypted Connection (SSL)” in Outlook when changing to 995 and 465 ports as it won’t work and you won’t be able to send/receive mail if you don’t have these boxes checked.
Randy, you are a genius! Thanks so much! I have been looking for a fix for a couple weeks now, and this saved me from throwing my computer out the window. Love me some Comcast…
I may have a more complicated issue here. I am running Outlook 2010 with my hotmail account as my default account and Comcast is my ISP. I do not have the option of changing my port setting for this account only! I have two others on there and they are both set to send from port 587 and working fine. The hotmail account is receiving fine but, it will not send. Any ideas how I can change that port setting? I also am using the hotmail connector which I think may be part of the issue. Thanks!
Thank you Bill Draper. I have GoDaddy as email and comcast as isp. This solution works perfect. Cheers
My scan to email function on my HP Color Laser Jet CM2320fxi MFP quit working in January, and I am getting around to fixing it. I use Outlook 2010, but do not have any issues getting or receiving email from Rackspace; only the outgoing email from the scanner is affected. With Port 25, the scanner said that it “cannot connect to the SMTP server.” After verifying the SMTP Gateway for Comcast (my carrier), which is smtp.comcast.net, I changed the SMTP Port to Port 587. Now, the scanner says the “an error occured while sending the email. Try sending again.” Repeating the scan did not work. I think the issue must be with the HP scanner, but HP business customer support (apparently the only one qualified to advise on scanners) is only open M-F. Any ideas gladly entertained!
David Marcus
I have no isea how to setup an SMTP Port Forwarding service (EasyDNS.com) to relay my mail via port 587.
can you help me with that, please
I also have all of a sudden stopped recieving email on outlook 2007 on 2 of 3 computers. Comcast just told me you can only use outlook for 1 computer this makes no sense. So I changed the settings to the setting on the one that does work and it stops again. I find this a little hard to believe after 7 years of using outlook on 3 computers it does not work anymore
Judith, if you want to receive all messages on multiple devices, you should set up your account as IMAP rather POP. Alternatively, you might be able to get by checking the box for “Leave a copy on the server” in your advanced settings, although in your situation that’s a workaround that may not produce ideal results.
Using Outlook 2010, outgoing emails stopped working a few days ago. port 587 no SSL and auth. req. still does not work. Any ideas? Thanks.
Thank you a thousand times thank you.
I was more than an hour and a half today with a Comcast
“technician” who did not tell me about the blockage of Port 25 and could not fix the problem of my outgoing mails, I have another server for my incoming mails and Comcast for the outgoing.
This “advice” was given after accepting to pay 49,95 dollars for a one time advice and solution (which was not the case) we are now hoping to get a refund. The tecnician blamed my incoming server. Reading your advice I could fix the problem and it is working perfectly!
Glad to help Ines. Comcast really screwed up here – as you can see I wrote that post several months ago but the problem is still cropping up newly for customers all the time.
I too have just experienced the “send” outage!
After trying every combo of settings and hours of calls and offers to fix the problem for hundreds of dollars, I finally can send emails with my Pop3.
110 in
587 out, no SSL
Requires authentication
Put in your Comcast user name
And your Comcast password
Not your Pop3 password
And like magic I’m back in business !!
Good luck and thanks for all of your good posts and advice.
I am a Comcast e-mail user through comcast not thru outlook or anything else. I can send e-mail but not receive. I spoke to a Comcast rep and she stated that my incoming ports 25 & 587 were blocked (not by me) and I needed to change my ports to 995 (?) and 110(?). However she did not know how to direct me to do it!
What is really interesting is that my wife’s email account is on the same computer and she goes straight to Comcast e-mail and doesn’t have a problem.
Can someone please explain in how to accomplish this!
Since I can’t receive email at comcast I have left an alternate email.
Thanks
Tom, are you saying you check your mail through webmail at comcast.net?
Yes. I check my email through Comcast. I have other email accounts such as yahoo and hotmail. Again I go directly to those accounts. I do not use an email client.
My wife accesses her emails in the same way. we also use the same computer with IE 9. She has no problems, so I don’t understand why I would need to change ports
Sorry to hear about the trouble Tom, but unfortunately this is a completely separate and unrelated issue. And it sounds like the Comcast person you spoke to was clueless. Port settings shouldn’t be an issue if you’re simply using web mail. The issue we’re talking about here with outgoing ports is the result of Comcast changing which outgoing ports it supports for those that use an email client.
Sorry,
When I saw the discussion about ports I was hoping to gain some knowledge and maybe solve my problem.
Thanks
I too have just experienced this problem. It worked fine before I went on vacation and figured I had “gremlins” invade the computer while I was gone. I have tried everything (I think) that ppl have mentioned and still can’t send (just receive). I am currently set at 110 and 587 … ugh this is annoying!!
Emails to my business site won’t go…just started this yesterday…very frustrating
Add me to the list. I’m using a Mac and out of nowhere on Wednesday, I am no longer able to send. Calls to Comcast were useless as they say as long as you can use the webmail, the problem isn’t on their end. I have tried changing my ports to 587 and 465 with and without SSL/password and it still doesn’t work.
Is there something else I can try?
With Outlook 2007 and MSN/Hotmail service, for me the final solution was:
“INTERNET E-MAIL SETTINGS”:
Account Type: POP3
Incoming mail server: pop3.live.com
Outgoing mail server: smtp.live.com
ON “OUTGOING SERVER” TAB:
Check box: “My outgoing server (SMTP) requires authentication”
Select circle: “Use same settings as my incoming mail server”
ON “ADVANCED” TAB:
Incoming server: 995
Check box: “This server requires an encrypted connection (SSL)”
Outgoing server: 587
“Use the following type of encrypted connection” – select from drop-down menu: “AUTO”