Closed Bug 247372 Opened 21 years ago Closed 21 years ago

change of default outcoing SMTP server does not take effect for send message thereafter

Categories

(MailNews Core :: Networking: SMTP, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 170089

People

(Reporter: liebich, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040608 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040608 When I change the default outcoing SMTP server (mail&news account settings -> Outcoing server (SMPT) -> advanced ... then "set default" to a different smpt server in the list of server), if does not take effect to a later "sent now" or "sent unsent message" - it still contacts the previously selected SMTP server. Also closing mail&news or exit mozilla and restart does not change it. I used this procedure regularly and had no problems since Mozilla 1.6 (so it appears to be a new problem in 1.7 (using RC3 now). Only way to overcome the problem was to delete the previous SMTP server from the list, then the new default SMTP server is accepted. Reproducible: Always Steps to Reproduce: 1. change the outcoing SMTP server (need to have at least two previously defined) 2. send a message (send now or send unsent messages) 3. message bar shows that still the previously SMPT server is contacted Actual Results: mail sent via the "old" default SMTP server Expected Results: mail sent via the "new" default SMTP server
Sure the SMTP server in Mail&News Account Settings -> Server Settings -> Advanced ... is set to "Always use default server" rather than a particular one?
no it wasn't - a specific smtp server was set - however I did never made this setting, so it should be (by default), set to "always use default server", when upgrading to 1.7 ?
*** This bug has been marked as a duplicate of 170089 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.