109260 - Path to mail folders doesn't match path to user profile on network drive

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Manfred Lebek]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.5) Gecko/20011011
BuildID:    2001101117

I mapped a network drive where i placed a Mozilla user-profile. To use this
profile with Mozilla i started the profile manager, set the directory to store
the profile to the directory on my mapped drive like in Communicator 4.x. After
restart, all mail folders are empty until i change the wrong path in the account
settings(local directory) to the path to the user profile on the network drive.

Reproducible: Always
Steps to Reproduce:
1. map network drive with Mozilla user profile
2. In profile-manager, select "create profile"
3. choose the path to the folder on the network drive
4. restart Mozilla 

Actual Results:  there are no folders in the mail-accounts

Expected Results:  Mozilla should change the pathes to the network drive

Comment 1

[Harald Glatt]

do you see the folders but they are empty? there is a inbox folder for every pop
server you are using... are they all there but empty? i have a simmilar problem
but it appears to me that the mails are found because i can scroll the inbox
listbox... and i can scroll about the amount of mails i got... but i can't see
anything and can't click anything so i think the mail inbox listbox and/or quick
preview are broken...

Comment 2

[Dimitrios]

When you create a new profile and define its path, Mozilla doesn't use any files
that might already exist in this path. It can only migrate from other profiles.
Assuming you copy a Mail directory to another drive/path. The folder contains
two subdirectories:
a) Local Files, b) MyPopServer (example)
The second subdirectory contains the existing email database that you want to be
visible from the new profile. Now create the new profile pointing to the new
path of Mail dir. Then you run Mail client and enter the account wizard. You
provide the pop (incoming) server name, i.e. MyPopServer, and you suppose that
you will be able to see the old messages. But no, what actually Mozilla does is
that it creates in $path\..\Mail directory a new subdirectory named
MyPopServer-1. Until you edit server settings on Mozilla or copy MyPopServer
contents to MyPopServer-1, old messages won't be used.

I think current Mozilla behaviour (i.e. wizard always create a new pop3
directory) is correct, so this bug is invalid. A lot of problems might arise if
a new profile could overwrite an existing mail directory. An importing tool is
what we need for copying a message database to another profile.

And the component is Mail&News->Account Manager, isn't it?

Comment 3

[Dimitrios]

Over to MailNews->Account Manager. As far as I can understand this bug, reporter
wants to create a new profile that will use an existing mail database without
moving files from the old path to the new one (network mapping is irrelevant).
Our current workaround is simple and safe for any power user: create the
profile, then copy here the old mail database.

Changing status to NEW. I would prefer marking it WONTFIX but I don't think I am
qualified for this.

Comment 4

[racham]

What are the wrong path values you see in the prefs file..? Are they pointing to
a default profile path..?

Comment 5

[Moritz Balz]

Seems to me it's the same or a similar problem as discussed in bug 12911:
"Use relative pathnames for profile directories and profile-relative data"
-> comment #43

http://bugzilla.mozilla.org/show_bug.cgi?id=12911

Comment 6

[Manfred Lebek]

ok, i try to explain it once again:
assuming my user profile resides on U:\Mozilla\[e-mail]\
and i create a new email account.
after creation the new account resides on 
D:\WIN\Mozilla\Profiles\[e-mail]\bk0tpspl.slt\Mail\pop.test.de.
that means i have to copy the account files every time i created a new email or
news account to a subfolder of my profile. my question is, why mozilla doesnt
create new email accounts in the profile folder. 
i think this happens after experimenting with profiles. 

Comment 7

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 8

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 9

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 10

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420