Closed Bug 225606 Opened 22 years ago Closed 20 years ago

SMTP settings of removed mail account are used after account is removed instead of correct one

Categories

(Thunderbird :: Account Manager, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: maksf, Assigned: mscott)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Build Identifier: Mozilla Thunderbird 0.3 (20031013) I've added two accounts: foo@bar.com and foo2@bar.com Then I've removed foo@bar.com When trying to send mail via foo2 account, client was trying to send it via foo@bar.com ( what caused server error, foo couldn't send it as foo2 ). In prefs.js I've discovered following line: user_pref("mail.smtpserver.smtp1.username", "foo"); after changing it to: user_pref("mail.smtpserver.smtp1.username", "foo2"); Reproducible: Always Steps to Reproduce: 1.Add two accounts: foo@bar.com and foo2@bar.com 2.Removed foo@bar.com 3.Try to send mail via foo2. Actual Results: As desribed Expected Results: use proper settings
In the "Advanced Outgoing Sever (SMTP) Settings" dialogue box, NO matter which SMTP server is set default, always the first/top SMTP server in the list is used. Fail as a different ISP is used.
Note that SMTP server is a property of the identity, not the account; and the SMTP server pool is maintained separately from the accounts. Deleting an outgoing mail account doesn't delete the associated SMTP server; and when a new account is created, it defaults to using whichever server has been selected as default (but *not* "Use Default Server" -- bug 222388). When an SMTP server is deleted, any identity which uses it is reset to use (again) whichever server has been selected as default. So, deleting an account implies having to separately delete the SMTP server, if that's necessary; that's a bit of a drag, but 222388 and/or bug 170520 will make that less of a problem. With the new UI for SMTP management (Moz 1.8/Seamonkey 1.0/TB 1.5) it is much easier to see what's going on, and to figure out how to fix the settings, which were inscrutable before.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.