Cannot access emails in local folders after upgrade to 128.10.1esr, caused by UNC pathing (local folders are on network and accessible to 3 different computers)
Since upgrade to 128.10.1esr, list of emails in local folders is visible, but cannot view email contents, cannot forward, cannot reply, cannot move, cannot delete.
IMAP folder functionality is all OK.
Occurs in both 64 bit and 32 bit versions of 128.10.1esr
After this occurred on 64 bit machine, we had 32 bit two machines running a previous version of Thunderbird that were still able to access (read, forward, delete, etc) emails in the same local folders (local folders are on network and accessible to 3 different computers).
After upgrading one of them, access to emails on local folders broke on that one, but still working on remaining machine running older version.
This means it is not corruption of local folders (e.g. folder repair and .msf deletion don't make any difference).
It seems to be a problem with this version since update.
How can this be fixed, do we need to wait for another update?
Zmodyfikowany przez Wayne Mery w dniu
Wybrane rozwiązanie
Hi Wayne, I mapped the network drive and changed the setting for the local folders directory to the mapped path and it appears problem has been solved. Thank you!
Wszystkie odpowiedzi (6)
Are you using UNC pathing for file/folder locations anywhere in your Thunderbird configuration?
I just caught this "(local folders are on network and accessible to 3 different computers)."
Are you seriously pointing to the same directory for local folders of multiple computers?
Hi Wayne,
Using UNC for local directory path.
Yes, three computers have access to the same archived email local folders on a network drive - has always worked without problems.
Note: Multiple users on the same data simply isn't supported. It might work for years, and then suddenly, not.
However, that's probably not what is causing your issue. See https://bugzilla.mozilla.org/show_bug.cgi?id=1966256
Can you map the location instead of doing UNC?
Zmodyfikowany przez Wayne Mery w dniu
Wybrane rozwiązanie
Hi Wayne, I mapped the network drive and changed the setting for the local folders directory to the mapped path and it appears problem has been solved. Thank you!
For me the solution worked out. Thanks.