Thunderbird E-mail Client Anomalies
A couple of updates ago in Thunderbird, a couple anomalies have appeared which I haven't been able to fix! First one is there has been an additional folder added to the area where INBOX, DRAFT, SENT ITEMS, JUNK, and TRASH folders reside. The additional folder is "JUNK MAIL" and I cannot delete it. The original "Junk" folder is still present. Why do I need two different folders labeled JUNK MAIL and JUNK? Another issue is Thunderbird is very slow now when trying to "EMPTY" the TRASH! Takes forever to complete and many times will re-load the trash folder and then delete all the trash mail. Very frustrating! Can anyone help with this? "IF" I remove Thunderbird, (Uninstall), and then re-install will I loose everything? Any help would be appreciated!
Thank you! John
Обране рішення
Check with your email host. They may be including the extra folder. This is not unusual, as some email hosts provide 'Drafts' folders, not 'Draft', causing the same frustration. Assuming you defined the folder you want, see if you can right-click the account in folder pane, click 'subscribe' and untick the unwanted folder.
Читати цю відповідь у контексті 👍 1Усі відповіді (3)
Вибране рішення
Check with your email host. They may be including the extra folder. This is not unusual, as some email hosts provide 'Drafts' folders, not 'Draft', causing the same frustration. Assuming you defined the folder you want, see if you can right-click the account in folder pane, click 'subscribe' and untick the unwanted folder.
Thanks David! That remedied the "JUNK MAIL" folder. I should have known about that but it just wasn't popping up in my thinker! Now if I can figure out the slow motion anomaly when emptying the trash folder. Any ideas with that?
This sounds like a network issue. The files are online and Thunderbird downloads them to mark as trash and that generates the link on the server to remove them. I'm no expert at all in this network world, but you might try marking the trash to be downloaded, and it may be a server connection issue. Just guessing, of course.