I've done this before. I had to change the POP server and I managed to
do it by changing the prefs.js file and the directory structure. The was
I did it then (about 3-4 months ago) was to change all places where
'pop.oldserver' was written to 'pop.newserver' in the prefs.js file. I
then changed the name of the folder in Mail directory from pop.oldserver
to pop.newserver. That worked for me.
Looking at the prefs.js file, I think you should be able to get away
with just changing the following line.
user_pref("mail.server.serverx.hostname", "pop.oldserver");
to
user_pref("mail.server.serverx.hostname", "pop.newserver");
- Pratik.
DISCLAIMER - Not responsible if doing the above makes your account
unusable or deletes all your mails or crashes Mozilla, etc. etc.
Steve wrote:
> I was reading the bug thread on this one, and I think the gist of the
> conversation between the Mozilla folks was that it would require some
> solid rework on that and related components while not being that big of
> a deal for the user to get around (by creating a new account.)
>
> From a user interface issue, particularly for newcomers, this leaves a
> bad taste in my mouth. I don't know what other email program would
> require you to do something similar. But by the same token, I can
> understand why it won't get high priority vs. the others. I'd gladly
> trade a speed increase for it, for instance.
>
> Steve
>
> In article <[EMAIL PROTECTED]>, Thomas
> <[EMAIL PROTECTED]> wrote:
>
>
>> nospam@nospam wrote:
>
>
>> it's a bug, I think you have to create a new account.