We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Sending of the message [via Earthlink] failed. ... you may be susceptible to getting your password stolen.

  • 2 个回答
  • 2 人有此问题
  • 32 次查看
  • 最后回复者为 ecruoff

more options

Yesterday 6/1/21 TB 78.10.2 on my two Dell laptops stopped being able to send messages via Earthlink with 'Authentication method: Encrypted password', though my Gmail accounts still work. Now it says:

Sending of the message failed. The Outgoing server (SMTP) smtpauth.earthlink.net does not seem to support encrypted passwords. If you just set up the account, try changing the 'Authentication method' in 'Account Settings | Outgoing server (SMTP)' to 'Password, transmitted insecurely'. If it used to work but now doesn't, you may be susceptible to getting your password stolen.

Changing to 'Password, transmitted insecurely' allows sending, but I'm uncomfortable with that setting. "It used to work but now doesn't," so I wonder what the rest of the message means.

Suggestions?

Yesterday 6/1/21 TB 78.10.2 on my two Dell laptops stopped being able to send messages via Earthlink with 'Authentication method: Encrypted password', though my Gmail accounts still work. Now it says: Sending of the message failed. The Outgoing server (SMTP) smtpauth.earthlink.net does not seem to support encrypted passwords. If you just set up the account, try changing the 'Authentication method' in 'Account Settings | Outgoing server (SMTP)' to 'Password, transmitted insecurely'. If it used to work but now doesn't, you may be susceptible to getting your password stolen. Changing to 'Password, transmitted insecurely' allows sending, but I'm uncomfortable with that setting. "It used to work but now doesn't," so I wonder what the rest of the message means. Suggestions?

被采纳的解决方案

I've been having a similar problem with sending emails. I just discovered the following solution in another thread in this forum, entitled 'Thunderbird "Send Message Error"':

    These are the outgoing server SMTP setting which you should be using:
    outgoing server (SMTP): smtpauth.earthlink.net 
    Port: 587 
    Connection Security: STARTTLS Authentication      
    Method: Normal Password 
    User name: <email address>

So I went to my Outgoing Server Settings, found under Menu/Account Settings. (NOT Menu/Account Settings/Server Settings.) Clicked on the button marked 'Edit SMTP_server'. There I changed the Authentication Method from 'Encrypted Password' to 'Normal Password'. That seems to have fixed the problem. Emails are now sending without incident.

Based on the thread mentioned above, this issue may have been caused by Earthlink changing its server settings.

Good luck, hope this helps.

定位到答案原位置 👍 0

所有回复 (3)

more options

After update to 78.11.0, the problem disappeared -- I'm again able to send messages via Earthlink with 'Authentication method: Encrypted password'.

more options

Woops! The problem is back. TB is still 78.11.0.

由rwiniecki于修改

more options

选择的解决方案

I've been having a similar problem with sending emails. I just discovered the following solution in another thread in this forum, entitled 'Thunderbird "Send Message Error"':

    These are the outgoing server SMTP setting which you should be using:
    outgoing server (SMTP): smtpauth.earthlink.net 
    Port: 587 
    Connection Security: STARTTLS Authentication      
    Method: Normal Password 
    User name: <email address>

So I went to my Outgoing Server Settings, found under Menu/Account Settings. (NOT Menu/Account Settings/Server Settings.) Clicked on the button marked 'Edit SMTP_server'. There I changed the Authentication Method from 'Encrypted Password' to 'Normal Password'. That seems to have fixed the problem. Emails are now sending without incident.

Based on the thread mentioned above, this issue may have been caused by Earthlink changing its server settings.

Good luck, hope this helps.