Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

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

  • 4 odgovora
  • 3 imaju ovaj problem
  • 2 prikaza
  • Posljednji odgovor od 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.

Izabrano rješenje

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

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (4)

more options

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

more options

Odabrano rješenje

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.