Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Learn More

https://mail.yahoo.com won’t load without deleting the mail.yahoo.com cookie. This has to be done periodically as my Yahoo mail inbox breaks periodically, showing the message "no Internet connection" even though the connection is fine.

  • Không có trả lời
  • 1 gặp vấn đề này
  • 1 lượt xem
more options

https://mail.yahoo.com won’t load without deleting the mail.yahoo.com cookie. This has to be done frequently during the day as my Yahoo mail inbox periodically breaks, showing the message "no Internet connection" even though the connection is fine. When this occurs, I get no response whatsoever when I click to refresh the page or reenter the URL address and hit Enter. I can close the page, then reopen it, to no avail. That’s when I have to delete the cookie to get everything working again. When I first open Firefox and go to my.yahoo.com and mail.yahoo.com (which automatically goes to https://mail.yahoo.com/d/folders/1?.partner=sbc since my email address uses @sbcglobal.net), there’s no problem. It only occurs later. This doesn't happen with Chrome and used to never happen with Firefox.

https://mail.yahoo.com won’t load without deleting the mail.yahoo.com cookie. This has to be done frequently during the day as my Yahoo mail inbox periodically breaks, showing the message "no Internet connection" even though the connection is fine. When this occurs, I get no response whatsoever when I click to refresh the page or reenter the URL address and hit Enter. I can close the page, then reopen it, to no avail. That’s when I have to delete the cookie to get everything working again. When I first open Firefox and go to my.yahoo.com and mail.yahoo.com (which automatically goes to https://mail.yahoo.com/d/folders/1?.partner=sbc since my email address uses @sbcglobal.net), there’s no problem. It only occurs later. This doesn't happen with Chrome and used to never happen with Firefox.