Error Message when sending email

[donjerue1]

I am suddendenly getting an error message when trying to send emails in an app I use - it was working fine a day or two ago, no changes have been made to the settings. The error message is as follows: : "Error with User authentication:Server says: 500 command unrecognized", 

My Apps Email client is set up as POP3:

Incoming Mail:       mail.comcast.net    Sever requires secure connection (SSL)

Outgoing Mail:       smtp.comcast.net   Sever requires User identification  (have User name & Pswd set & Port 587

Any ideas what is happening and how to fix?

[Again]

---

@donjerue1 wrote:

I am suddendenly getting an error message when trying to send emails in an app I use - it was working fine a day or two ago, no changes have been made to the settings. The error message is as follows: : "Error with User authentication:Server says: 500 command unrecognized", 

My Apps Email client is set up as POP3:

Incoming Mail:       mail.comcast.net    Sever requires secure connection (SSL)

Outgoing Mail:       smtp.comcast.net   Sever requires User identification  (have User name & Pswd set & Port 587

Any ideas what is happening and how to fix?

---

You need to set the secure connection as well, either to SSL or SSL/TLS, or TLS.

[R_Alarm]

Is this something new that needs to be set? Did Comcast change something recently? I have the same issue and my email app has worked perfectly for several years. However as of October 4, 2019 I have started receiving the same error message.

[cmbishop0823]

I have been having the same problem since Thursday last week. Email server not working at all called Xfinity and was sent to overseas customer support who were no help.  I am getting a connection error to the server when Ive been using it for years with no problem. 

[Again]

Check your email settings here.

[donjerue1]

This does not work eother, still getting error, allbeit a slightly different one:

"Error with sending sending HELO.EHLO:socket error"

Cant believe this has not been resolved by Xfinity, they obviously changed something!

[donjerue1]

Comcast is USELESS in sesolving this issue, and they remove my replies to that effect when crirrized....well they do inhale sharply no matter what...2 weeks, no solution no announcements? Decide for yourselves....

[Again]

---

@donjerue1 wrote:

Comcast is USELESS in sesolving this issue, and they remove my replies to that effect when crirrized....well they do inhale sharply no matter what...2 weeks, no solution no announcements? Decide for yourselves....

---

Your post was removed because you bypassed the language filters.  When they say "no" it doesn't mean time to get creative.

[erasure7]

I am getting the exact same problem as well, since the exact same date, Oct. 4th, 2019 with SMTP on Comcast.

I already had been using smtp.comcast.net, port 587, and username and password credentials for authentication.

And as far as I know, SSL / TLS is also enabled.  Does anyone know the low level telnet commands to pass to and from port 587 to troubleshoot and test further?

I use to know how to do this with basic SMTP protocol on port 25 (way long ago) HA.

And agree Comcast support / help has been less then stellar (i.e. completely useless and ineffective).  The more I request for Tier level 3 or higher support directly (the actual E-mail Server Administrators who configure these systems on the network and made the changes on Oct. 4th), and the deeper technical explanations I give, the more generic answers from Tier 1 I get, and generic transfer handoffs I get.  I have wasted hours waiting on holds for different people that are all unable to assist because they are never the right people.

I also want Comcast to provide alternative solutions technically to whatever change they mandated / forced in their configurations on Oct. 4th, because I have been operating with my app for years (over a decade plus), with no issues. I may require other options and workarounds depending on what is going on behind the scenes.  But I at least need a technical person who can deep dive troubleshoot at the network packet / protocol level on the other end. 

[DistantSun]

This happened to me as well. My fix was to turn on TSL/SSL and switch to Port 465 (I had been using 587). Hope that helps someone else.

[donjerue1]

It helps if your email client supports TSL...mine did not ;-(

---

@DistantSun wrote:

This happened to me as well. My fix was to turn on TSL/SSL and switch to Port 465 (I had been using 587). Hope that helps someone else.

---