Open
Bug 837667
Opened 11 years ago
Updated 2 years ago
Mail (sub)folders with names containing a dot (".") are not recognised / can't be created while copying a folder tree
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: roelof, Unassigned)
References
Details
(Whiteboard: [dupeme?])
Attachments
(1 file)
30.50 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0 Build ID: 20130117042419 Steps to reproduce: dragging a whole folder (tree) from one account to another in the folder list, and dropping it on the other account name Actual results: the dropping auto-created the folder at the other account and started creating all the subfolders and copying their messages. This process stopped when a subfolder name was encountered containg a dot (".") .. a certain error message in the status bar appeared, like "can't create folder xx" or "folder xx doesn't exist" - i don't remember .. Instead, a subsubfolder was created, which name was the part after the dot .. see attachment screenshots. Expected results: the copy process should end normally : a subfolder name containing a dot (".") should be legal.
Reporter | ||
Comment 1•11 years ago
|
||
Comment on attachment 709703 [details]
folder copy error, name contained a dot
folder copy error, name contained a dot : "LauchPad.Net" was the name of the original folder, but during the copy process something else happened (see image) and the copy process stopped ..
Comment 2•11 years ago
|
||
Roelof did you mean to mark this bug security sensitive? Did you need to keep the screenshot private?
Reporter | ||
Comment 3•11 years ago
|
||
(In reply to David Bolter [:davidb] from comment #2) > Roelof did you mean to mark this bug security sensitive? Did you need to > keep the screenshot private? The screenshot doesn't need to be private. This bug might be security sensitive, i don't know .. that's why i marked it like that ..
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•