Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Comcast smtp verification failed.

  • 1 resposta
  • 1 tem este problema
  • 123 visualizações
  • Última resposta de sfhowes

GrammieRee
GrammieRee
more options

Have used Thunderbird for some time now with NO problems. Then I received a notice from Comcast (xfinity) that I needed to change my password, so I did. Deleted old password in Thunderbird and added new one. (Yes, I'm sure it is correct, I've put it in numerous times..) Receiving comcast email just fine but when trying to send I get this error message: Sending of username did not succeed. Mail server mail.comcast.net responded: [AUTH] Authentication failed. Thunderbird gives me the option to Retry, Enter New Password or Cancel. I've tried them all. I've deleted and reentered the new password in Thunderbird repeatedly. Comcast says my SMTP port should be 587 or 465 if needed. Was set on 465 but have tried them both. I've tried choosing no authorization for SMTP instead of 'normal password' and receive this error message: An error occurred while sending mail. The mail server responded: 5.1.0 Authentication required. Please verify that your email address is correct in your account settings and try again. No matter what I try, I still am unable to send comcast email via Thunderbird. Please help! Mail provider: Comcast (xfinity) Firewall/Antivirus: Norton security suite (provided by comcast) OS: Windows 7 Home Premium 64-bit Version: Thunderbird 60.0b10

Have used Thunderbird for some time now with NO problems. Then I received a notice from Comcast (xfinity) that I needed to change my password, so I did. Deleted old password in Thunderbird and added new one. (Yes, I'm sure it is correct, I've put it in numerous times..) Receiving comcast email just fine but when trying to send I get this error message: Sending of username did not succeed. Mail server mail.comcast.net responded: [AUTH] Authentication failed. Thunderbird gives me the option to Retry, Enter New Password or Cancel. I've tried them all. I've deleted and reentered the new password in Thunderbird repeatedly. Comcast says my SMTP port should be 587 or 465 if needed. Was set on 465 but have tried them both. I've tried choosing no authorization for SMTP instead of 'normal password' and receive this error message: An error occurred while sending mail. The mail server responded: 5.1.0 Authentication required. Please verify that your email address is correct in your account settings and try again. No matter what I try, I still am unable to send comcast email via Thunderbird. Please help! Mail provider: Comcast (xfinity) Firewall/Antivirus: Norton security suite (provided by comcast) OS: Windows 7 Home Premium 64-bit Version: Thunderbird 60.0b10

Solução escolhida

They say the correct settings for the outgoing server are: smtp.comcast.net on port 587, STARTTLS security, authentication = normal password, and User name = full email address. If you still get errors with those settings, there is probably something else causing the problem, such as Norton, a VPN etc.

Ler esta resposta 👍 0

Todas as respostas (1)

sfhowes
sfhowes
  • Top 10 Contributor
more options

Solução escolhida

They say the correct settings for the outgoing server are: smtp.comcast.net on port 587, STARTTLS security, authentication = normal password, and User name = full email address. If you still get errors with those settings, there is probably something else causing the problem, such as Norton, a VPN etc.