262402 - Import of Communicator 4.76 local mail folders fails

Status: RESOLVED EXPIRED

(MailNews Core :: Database, defect)

Description

[richie]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7.3) Gecko/20040920

The import of Communicator 4.76 local mail folders fails and does not enable 
access to nested sub-folders.
Local mail folders are stored on a shared Unix network drive, cross mounted to 
my Solaris workstation. The mapped mail directory can be accessed, by setting 
the Local Folders preference. The email files within this directory can be used 
sucessfully but the email files within folders cannot be used, even though they 
are visible. Any further nesting of folders is not even visible. Note that the 
mail folders which contained sub folders are Unix directories and had no emails 
within them. 

Reproducible: Always
Steps to Reproduce:
1.Use Comunicator 4.76 to create local mail folders with nested sub folders, up 
to 3 levels deep.
2.Save emails to folders in all levels (but not in the folders containing sub-
folders)
3.Close Communicator and start Mozilla, configure to access the local folders 
on the Unix drive.
4. Import the Communicator 4.76 mail folders.

Actual Results:  
The first 2 levels of nested folders are visible but the sub-folders cannot be 
read.
Following the import of Communicator 4.76 mail folders the new folders created 
do not include the missing or inaccessible folders.

Expected Results:  
Access to local folders with nested email folders should work as for other 
first level folders.
The import command should convert the whole local folders nested tree structure 
to the mozilla compatible email format.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.