ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

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

  • 4 პასუხი
  • 3 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 8 ნახვა
  • ბოლოს გამოეხმაურა user01229325

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)

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

შერჩეული გადაწყვეტა

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

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

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.