Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

cannot log in w/Tbird, but OK with Verizon FIOS webmail

  • 4 件の返信
  • 3 人がこの問題に困っています
  • 8 回表示
  • 最後の返信者: user01229325

more options

Yesterday, everything was fine with my Thunderbird e-mail client. Today, I cannot receive mail. Thunderbird stalls for 20 seconds, then displays, "Sending of password did not succeed. Mail server pop.verizon.net responded: + " then "Login to server pop.verizon.net failed."

My settings for Incoming and Outgoing are correct, including ports. I entered password manually on subsequent attempt, to no avail.

I can send and receive e-mail on the Verizon Webmail site without problems.

I did perform my usual weekly cleanup last night, with Norton, Kaspersky, etc. tools, but can't think of a reason this would cause sudden problems.

Yesterday, everything was fine with my Thunderbird e-mail client. Today, I cannot receive mail. Thunderbird stalls for 20 seconds, then displays, "Sending of password did not succeed. Mail server pop.verizon.net responded: + " then "Login to server pop.verizon.net failed." My settings for Incoming and Outgoing are correct, including ports. I entered password manually on subsequent attempt, to no avail. I can send and receive e-mail on the Verizon Webmail site without problems. I did perform my usual weekly cleanup last night, with Norton, Kaspersky, etc. tools, but can't think of a reason this would cause sudden problems.

選ばれた解決策

That is what is good about email. It is great when it works. :) Would you mark your issue solved.

この回答をすべて読む 👍 0

すべての返信 (4)

more options

Now working. Don't know how/why, but problem solved.

more options

選ばれた解決策

That is what is good about email. It is great when it works. :) Would you mark your issue solved.

more options

I have this problem as well. What is the solution?

more options

The solution here was it started working on its own. The route to a solution for you is to start your own thread with the details of your problems and not tag on to a solved thread.