Hello there Robert Chapin. We have read your message.

We try to help you.

Greetings Firefox volunteer.

—

hello there again. Here is a good add-on for safely removing the sub / folders from the trashcan on your computer machine.

https://addons.thunderbird.net/en-US/thunderbird/addon/remove-duplicate-messages/

Greetings Firefox volunteer.

Hello there Robert Chapin.

is there also talk of a double trashcan in your menu bar? or anywhere else?

the folders in your trashcan / folder? are these also renamed if they are duplicated?

There is not really much information on this subject at thunderbird it seems almost uncommon.

Let me hear from you.

Greetings Firefox volunteer.

Just as a level set - for a pop accounts only the Inbox interacts with the server, so everything in the Trash folder is from actions and activity taking place locally on your PC.

That said, I've never seen someone report what you are seeing.

I'm also having trouble with deleted messages not appearing in the Trash folder. I deleted a month-old message from my Inbox earlier today and now it is completely missing.

Right click the trash folder, select properties and then the repair button.

Does re indexing the file do anything here at all?

Repair doesn't seem to help, no.

In the meantime, I've disabled the Retention Policy for this folder, as I'm becoming highly suspicious of that feature.

Try "Rebuilding the Global Database" as per this very useful page: https://support.mozilla.org/en-US/kb/rebuilding-global-database

I've just observed Thunderbird adding messages to the Inbox that were already deleted. When I delete them again, they now appear as duplicates in the Trash.

I am going to also disable the "Leave messages on the server" feature to see if that helps.

Hello there

Thank you for using Firefox.

Firefox volunteer

I am happy to report that the problem is resolved after I did these three things:

1. Disabled the Retention Policy on the Trash folder, setting it to "Don't delete any messages."

2. Disabled the "Leave messages on the server" option for the affected account.

3. Upgraded to v60.9.0.

One or all of these things was likely flawed, so I will just avoid them going forward.

Thank you all for the ideas.