Questo sito potrebbe offrire funzionalità limitate durante le operazioni di manutenzione per migliorare l'esperienza utente. Se un articolo non risolve il tuo problema e vuoi richiedere supporto, la nostra comunità di supporto è pronta ad aiutarti tramite @FirefoxSupport su Twitter e /r/firefox su Reddit.

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

How to reset send to > recent folder list? [was Where did the panacea.dat file go???]

  • 12 risposte
  • 1 ha questo problema
  • 2 visualizzazioni
  • Ultima risposta di OldBob2

more options

Where did the Panacea.dat file go--seems to be missing/moved since the last update. I used to be able to keep the email send to list reasonable by deleting this file and it automatically recreated the next time I opened Thunderbird. Now the file is not there.. The path I used to follow was Windows (C:)\Users\my name\AppData\Roaming\Thunderbird\Profiles\tx6pmhuc.default\panacea.dat (43KB) Yes, TB is closed and I have hidden files open to see.

Where did the Panacea.dat file go--seems to be missing/moved since the last update. I used to be able to keep the email send to list reasonable by deleting this file and it automatically recreated the next time I opened Thunderbird. Now the file is not there.. The path I used to follow was Windows (C:)\Users\my name\AppData\Roaming\Thunderbird\Profiles\tx6pmhuc.default\panacea.dat (43KB) Yes, TB is closed and I have hidden files open to see.

Modificato da Wayne Mery il

Tutte le risposte (12)

more options
more options

Thank you for your reply..the link you posted has entries from 15 years ago that concerns me.. I searched for this folder also with no results..where is it located and do you delete the entire folder? A bit more detail is needed to clear the most recent folder please.

more options

folderCache.json is a file in the profile folder. It is automatically recreated when TB is closed, the file is deleted, and TB is restarted.

more options

Thank you for the screenshot..I did find and deleted the foldercache.json and reopened TB and it did not clear the send to > recent listing. I even restarted the pc and tried again and the old list is still there. I do see each time I go into TB and out the time and date of this file is changing but the move to/recent list does not clear.

Modificato da OldBob2 il

more options

So I have seen other posts now on this issue and it seems deleting this new file does not clear out the recent list..How do you report this issue to programmers to fix?

more options

Issues are normally submitted to Bugzilla, but I would wait until 102.2 is released this week, as there have been some fixes for the folderCache.json file:

https://bugzilla.mozilla.org/show_bug.cgi?id=1776280

more options

Thank you for your advise.. hope this issue is resolved in the next update..

more options

If deleting folderCache.json doesn't clear it then the info probably isn't contained there. Did you try deleting session.json or xulstore.json ?

more options

Did no know to try this. can these two files be deleted safely and will they recreate when I boot up TB again? A bit out of my comfort zone so just wanted to check first before deleting anything.

more options

oldbob2 said

Did no know to try this. can these two files be deleted safely and will they recreate when I boot up TB again? A bit out of my comfort zone so just wanted to check first before deleting anything.

Yes, it ok to exit Thunderbird, then delete:

  • folderCache.json
  • session.json
  • xulstore.json

Start Thunderbird and report on results.

more options

I deleted the three folder and reopened TB. I put lots of folder views back to defaults but the send to /recent/ was NOT cleared as it did when previously did deleting the panacea file.

more options

Alas update 102.2.0 did not correct this issue.