Closed Bug 131013 Opened 22 years ago Closed 20 years ago

Import folders from Outlook containing hash sign (#) or slash (/) results in error ["cannot create proxy objec"]

Categories

(MailNews Core :: Backend, defect)

Product:
MailNews Core
Component:
Backend
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
mozilla1.8alpha4

People

(Reporter: vhou, Assigned: cavin)

References

(Blocks 1 open bug)

Details

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461)
BuildID:    2002031104

I receive a could not create proxy folder error when attempting to import 
folders that contain non-alphanumeric characters (#,/,etc).  The cause appears 
to be the inability to create the temporary folders required during import for 
these folders due to restrictions on the Windows operating system for folder 
names.

Reproducible: Always
Steps to Reproduce:
1. Create folder in Outlook with / or # sign (or any sign not allowed by the 
Win32 filesystem)
2. Attempt to import Outlook folders from Mozilla
3. Observe proxy error.

Actual Results:  Error displayed.

Expected Results:  Import should have succeeded.

Since Mozilla stores folders as files, files cannot contain symbols restricted 
by the Win32 filesystem.  This may or may not be an advantage for the mailer, 
though it may affect folders that use irregular symbols.

A workaround is to rename the folders to remove these characters before 
importing.
-> Cavin, looks like an import problem.
Assignee: bienvenu → cavin
Component: Mail Database → Mail Back End
QA Contact: esther → nbaca
*** Bug 143482 has been marked as a duplicate of this bug. ***
from bug 143482 comment 1, by cavin@netscape.com:

"There are a few bugs related to not being able to create local folders with
special chars (for example, bug 120559) and we'll have to deal with them all at
the same time. So it's a general folder creation problem and not caused by the
import code."
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 180315 has been marked as a duplicate of this bug. ***
*** Bug 176589 has been marked as a duplicate of this bug. ***
Blocks: folders-with-special-characters
Summary: Import folders from Outlook containing hash sign (#) or slash (/) results in error → Import folders from Outlook containing hash sign (#) or slash (/) results in error ["cannot create proxy objec"]
*** Bug 127486 has been marked as a duplicate of this bug. ***
*** Bug 198921 has been marked as a duplicate of this bug. ***
*** Bug 203530 has been marked as a duplicate of this bug. ***
*** Bug 210971 has been marked as a duplicate of this bug. ***
*** Bug 216410 has been marked as a duplicate of this bug. ***
Please also see description under bug 216410 (marked as duplicate). That bug 
complains that it takes several minutes to fail. The failure could/should be 
detected immediately.
*** Bug 207651 has been marked as a duplicate of this bug. ***
*** Bug 218875 has been marked as a duplicate of this bug. ***
*** Bug 242875 has been marked as a duplicate of this bug. ***
Additional observations: 
Observed in w95, w98, XP, with Mozilla 1.6 and spiffy new Thunderbird 0.6.

My folder had a pound (#) in the name, and the actual import was successful. 
(showed 80 messages imported) However, selecting the imported folder resulting
in the hourglass appearing, but no further activity would ever occur until I
selected another box.  I got no error message of any kind... just the hourglass.
 I think this is inappropriate behaviour.

Renaming the imported box caused the index to be built immediately, and all was
good again.

This caused a showstopper for me trying to convert someone away from OE. 
I think it should be notched up in severity.

*** Bug 251981 has been marked as a duplicate of this bug. ***
I just checked in something for Bug #219586 which should fix this
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.8alpha4
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.