![]() This will make things faster)ħ- IN GMAIL: Get inside LABEL 1, hit select all so you can select the first 100 mails. ![]() Now check that the error is now in LABEL 1.Ħ- IN GMAIL: Go to settings - Change the maximum page size to 100 (so you can see 100 msgs per page. INBOX must be empty after this step) every mail from INBOX to LABEL 1ĥ- IN THUNDERBIRD: Check that the INBOX is empty and the error message is gone. Check that the problem still persists in the INBOX.Ĥ- IN GMAIL: Move (yes, move. In my case, y had 4 problematic mails in my INBOX, neither of them was the last one.ġ- IN GMAIL: Get into every label and ARCHIVE every mail in there (so i move them away of my INBOX)Ģ- IN THUNDERBIRD: Check that there isn't any problems inside any labels (aka folders). This is what i replied in there in case that his may help you: So, I've found it helpful to find out the number of messages that are corrupted. ![]() It then goes on to point out that there isn't a way to correlate the message UID in the log to the messages in Gmail. MailNews:Logging - Generating a Protocol Log It gave the advice of creating a Protocol Log from Thunderbird and examining the log to find out the UID of the corrupted messages. I recently came across the most helpful info I've found concerning these error messages in this thread on the Gmail support forums Otherwise, you have more messages that are corrupted that you need to find and delete. I once had 20 corrupted messages and 12 of them were from the same sender.Īfter you delete the message, close Thunderbird and reopen - if the error is gone you're done. If possible, take some notes about the message (sender, etc.) - it may help identify other messages that are corrupted. ![]() You'll know that you've found a corrupted message because you'll see the following (or similar) message at the top of the screen (it may retry several times before saying the message is unavailable):Īfter it gives up trying to load the message you'll have to go back to the message listing to delete the corrupted message. That creates another problem - there isn't really an easy way to find the corrupted messages except by trying to open them in the Gmail web client. The only way I've found to fix the errors is to track down which message(s) are causing the problem and then delete them. It most likely means that there is a message that is corrupted on Gmail's servers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |