POP always stalls on first message
TB v31.5.0.5531 POP3 Get Messages proceeds normally to "Downloading message 1 of nnn" in lower left corner. But it does not progress to message 2, 3, 4, etc. Not messages are actually transferred. There is no error message. This behavior began about three days ago and current TB version was installed well before that and no changes were made to TB settings or extensions recently. The email account is one of several email addresses on an Earthlink web hosting account. The accumulated mail is accessible via webmail and the number of messages corresponds to nnn on the TB screen, so TB obtains the correct number of messages to download, but doesn't download any. Earthlink tech service took this question seriously, concluded it must be a client problem.
I've tried simple reinstall of TB over existing install. Any suggestions?
선택된 해결법
If you access the account via webmail and delete the oldest message, the rest of the messages may download properly in TB. If not, delete the next oldest message, .... and see if eventually you can delete the one that is causing the problem.
문맥에 따라 이 답변을 읽어주세요 👍 1모든 댓글 (4)
선택된 해결법
If you access the account via webmail and delete the oldest message, the rest of the messages may download properly in TB. If not, delete the next oldest message, .... and see if eventually you can delete the one that is causing the problem.
Thank you sfhowes. Worked like a charm.
Been there done that. Sometimes it works, other times no.
Just happened to be in the Kaspersky forum looking for some information on another topic and discovered this thread: http://forum.kaspersky.com/index.php?showtopic=316779
Turns out this is a bug with the Email Antivirus component of Kaspersky Internet Security 2015. Apparently their developers are working on a fix. With that component turned off, TB works fine.
Thanks for the reply, johnmsch. I'm using NOD32 and Malwarebytes, no Kaspersky. For me deleting the oldest msg from the server did the trick. I should have mentioned I checked with task manager and the cpu wasn't compute-bound.