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".

Tìm hiểu thêm

Can no longer receiver emails

  • 3 trả lời
  • 1 gặp vấn đề này
  • 18 lượt xem
  • Trả lời mới nhất được viết bởi axw

more options

11/30/20 have not been able to receive emails but can send.

I have updated thunderbird. rebooted my router reset my password verified email works via web browser disabled my firewall No joy, Thunderbird refuses to get both my verizon and gmail mail.

I tried safe mode I turned on transaction logging 2020-12-01 04:51:11.673000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] LoadUrl() 2020-12-01 04:51:11.673000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] Initialize() 2020-12-01 04:51:11.736000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D7240] Connecting to server pop.verizon.net:995 2020-12-01 04:51:11.736000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] Setting server busy in nsPop3Protocol::LoadUrl() 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D7240] Entering NET_ProcessPop3 0 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D7240] Entering state: 24 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D7240] Entering state: 25 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] Clearing server busy in POP3_FREE 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] Clearing running protocol in POP3_FREE 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] ~nsPop3Protocol() 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 sink: [this=36BF9940] Calling ReleaseFolderLock from ~nsPop3Sink 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 sink: [this=36BF9940] ReleaseFolderLock haveSemaphore = FALSE 2020-12-01 04:51:21.109000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] LoadUrl() 2020-12-01 04:51:21.109000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] Initialize() 2020-12-01 04:51:21.112000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D70E0] Connecting to server pop.verizon.net:995 2020-12-01 04:51:21.112000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] Setting server busy in nsPop3Protocol::LoadUrl() 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D70E0] Entering NET_ProcessPop3 0 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D70E0] Entering state: 24 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D70E0] Entering state: 25 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] Clearing server busy in POP3_FREE 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] Clearing running protocol in POP3_FREE 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] ~nsPop3Protocol()

11/30/20 have not been able to receive emails but can '''send'''. I have updated thunderbird. rebooted my router reset my password verified email works via web browser disabled my firewall No joy, Thunderbird refuses to get both my verizon and gmail mail. I tried safe mode I turned on transaction logging 2020-12-01 04:51:11.673000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] LoadUrl() 2020-12-01 04:51:11.673000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] Initialize() 2020-12-01 04:51:11.736000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D7240] Connecting to server pop.verizon.net:995 2020-12-01 04:51:11.736000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] Setting server busy in nsPop3Protocol::LoadUrl() 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D7240] Entering NET_ProcessPop3 0 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D7240] Entering state: 24 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D7240] Entering state: 25 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] Clearing server busy in POP3_FREE 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] Clearing running protocol in POP3_FREE 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D7240] ~nsPop3Protocol() 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 sink: [this=36BF9940] Calling ReleaseFolderLock from ~nsPop3Sink 2020-12-01 04:51:11.825000 UTC - [(null) 15116: Main Thread]: D/POP3 sink: [this=36BF9940] ReleaseFolderLock haveSemaphore = FALSE 2020-12-01 04:51:21.109000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] LoadUrl() 2020-12-01 04:51:21.109000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] Initialize() 2020-12-01 04:51:21.112000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D70E0] Connecting to server pop.verizon.net:995 2020-12-01 04:51:21.112000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] Setting server busy in nsPop3Protocol::LoadUrl() 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D70E0] Entering NET_ProcessPop3 0 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D70E0] Entering state: 24 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: I/POP3 [this=304D70E0] Entering state: 25 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] Clearing server busy in POP3_FREE 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] Clearing running protocol in POP3_FREE 2020-12-01 04:51:21.167000 UTC - [(null) 15116: Main Thread]: D/POP3 [this=304D70E0] ~nsPop3Protocol()

Giải pháp được chọn

If you are using ESET/NOD32 security/AV then probability is very high it is causing your problems. According to their forums, you should temporarily disable SSL until they solve the problem per https://support.eset.com/en/kb3126-disable-ssl-filtering-in-eset-windows-products?ref=esf - the problem is being reported by dozens of users https://forum.eset.com/topic/26517-problems-with-thunderbird-and-imaps/ https://forum.eset.com/discover/

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (3)

more options

I have the same issue with a bunch of other accounts. Thunderbird (75.8.0 on Windows 10 Pro) just stopped downloading mails. It seems like it is trying to connect but to no avail.

more options

Giải pháp được chọn

If you are using ESET/NOD32 security/AV then probability is very high it is causing your problems. According to their forums, you should temporarily disable SSL until they solve the problem per https://support.eset.com/en/kb3126-disable-ssl-filtering-in-eset-windows-products?ref=esf - the problem is being reported by dozens of users https://forum.eset.com/topic/26517-problems-with-thunderbird-and-imaps/ https://forum.eset.com/discover/

more options

Thanks Wayne! much appreciated.