Closed Bug 115312 Opened 23 years ago Closed 16 years ago

Account's top level folder corrupted with wrong online name

Categories

(MailNews Core :: Networking: IMAP, defect, P1)

x86
Windows NT
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
Future

People

(Reporter: scottputterman, Unassigned)

References

Details

I'm using the 12/13 build on Win NT 4.0 with an IMAP account.

I currently have my Inbox selected.
I bring up the new folder dialog
The current account is selected as the parent folder.
I type a folder name.

When I see the folder name in the folder list, I see:

mailnewsstaff^foldername.

mailnewsstaff is the name of one of my other folders which should be a sibling
of the new folder I'm creating.  I did this three times with 3 different names
with the same result.
Severity: normal → critical
Priority: -- → P1
I will take a look
Assignee: mscott → naving
I just tried this using 12/13 build and it works ok for me, both for acct
as parent and a folder as parent. Updating my build...



^ is the canonical imap hierarchy delimiter - the fact that we're not replacing
it with '/' means that we're confused about what the real hierarchy delimiter
is. It might just be your .msf file or panacea.dat, or it could be a general
problem. I don't know how we could get confused about what the parent folder is,
unless the js is confused.
This looks like a dup bug which I reported before....
this works fine on my 12/13 release build.
Here's some odd behavior.  I just downloaded today's build (12/14) and when it
started up, all of the folders were in the correct place for 1/2 a second and
then went back to the wrong place.
Changing the summary based on my understanding of what was happening. 
Regenerating the account's .msf file made this problem go away. When I looked at
the old one it appears that it's online name was "mailnewsstaff" which explains
the problem.  I dont know how it go that way or how to reproduce. So, I'm moving
this to the future milestone unless more people start reproducing this.
Status: NEW → ASSIGNED
Summary: New folders not being created in the correct place → Account's top level folder corrupted with wrong online name
Target Milestone: --- → Future
I found that there are two bugs related to this bug problem:

1)bug 29926: 2001-08-16 16:09 my comments:
>Now if I create the folder name with the slash. (e.g. karen1/karen2)
>On the UI, our client will create additional unknown subfolder "karen1^karen2".
>After exit and relaunch again, it will disappear. 

2)bug 98228: 2001-09-04 12:29 my comments:
>I saw this problem on Dawn's Linux system.
>But, Stephen & I couldn't reproduce this problem on our system.
>I notice Dawn is using an existing profile with multiple accounts......

>It seems that it's trying to create a subfolder under the Inbox & finally got 
>"INBOX^test" which is not correct and is a little bit similar to the scenarion 
>that I got on 8/16 of bug 29926.....

David, from above your 12-14 comments of this bug, do you think that this bug & 
bug 98228 should be dup of bug 29926 which dealing with Folders' names with "/" 
problem?
I am using 0.9.7 (Win32 Daily, 12/31/01) and can successfully create IMAP 
folders of name/name2 correctly.  I have multiple accounts, but a single IMAP 
account.  Of course, with WU-IMAP there is the slight problem that "name" is 
not a mailbox, but "name2" is; but that is an implementation detail.  I can 
make a subdirectory of INBOX, but this causes the same problems as the "name" 
directory.  With WU-IMAP I cannot make a parent directory an mailbox as well; 
could this be compounding the the problem that you are looking at or am I just 
explicating a different facet of the implementation problem?
Michael, I'm not sure. Are you able to reproduce the problem described in this
bug? I suspect what's going on in this bug is that we have some trouble parsing
folder names with '/' in them and end up writing the wrong online name into the
root account level db. What you're describing sounds more like a limitation of
the UW server in certain configurations.
QA Contact: huang → gchan
mass re-assign.
Assignee: naving → sspitzer
Status: ASSIGNED → NEW
Product: MailNews → Core
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Michael Semich no longer sees the problem. I've never seen it.
=> WFM
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.