Fails to update account settings when mail server name changed

RESOLVED EXPIRED

Status

Thunderbird
Preferences
RESOLVED EXPIRED
13 years ago
12 years ago

People

(Reporter: John Olsson, Assigned: Scott MacGregor)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

At work we have switched IMAP mail servers (name of mail servers) and thus I
needed to update my mail account settings to reflect the changes. I just
replaced the "Server Name" setting, got a warning message and then everything
seemed to work as it should. Until I tried to send a mail. When Thunderbird
comes to the phase where it copies the sent mail to the Sent folder on the mail
server it just hangs. I can press "Cancel" and close the mail edit window
(confirming that the mail was not sent properly). This happended *every* time.

Today it struck me that it might be interesting to verify that the account
settings in Thunderbirds prefs.js file were correct. They were not. Just the
mail server name had been changed, but the paths to the Sent, Draft and Template
folders still had the old mail server name in them!

Once I replaced the old mail server name by hand in the prefs.js file (for all
relevant configuration options) to the new mail server name everything worked as
a charm again. :)

Reproducible: Always

Steps to Reproduce:
1. Create an IMAP mail account on mail server
2. Rename the mail server (e.g. from foo.bar.com to gazonk.bar.com)
3. Update account settings to reflect the name change

Actual Results:  
Thunderbird fails to copy sent mail to Sent folder on mail server.

Expected Results:  
All relevant configuration settings should have been updated automatically to
reflect the change of mail server name.
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.