Problems after renaming a folder when folder name is very long (> 192 characters) on FreeBSD OS
Categories
(Thunderbird :: OS Integration, defect)
Tracking
(Not tracked)
People
(Reporter: paul, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
Ok sub-folder was renamed to a longer folder name that past 192 characters in length?
Actual results:
folder rename failed on thunderbird
getting message when trying to access the folder saying
Unable to open summary file for .....
perhaps there is an error on disk or the full path is too long.
Expected results:
Folder should have renamed :
please note the following info from this bug
I am running dovecot 2.3.19
summary file DOES contain the proper info (subscriptions within dovecot.)
"subscriptions:INBOX Contract Region of Durham RFP-347-2021 Prequalification Registry of Contractors Works W-058 WM Emergency Repair Victoria and Hopkins"
filepath is valid and does work (am running freebsd zfs file system)
"""[09:33:45] mail18.scom.ca [root:0] /data/dovecot/users/elirpa.com/keith@elirpa.com/.INBOX.Contract.Region of Durham.RFP-347-2021 Prequalification Registry of Contractors.Works.W-058 WM Emergency Repair Victoria and Hopkins/cur"""
file path seems to be aprox 192 in length or more?
thus causing the folder access issue.
I can access folder and rename it smaller on webmail.
figure thunderbird should support length of folder up to and including 255
or at least stop the folder rename/create and explain the path went too long ?
something like when creating a folder with a period in it or '/' ??
|
||
Updated•3 years ago
|
|
|
||
Comment 1•3 years ago
|
||
Search for similar bugs: https://mzl.la/3JdgyzJ
Paul, so you have first renamed the folder inside Thunderbird (from short name to long name)?
Then Thunderbird first accepted the rename without error message and then failed later?
Your report is pretty hard to read...
As an easy workaround, if I may say so, consider shorter folder names ;-)
|
||
Updated•3 years ago
|
This may be related:
TB has begun adding a "nobody" in the line pointing at the users local mailbox. The user nobody only exists in the /etc/group file.
TB accesses my imap inbox at shentel.net but I keep as much local as TB allows.
To Show, edit an existing but just recently made incoming filter, or make a new filter, and then edit it look at the mailbox address the message is to be moved to.
Old filters from a year ago work ok.
To make that even more upsetting, that line is not editable in the editors screen. so all you can do is delete
the malformed filter, leaving the high traffic stuff in ones inbox. The user can't fix it.
Resolved per whiteboard
Description
•