Closed
Bug 208806
Opened 23 years ago
Closed 22 years ago
changes to SMTP default server not recognized
Categories
(MailNews Core :: Networking: SMTP, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 202308
People
(Reporter: scott.mattoon, Assigned: sspitzer)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030529
from "Mail & New Account Settings -> Outgoing Server (SMTP) -> Advanced ..." if
I select a different server on the list as the Default, the previous server is
still used to send new email. restarting mozilla, and restarting windows does
not solve the problem. My workaround was to delete the previous server from the
list (even though it was no longer marked Default, and readd the desired server
then set it as Default.
Reproducible: Always
Steps to Reproduce:
1. Mail & New Account Settings -> Outgoing Server (SMTP) -> Advanced ...
2. select a different server on the list as the Default
3. restart windows.
4. send email and track which server is used to deliver
Actual Results:
Since I was behind a firewall that filters SMTP, I had to switch to an SMTP
server inside my firewall. when I made the switch following the steps, then
clicked sent email, Mozilla responded with <server name> cannot be reached,
where <server name> was the previous default, and not the current default SMPT
server.
Expected Results:
use the new default SMTP server.
this appears to be a regression, as the problem did not occur in 1.4b.
Comment 1•23 years ago
|
||
Yes, I have same problem on Linux, Mozilla 1.4 RC2
I second this behavior. Using Ethereal, I see this behavior with both Mozilla
1.4 and Thunderbird 0.1.
rp03
I forgot to mention that restarting Mozilla 1.4 or Thunderbird 0.1 does not
affect the outcome. The GUI still shows the new default, but outgoing messages
still go to the old SMTP server.
This bug appears to be a dupe of bug 202308 - Outgoing Server (SMTP) swictching
is not functioning properly.
Comment 6•22 years ago
|
||
It's a dupe.
*** This bug has been marked as a duplicate of 202308 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•