Open
Bug 1265255
Opened 9 years ago
Updated 2 years ago
Add optional strict filename sanitizer to chose when saving multiple e-Mails to hdd
Categories
(Thunderbird :: OS Integration, enhancement, P5)
Thunderbird
OS Integration
Tracking
(Not tracked)
NEW
People
(Reporter: matombo, Assigned: aceman)
References
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160319202018
Steps to reproduce:
Saving multiple e-Mails at once dosn't give you the option to specify the filenames.
This can cause problems with specific file systems and OS
Actual results:
Saving e-Mails with special characters from Linux to a ntfs and then mount it on windows.
Or try to save e-Mails with special characters from Linux to a ntfs that is mounted with windows_names flag
both give errors
Expected results:
Add a option to sanitize filenames before saving to only include alphanumeric characters (and maybe also a check for case insensitive file systems)
Yes, I support this proposal.
I can look at implementing it when I get some time.
My suggestion would be to implement a generic sanitizer that worked on all platforms and all filesystems. User could turn it on via a preference. The sanitizer would only allow characters like [a-zA-Z0-9] (or [a-z0-9] if we wanted to be case-safe) and all others would be converted e.g. to '_'.
Assignee: nobody → acelists
Status: UNCONFIRMED → NEW
Component: Untriaged → OS Integration
Ever confirmed: true
OS: Linux → All
Priority: -- → P5
Hardware: Unspecified → All
See Also: → 1265153
Version: unspecified → Trunk
Comment 2•8 years ago
|
||
I'm faced with another manifestation of this bug: When saving a message at work with Icedove 38.8 on a FAT mounted FS, Icedove behave like if the file has been saved. But it wasn't!
-So while there wouldn't be sanitization, there must be an error message!
-I'm absolutely sure that the Icedove on my home's Debian Squeeze does sanitization, removing "Re:" and so on in filenames to be saved.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•