385668 - profile migration creates two copies of IMAP folders with spaces in the names

Status: NEW

(SeaMonkey :: Startup & Profiles, defect)

Description

[Nelson Bolyard (seldom reads bugmail)]

Gecko/2007062001 SeaMonkey/2.0a1pre

I migrated from SM 1.5a to SM 2.0a1 using this build.

My IMAPS account has folders within folders.  Many of my top level folders
have spaces in the names, e.g. "ABC Aliases", "ABC Colleagues".

The migrator caused all of the top level folders with spaces in the names
to be copied twice, once with a space in the name, and once with %20 in the 
name, e.g. "ABC Aliases" and "ABC%20Aliases".   

The contents of these duplicated high level folders are identical.  
It appears that SM simply has two names for each higher level folder,
and the same underlying contents are reached by either name.

This bug requests that the migrator be fixed to not do that.
And it is also a request for support.  How do I get rid of the 
unwanted top level pseudo-folders with the %20 in the names, without 
losing any of the contents?

Comment 1

[Nelson Bolyard (seldom reads bugmail)]

One of my old top-level folders was named "XXX Dead Folders".
After the migration, I expected to find these two directory entries:
XXX Dead Folders.msf
XXX Dead Folders.sbd

But I actually found these four:
XXX Dead Folders-1.msf
XXX Dead Folders.msf
XXX Dead Folders.sbd
XXX%20Dead%20Folders.msf

Likewise, for "ABC Colleagues" I found:
ABC Colleagues-1.msf
ABC Colleagues.msf
ABC Colleagues.sbd
ABC%20Colleagues.msf

After seeing new top level folders with the names ABC%20Colleagues
and XXX%20Dead%20Folders, I had expected to find XXX%20Dead%20Folders.sbd 
and ABC%20Colleagues.sbd subdirectories.  But those directories did not
exist.

While SM was not running, I deleted all the *-1.msf and *%20*.msf files.
Then when I restarted SM, things appeared to be normal again.

Comment 2

[Andrew Schultz]

I was unable to reproduce this on linux... I created a top-level folder in my IMAP with a space in it.  I created a test profile with 1.1.7, set up the IMAP account in that profile and then migrated the profile.  The folder was migrated successfully by a current trunk build.  I also tried a trunk build from 2007-06-24 and that also migrated the folder successfully.

I suspect there's some other ingredient needed to reproduce that I'm missing.  Nelson, can you try to see if you still this problem (you'll need to create a new trunk profile and then invoke a trunk build with "-P newProfileName -migration -no-remote").  And perhaps try creating a 1.1.7 profile that just has the IMAP account and try migrating that profile.

Comment 3

[Ian Neal]

Nelson, could you test to see if this still happens on a recently nightly? TIA
Denying a1 blocking for the moment.

Comment 4

[Nelson Bolyard (seldom reads bugmail)]

Ian, I kept a copy of my old unmigrated profile around for months, in case
someone tried to fix something and asked me to try again.  But after a 
while, I removed the old profile.  So I have no old profile with which to
try this migration again.  I run nothing but the trunk, all the time, for 
years now.