Created attachment 383486 [details] Grab showing the issue I have to Archive Icons : * Archive folder * [Gmail All] I think one should be enough.
none of those folders should be showing up in smart folders mode, and they don't for me. Are you in smart folders mode? It's hard to tell since that's not your whole folder pane...that little grab only shows one archives folder, actually...
Sorry I have Ludovic@..... (imap gmail) inbox Archive Folder 1 Folder XXX [Gmail] Drafts Sent Mails All Mail Spam Trash Both Archive and All mail have the same Archive Icon. I'm in all folder mode.
Ludo I'm guessing you store Archived mail in the Archive folder and not in All Mail? (I think I changed it to All Mail for Gmail so I only have the All Mail folder)
(In reply to comment #3) > Ludo I'm guessing you store Archived mail in the Archive folder and not in All > Mail? > > (I think I changed it to All Mail for Gmail so I only have the All Mail folder) Yes exactly.
ah, ok - GMail really wants you to use the All Mail folder as the archive folder, so we set that up for the user. I suspect you used a nightly version of TB that created a special archive folder on the gmail server and then ran a newer version that knows to use the All Mail folder. What does account settings for that account say? We really should be removing the archive flag from the archive folder, unless the pref really says to use the archive folder.
I have : mail.identity.id1.archive_folder;imap://Ludovicemail@example.com/Archives mail.identity.id2.archive_folder;imap://Ludovicfirstname.lastname@example.org/Archives mail.identity.id5.archive_folder;imap://Ludovicemail@example.com/Archives mail.account.account2.identities;id1,id2 mail.account.account6.identities;id5 I think account6 is one of my usenet accounts while 2 is my main mail one.
Severity: normal → minor
Summary: My [Gmail] All email as the Archive folder icon → My [Gmail] All Mail and Archive folders both have the Archive folder icon, only All Mail should have the icon
Any updates on this bug since then? :)
You need to log in before you can comment on or make changes to this bug.