Closed Bug 1464047 Opened 7 years ago Closed 2 years ago

After renaming an IMAP server, notifications use the old server name

Categories

(Thunderbird :: General, defect)

Product:
Thunderbird
Component:
General
Version:
52 Branch
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: psychonaut, Unassigned)

Details

Once upon a time I set up an account called Foobar in Thunderbird to use the IMAP server mail.example.com. Later the IMAP server got moved to a different domain, post.beispiel.de. So I went to Edit->Account Settings->Foobar->Server Settings->Server Name and changed the value from "mail.example.com" to "post.beispiel.de". Everything has been working fine since then, except that now, years later, Thunderbird's notifications still refer to the server name as mail.example.com. For example, if Foobar's server goes down, the message "Connection to server mail.example.com timed out." appears as a notification and in the Activity Log when Thunderbird tries to check mail.
Yes, there is this confusing stuff about "server name" and "real server name". Check in the preferences for hostname and realhostname. See bug 1414607 comment #2. The quick fix would be to change the offending value in one of the preferences.
I've just noticed that the problem is not limited to notifications. The old server name also appears in printed messages if the "URL" field is selected for the header and/or footer.
And I believe in the internal URL when you inspect the folder properties, no? See bug 1483485. We're looking into cleaning up this mess one day, see bug 1414607.

With Thunderbird 78.4.0, the old server name also appears in the Location field of the Add Security Exception dialog (when attempting to connect to a server whose certificate is self-signed, expired, invalid, etc.). I don't remember this particular manifestation of the problem occurring in previous versions of Thunderbird; in fact, I'm pretty sure that the Location field was always populated with the real server hostname. Perhaps this is related to Bug 1590474.

Severity: normal → S3

No longer reproducible with Thunderbird 115.2.0.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.