urlencoded filepaths in IMAP

RESOLVED INCOMPLETE

Status

Thunderbird
OS Integration
RESOLVED INCOMPLETE
2 years ago
2 years ago

People

(Reporter: Jim Michaels, Unassigned)

Tracking

38 Branch

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (Windows NT 6.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36

Steps to reproduce:

used IMAP for email
looked at profile using a cd burning program or windows explorer.


Actual results:

filepaths were created per email that wrote % signs and other disallowed characters.
like %40 for @
look at NTFS spec to find out what punctuation is allowed: pretty much . and - and _ only. 



Expected results:

base64encode()?
(Reporter)

Comment 1

2 years ago
- also, the filepaths are WAY too long. NTFS allows 255 characters max per path, ReFS 32768.
- I hear the ASCII equivalent of \ is not encoded.
- I hear the ASCII equivalent of * is not encoded.
- I hear the ASCII equivalent of \| is not encoded, and you know what | is used for.

Comment 2

2 years ago
(It would be super great if you would answer questions in old bug reports like bug 1274477 and bug 1267731 before filing new bug reports)

A. As a frequent bug reporter you should be filing bugs against the most current version. Version 38 is not.
B. "filepaths are WAY too long" is something *you* need to mitigate and guard against
C. "filepaths were created per email that wrote % signs and other disallowed characters. like %40 for @"  How about a screen shot or an example
D. Try explaining things in terms of steps that other people can use to reproduce your issue
Flags: needinfo?(jmichae3)
Summary: fs corruption because of urlencoded filepaths in IMAP → urlencoded filepaths in IMAP
Whiteboard: [closeme 2016-06-10]

Comment 3

2 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 2 years ago
Flags: needinfo?(jmichae3)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2016-06-10]
You need to log in before you can comment on or make changes to this bug.