You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
looks like that profile/account is affected by #19 - please try the steps described in #19 (comment) and the follow up posts. If you get the same error messages ("folder not found") you'll have to wait for the next Thunderbird major release, I'm afraid.
Also make sure, that your folder names don't contain any special characters (like @ or +), as Thunderbird is currently unable to handle them - see #223.
Thanks for the quick reply!
At least on folder can not be parsed (using the code snippets provided
in #19). There '#' caracters in this folder, but I have a lot like
this... so never mind, I won't use thirdstat on this account.
Best regards
Le 06/05/2021 à 16:36, Andreas a écrit :
Hi there,
looks like that profile/account is affected by #19
<#19> - please try the
steps described in #19 (comment)
<#19 (comment)>
and the follow up posts. If you get the same error messages ("folder
not found") you'll have to wait for the next Thunderbird major
release, I'm afraid.
Also make sure, that your folder names don't contain any special
characters (like |@| or |+|), as Thunderbird is currently unable to
handle them - see #223
<#223>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#311 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AN3RE65PG5COBUR3EQYY2I3TMKSP7ANCNFSM44HDMBSA>.
You're welcome. Afaik the problem with special chars in folder names has already been fixed and will be part of the next major release of Thunderbird. Nevertheless thanks for reporting.
When I launch the thirstat indexing, is starts then is blocked (for hours) at something like 70%. This may be a special case with my mail box...
With the same thunderbird installation, but on a different profile, the same thirdstat plugin (of course) works perfectly.
The text was updated successfully, but these errors were encountered: