Mail (sub)folders with names containing a dot (".") are not recognised / can't be created while copying a folder tree

UNCONFIRMED
Unassigned

Status

Thunderbird
Folder and Message Lists
UNCONFIRMED
5 years ago
2 years ago

People

(Reporter: Roelof Berkepeis, Unassigned)

Tracking

17 Branch
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [dupeme?])

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 709703 [details]
folder copy error, name contained a dot

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

5 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 ..
Roelof did you mean to mark this bug security sensitive? Did you need to keep the screenshot private?
(Reporter)

Comment 3

5 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 ..

Comment 4

5 years ago
not sec sensitive
Group: core-security
Whiteboard: [dupeme?]

Updated

2 years ago
Duplicate of this bug: 1205315
You need to log in before you can comment on or make changes to this bug.