Unable to send messages
I can receive but not send messages, this has been going on for over a month now. I've tried several times to fix this but unable to correct it. The first error message prompted me to check password which I did. It worked for a few days, then it didn't. Checked with my IP to make sure I have the right port number and security settings: Port: 587, SSL/TLS. Started getting other error messages... this one is the latest: The message could not be sent because the connection to Outgoing server (SMTP) smtp.comcast.net was lost in the middle of the transaction. Try Again).
I'm on Macbook Air (Sierra 10.12.6). Using Thunderbird (115.18.0 (64-bit), says it's up to date. I've attached the last two messages and a snap shot of my smpt settings. My brain is fried from trying to figure this. I'm also wondering, if my OS software no longer supports this version. Any help would be greatly appreciated.
All Replies (4)
Those appear to be the wrong SMTP settings. According to Xfinity's support page, the correct settings are:
SMTP (Outgoing): SMTP Server Name: smtp.comcast.net Port: 465 Connection Security: SSL/TLS Authentication method: Normal Password OR OAuth2 User Name: <my email address>
https://www.xfinity.com/support/articles/email-client-programs-with-xfinity-email
You have port 587, but they specify port 465, and, in fact that's what I successfully use. So, change the port and see if you get better results.
Thanks for taking the time to reply. I did try changing port to 465, but received this error message: Sending of the message failed. An error occurred while sending mail. The mail server responded: vytHwfrAmFF6MvytJwsiIu DMARC Policy Enforcement: https://postmaster.comcast.net/smtp-error-codes.php#ODM00001. Please check the message and try again.
Do you use an Anti-virus or other security or network "helper" software? If so, maybe that's where that oddball port number came from. Try disable that AV or tell it to not scan email, or re-start Windows in Save Mode with Networking, which will temporarily disable the AV.
Well... I'm getting some resolution here... as I was finally able to find an explanation of the error code message (see attached). Apparently, I cannot send because I'm using my domain email as the reply to, saying it's protected by a DMARC reject. So I changed it using the comcast.net and it went through.
So if you can confirm/clarify my thoughts on this... I believe the source of the problem (s) began when my previous IP (OMNIS) was bought out and migrated over to Jet Host about a month ago. This is when I started having this issue, along with password recognition.
So... I'm assuming that I need to contact Jet Host to correct this DMARC issue... unless you have an alternative solution on how to correct it on my end?
Kind Regards, Tess
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.