חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

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

  • 4 תגובות
  • 3 have this problem
  • 8 views
  • תגובה אחרונה מאת 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.

Read this answer in context 👍 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.