Closed
Bug 142464
Opened 23 years ago
Closed 20 years ago
import mail with mail folder named /. creates odd folder heirarchy
Categories
(MailNews Core :: Import, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.8alpha4
People
(Reporter: stormpunk, Assigned: cavin)
References
(Blocks 1 open bug)
Details
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90; Q312461)
BuildID: 2002041711
Back in the days I used to use Outlook Express (last week)I had a folder
named /. to house things that would come from a similarly named website.
Outlook Express named this folder ..dbx
Mozilla imported my mail with mostly lots of trouble and then finally got all
of it, however some folders were contained in the /. folder, which mozilla had
named '.' sans quotes.
Reproducible: Always
Steps to Reproduce:
1. Create folder in Outlook Express named '/.' sans quotes
2. Go delete Folders.dbx as mozilla can't seem to figure out how that works and
ends up skipping most of the folders if you don't
3. In mozilla, import mail from outlook express
Actual Results: Look at how mozilla threw a duplicate of every folder inside
the folder mozilla named '.'
Expected Results: It should not duplicate every folder.
The help page speaks of a Import module which I should report this as part of,
yet the page I use to report this bug with doesn't list that. One of these
needs to be changed.
Comment 1•23 years ago
|
||
changing component to import -> Cavin
Assignee: bienvenu → cavin
Component: Mail Database → Import
There are some existing bugs about folder names with certain characters causing
problems... one I found is 140212.
Updated•22 years ago
|
Blocks: folders-with-special-characters
Comment 3•20 years ago
|
||
I just checked in something that should fix this under Bug #219586
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.8alpha4
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•