Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.
Solved In die argief

Some Local folders have been renamed as Sent

FlemingMJ99

I have several folders defined under 'Local Folders'. Two ('Mark_emails' and 'Mums_emails') have been renamed as 'Sent'..... so I now have 3 'Sent' folders! Looking at the properties of one of these, shows:

       Name:  Sent
       Location: mailbox://nobody@LocalFolders/Mark_emails

I can't change the name back to 'Mark_emails'. I've tried Repair, to no avail. I can't delete it either.

It's a similar situation with 'Mums_emails'

I want to keep the emails that these folders contain.

I'm using Thunderbird 146.0 (64-bit) on Windows 11.

I have several folders defined under 'Local Folders'. Two ('Mark_emails' and 'Mums_emails') have been renamed as 'Sent'..... so I now have 3 'Sent' folders! Looking at the properties of one of these, shows: Name: Sent Location: mailbox://nobody@LocalFolders/Mark_emails I can't change the name back to 'Mark_emails'. I've tried Repair, to no avail. I can't delete it either. It's a similar situation with 'Mums_emails' I want to keep the emails that these folders contain. I'm using Thunderbird 146.0 (64-bit) on Windows 11.

All Replies (2)

Gekose oplossing

See whether this helps: https://support.mozilla.org/en-US/questions/1554533

Alternatively just be patient and wait for the developers to fix this mess.

Gewysig op deur christ1

Installed the FolderFlags extension. Then when selected one of the errored 'Sent' folders, chose Properties, there is now a 'Flags' option. Selecting this showed that the 'Sent' flag was set. I removed this, and the folder went back to it's proper name (listed out of position under 'Local Folders' until Thunderbird closed and reloaded). Thanks for the info. And yes, the error occurred during the upgrade to version 146.0.