User-defined email tags not syncing to server in large Imap folders
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: cseo, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36
Steps to reproduce:
I've defined custom tags in user.js for many years (including redefinitions of $label1 through $label5, plus $label6 through $label9 and numerous others) and routinely assign them to emails. The problem affects all of them.
Actual results:
Tags are often no longer syncing between Thunderbird clients on my iMac (running Ventura) and MacBook (running Sonoma). This problem has been occurring prior to Sonoma and possibly prior to Thunderbird 115; it's only recently that I realized how frequent it is. I tried repair measures all the way up to reinstalling Thunderbird from scratch, to no avail.
My email provider is Ionos.com, which supports Imap tags. I use several email accounts with the same domain name in Thunderbird. The problem seemed to occur most often in my main account, which is much larger than the others. I logged into my main account via macOS Terminal and OpenSSL and confirmed that tags I set in Thunderbird would sometimes appear on the server with a FETCH (FLAGS) command, and sometimes not. (Conversely, tags I set via STORE +FLAGS command would always appear in Thunderbird.)
After repeated testing, the single factor I could see was folder size: tags did sync to the server when the email was in a small folder, but not in a big folder such as Archives. A more specific example: tags didn't sync in my Inbox when it was >1000 messages, but after I moved most of them to subfolders in Inbox to get it to <300, they suddenly started syncing.
Expected results:
Ideal behavior would be for custom email tags to always sync to server! But the size of the parent folder (excluding subfolders) appears to cause a problem. On the other hand, Starring a message syncs every time!
I can't rule out something funky with Ionos, but the following have been working reliably on folders of any size: (1) logging in to Ionos via Terminal OpenSSL and setting a tag via STORE +FLAGS; (2) defining an incoming message filter in Ionos webmail to add a tag and move to a folder. In both cases, Thunderbird always sees the tags.
Comment 1•2 years ago
|
||
How many tags are defined?
Are you directly editing prefs.js?
Are you using 115.8.1?
| Reporter | ||
Comment 2•2 years ago
|
||
Right now, 33 tags; I've probably had 20 to 30 for the last 5+ years.
They are all defined in user.js. As a test, I also tried adding a new tag via Settings > Tags > New…, which resulted in the same issue with not syncing to the Imap server from a large folder.
Currently using 115.8.0. Do you recommend upgrading and seeing if the problem persists?
| Reporter | ||
Comment 3•2 years ago
|
||
As for editing prefs.js, I may have tried to do that in years past to remove old tags, but not in a long time. Hopefully my clean reinstall of Thunderbird eliminated that as a possible factor in the problem.
Comment 4•2 years ago
|
||
Currently using 115.8.0. Do you recommend upgrading and seeing if the problem persists?
As far as I know no one is working on any problems in this area, I don't expect any fixes or changes.
Comment 5•2 years ago
|
||
I haven't touched the tags stuff in a long time. But I see the same thing that is reported.
By "does not sync" I assume the reporter mean he has two TB instances accessing the same mailbox and both instances are set to support "immediate notification" of new mail (meaning TB will use imap IDLE if server supports it). I tested like this with dovecot which supports IDLE and when I set a tag (e.g., Important) on instance 2 of TB it doesn't show on instance 1 of TB until I select the messages. However, if the "star" is selected too the changes shows up on the other TB instance automatically.
I see the correct response to imap IDLE in the log so the server is doing the right thing. But unless the star (\Flagged tag) is also set, any other built-in or customs tag don't automatically appear.
I tried this on a larger folder with 30k messages and a small folder with just 10 and see the same result.
In comment 0 reporter indicates that not sure if it was working before moving to 115 so I need to check if this is a regression.
Also, I'm not sure if the tag should appear automatically on other TB instance if that instance doesn't use IDLE (immediate notification).
:
:
After writing the above comment I thought this sounded familiar and I just found that the problem was reported earlier at bug 1865651. So I'm "resolving" this as duplicate of that bug. I concluded then that this is a UI bug.
Not sure why there seems to be no interest by the UI/supernova devs to investigate this.
FWIW, bug 1865651 points outs some workarounds for this issue until it is actually fixed.
| Reporter | ||
Comment 6•2 years ago
|
||
Hello gene, thanks for your efforts. I do experience the other bug, so appreciate those workarounds.
However, my custom tags were actually not being stored on the server, as confirmed with FETCH (FLAGS). And yet I can't reproduce that problem now on any size folder, haha. I'll blame the server.
Best,
Chris
Comment 7•2 years ago
|
||
Ok, I thought by "not syncing" you meant you could not see the tags on the other instance. But you were implying that the tags (keywords) were not being stored by TB on the server. I see that's what you meant after re-reading your earlier comments (and you made it clear in comment 6).
I haven't seen TB not store the tags when set in the UI, but, in the future, if you think it is not, you might consider recording and attaching an IMAP:4 log (as described here, https://wiki.mozilla.org/MailNews:Logging) which will show if the tags are getting stored or not.
Description
•