I have not been able to send email today. I get my email, but can't send. Using Thunderbird 60.6.1 on Windows 10. Using smtp.comcast.net on Port 465. Have also tried Port 587. Security SSL, Normal Password. Message is: Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) smtp.comcast.net timed out. Try again.
Checked Anti-virus program, Avast. Had an update in the que. Performed the update, restarted computer, outgoing email works again. I had restarted the computer a couple of times before and that had not fixed the email issue. Was the anti-virus update the solution, or did Comcast happen to fix a problem at that moment? Will likely never know. Has anyone had a similar issue?
I think it has something to do with the handshake between Comcast's servers and our outgoing mail. Perhaps they are trying to stop people who send out mass emails or malicious emails. I just wish Comcast technicians had the competence or authority to see this as an issue for us and would diagnose and fix the proplem. This has been an issue for years if you look at this and other forums. The good news is that I could still send out email this morning. Just waiting for the next incidence. Anyone who says they have "solved" the problem is kidding themselves.
Feel free to be cynical, but I've never had this "can't send email" problem in the ~20 years I've had Comcast as my ISP. This week was the first time I ever encountered it, and as mentioned it was the AVG email protection service the blocked outgoing emails. Kinda weird, I thought it was only to protect me from infected incoming email, which is the sort of help I need - no idea who they think they're protecting by allowing incoming email but blocking outgoing email while an update is pending upon a reboot.
I hope you're right. However, I've frequently gotten that message over the years, tried again, and it works immediately. I've also had it happen for an hour or so, retrying doesn't help, but then it starts working again without any restart or antivirus update. It makes me think the Comcast server occasionally takes its good old time reviewing the email and then it's timing out on their end or my end. I'd love to see a Comcast employee with knowledge of this interaction between our computers or other devices and their servers. Sometimes an incoming message will take hours before it shows up on my computer. Is this the same thing, in reverse?
You make a good point - where the <Edited. language> are the Comcast/Xfinity techs that used to regularly respond to questions/problems in the old version of help forums? Nobody minding the store here - that's a huge step backwards while our bills continue to go up every year!
Comcast changed the POP3 server settings? What ports were affected? I'm using smtp.comcast.net on port 465 for outgoing mail, have used those settings for many, many years.
Thanks, Daniel. I think you've made my point that the problem is systemic and Comcast needs to treat it as an issue on their end. I recognize they have to account for many types of devices interacting with their email servers. However, they need to take problems seriously and try to recognize that they might be the problem. I've gone to their support pages to see how to set up Thunderbird as my mail client, maybe find some recent changes in the instructions. The instructions are for Thunderbird 16.0 and higher. Thunderbird is on version 60.6.1. The setup pages and choices don't look anything like the current Thunderbird client. Can't they keep current? It strongly suggests they don't care about their customers. Their silence on this thread also speaks volumes.
I've only had one incident in the last couple of days. Wouldn't send an email, tried second time, still wouldn't send, checked anti-virus and it was up to date, no pending updates, closed Thunderbird, reopened and email sent. Don't know if closing and reopening Thunderbird did it, or if it was just the elapsed time.
Just tried to send an email. Timed out twice and then sent on the third try. Did not close program, just hit send three times. On the third try, it went.
I spoke with a Comcast engineer that was working on the problem. He stated that there were others that he was aware of that were having this problem and that they were attempting to find the cause and the fix.
I have an Arris SBG6782-AC Gateway. I went into the Advanced menu-Port Triggers. Your Gateway or router should have a Port Trigger setup as well. If you want to try and use the 465 for smtp with SSL, I think you could by following what I did here . Created the following:
Trigger Range-Start Port 587; End Port 587
and Trigger Range-Start Port 588; End Port 588;
Protocol Description: SMTP Comcast;
Protocol Both TCP/UDP
I then went to e-Mail accounts, opened comcast account- used the Outgoing Server (smtp) 587 withTLS encryption. Have been able to send emails to varied addresses with varied attachments. Opened/Closed Outlook, sent more successfully. Shutdown computer and upon restart opened outlook 2016 and was able to send. This is the longest I've been able to keep the smtp working. I'm hoping that the TLS setting in Outlook will allow encryption to work even though I've opened the Trigger for the smtp port. Why other computers at the house were able to work fine with smtp 465 and this computer was only able to use it for a brief time is still a mystery. will keep you posted.
I uninstalled Outlook 2016 pro plus and installed outlook 2019 pro plus. After all those settings I tried in yesterdays post, the SMTP still fails. It worked yesterday using smtp.comcast.net with SSL/TSL port 465. This morning not happening. Same errors:
Task 'Comcast - Sending' reported error (0x800CCC1A) : 'Your server does not support the connection encryption type you have specified. Try changing the encryption method. Contact your mail server administrator or Internet service provider (ISP) for additional assistance.'
I went into command mode, typed in 'nslookup smtp.comcast.net' (no quotes) & get the following:
It's connecting but not working. I changed back to the outgoing: Startls, port 587 and it works. I've had to go back and forth doing this when one stops working. This makes no sense.
I beg to have a specialist reach out to fix this issue.
Thanks kbouter1 for all the detail you've provided about your issue. I'm not sure if your issue is related to the one that started this thread. The rest of us are not getting an error code, just the message "Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) smtp.comcast.net timed out. Try again." Your efforts at finding a solution are instructive, however. We all attempt things that appear to solve the problem, but then it comes back. Last night, I again could not send a message. I made my normal three attempts, still could not send. I saved the message as a draft, shut down Thunderbird, reopened, and then the message could be sent. I would appreciate having a Comcast employee with technical skills address this issue. Don't come on here with a script of things to try. What does this message mean and how can we or Comcast solve the issue. Still crickets from Comcast.
Just tried to send my first message this morning, timed out. Tried three times, no help. Shut down Thunderbird, reopened, tried three more times, no go. Getting very tiresome, Comcast. Where are you?
Problem with SMTP server.
Pinging to smtp.comcast.net fails with IPv6 address [2001:558:fe21:2a::5].
Pinging to smtp.comcast.net succeeds with IPv6 address [2001:558:fe16:1b::16].
This means that it's a toss-up if you reach the GOOD server [2001:558:fe16:1b::16] or the BAD server [2001:558:fe21:2a::5]. I hope Comcast will address this soon.
Sorry about the instructions. We are all having an issue with the smtp timing out with no codes to varied codes. I guess I thought people would want to try to get it working since comcast does not seem to appear in this forum.
My confusion starts with why does my mac & another identical windows computer work fine? Hence the recommendations I have going. If others are interested in what else I have done to get it working, we can pm
scheinbergh, this is the best explanation I've seen. Thanks. How can you tell which server your message is going through? Is there any way to get this issue directly to Comcast or do we just have to keep trying through this forum. Is there any way we can force our message to go out through a different server? I still can't send out my message from this morning. I find it hard to believe that I'm randomly drawing the same server over this period of time.
Glad you guys checked out the smtp email addresses as I suggested. I have opened port 587 & 465 in windows 10 firewall and excepeted the actual smtp.comcast IP address I got from the command I used (220.127.116.11) into malwarebytes and avast. With all that. I'm running outlook as it should. Have been able to shutdown computer and get messages to send after starting back up. BTW, I'm using IMAP. AS stated, unfortunately, comcast seems to not give us a moderator for these issues and keep us informed. Are any of you having thsi issue with other computers you use?
I had same problem for weeks. First I blamed the server, then my router, etc, but then realized my wife had no trouble with her SMTP on her LT on the same home network. Just now got it straightened out.
I use Avast Free Antivirus and found the fix within that software as below. You may use a different antivirus, but a similar inspection of your antivirus may help:
Bring up Avast main screen.
In upper right corner, click on "Menu" icon, then click "Settings" option from drop down menu.
Click "Protection" from left hand column, move right and select "Core Shields".
Scroll down to "Configure Shield Settings".
Immediately under that, click the tab, "Mail Shield", the right most tab.
If "Scan Outbound Mails" check box is checked, uncheck it, open your email program, send yourself an email to see if it works. It should send immediately.
X out of Avast.
This worked for me. Good luck.
Thanks for this response. I just followed your instructions and updated Avast. I can't see why I'd want to scan outgoing messages for viruses, so I don't think I've lost anything. This actually looks like it might address the problem. I haven't had an issue in a few days, so I can't say it worked, yet. Will have to see if this recurring problem comes back, but you've given me some hope.
Same problem on my cell phone but only at home. Works fine everywhere else.
Anyone else with this issue. Comcast has been no help.
Are you getting a wi-fi signal on the phone at home?
Those instructions work for AVG Antivirus Free too, exact same steps - I haven't had the problem re-occur, but went ahead and stopped AVG from scanning outbound mail anyway - I know at least one of my email sending failures to send was due to an AVG update needing a reboot, and I practice safe hex, so I'm not sending out infected emails to start with.
Just sent my first email this morning. It took much longer to send than usual. Just as I thought I was about to see it time out, it finally went. Since Avast is not scanning outgoing email anymore, it must be Comcast taking its time scanning the email on its end. If it makes any difference, the email was sent to one person and it had a 253kb jpg image attached. I would still like to have a knowledgeable Comcast employee weigh in. No scripts, please.
As you stated, this was not an antivirus problem. Mine seems to be better, (as in not fixed) but at times sending a photo or video is about like it used to be with dial-up; hit send and go fix a sandwich.
I even tried sending while logged in to my email directly on Comcast site, itself, no joy.
Good luck. <Edited> Have a great day.
I apologize that we haven't responded to this thread earlier. I'd be happy to check if we have any issues with the outgoing server. Just to make sure, I understood the issue correctly, I have to ask several questions:
- Have you noticed the issue only with 3rd party apps?
- Have you tried to send an email from the xfinityconnect.email.comcast.net or Xfinity Connect App?
@edsooper - Thank you for letting me know. If you will get an issue with sending emails again, could you please send me a private message with the example? I need an email recipient and timestamp + your first and last name and your email address. You can send me a private message by clicking on my name ComcastElla, then click Send a message.
ComcastElla, I use Thunderbird as my email client. I have Windows 10 operating system. I use Avast antivirus. Some days, I can't send email. As stated earlier in this email chain, I get the message "Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) smtp.comcast.net timed out. Try again." This is not a helpful message. Is it coming from Comcast servers? What causes them to time out. This morning, it took a long time for my message to be sent; normally, I would get the "time out" message if it took that long, but not today. And the message finally went out.
Cynic in me would say Comcast is throttling attachment containing email bandwidth, but given how much spam is getting through their nearly useless filters I don't think they're worried about how much bandwidth email consumes! Every morning I wake up to a flood of 15-20 spammy mail in my inbox, and a bunch of them in my deleted folder because I've created 17 custom rules to delete emails with subject lines containing certain words. - my "Junk Mail" folder, where Comcast's spam filtering sends spam, has the fewest new messages every morning. But my freebie Yahoo email accounts are 100% spam free......something wrong with this picture......
@virginiabuckeye - Thank you for letting me know. The "smtp.comcast.net timed out" error message is very general. It could be an issue with the server or a connection problem. Do you get the same issue on the xfinityconnect.email.comcast.net website?
@tolsen35 - Do you use a native email app or Xfinity Connect?
@Indigo - I have several email accounts with Yahoo, Gmail + College Emal - all of them are getting spam emails. It depends on how much you use your email address and enter it on different websites. Even for legit websites. For example, my Yahoo email account gets at least 20 spam emails every day. Some of them are in Spam folder, some end up in my Inbox. It's not Yahoo's fault - I just enter this email for any online registration and spam filter cannot guarantee a 100% protection from spam emails. My Gmail and Comcast accounts may get one or two spam emails in a month. Because I mostly use them for communication with my friends and family.
I never send emails from the Xfinity website and rarely from my iPhone. The last emails I sent from my iPhone were probably when I was on vacation last summer. I did not have a problem, but the timeout issue is sporadic so I can't say that says anything about the issue. I will go months with no problem on my computer, then go many days in a row where I can't send emails.
@virginiabuckeye - If you get an error message, could you please let me know right away? I will check if we have any issues with the server at that moment.
@tolsen35 - Got you. Do you have any recent examples? I would greatly appreciate it.
@jiminindy - Thank you for letting me know. To address any issues with the server, we will need to get some examples. Would you please send me examples when you get them?