Closed Bug 258861 Opened 20 years ago Closed 20 years ago

Creating a new Account - Default SMTP ServerNAME will be used

Categories

(Thunderbird :: Account Manager, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 222388

People

(Reporter: patrick, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040823 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040823 Firefox/0.9.3

When creating a new Account, the default SMTP Server will be used for this
account. Thats ok, but in the account server-settings (advanced) the smtp server
is not set as "always use default server" its just the name of the smtp-server.

Problem: When you have to change your SMTP Server (Accounts - SMTP), it didnt
work for the current POP3/IMAP Accounts. You have to change the SMTP Server in
every single POP3/IMAP4 Account (acounts-server-settings-advanced). 

Thats not very logical... i hope u know what i mean ;)


Reproducible: Always
Steps to Reproduce:
1. Change the (global) default SMTP Server


Actual Results:  
1. Non of the current accounts have the new default smtp set.

Expected Results:  
1. The current account should automaticaly set the new SMTP (in default)
You didn't state which version of TB you were using when you encountered this 
problem.  I have in fact seen the same thing with TB 0.7, but I just tried with 
TB 0.8 and did not get the duplicate entry, so I'm not sure what's going on.


*** This bug has been marked as a duplicate of 222388 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
OK, u are right! A TB 0.7 problem. sorry i forget the version number :-/
With 0.8 there is no problem (a new account have automatically set the default
SMTP).
(In reply to comment #2)
> With 0.8 there is no problem (a new account have automatically set the default
> SMTP).

Actually, I was mistaken when I tested earlier -- the symptom you're talking 
about is still present in TB 0.8, as I noted at the dupe.
You need to log in before you can comment on or make changes to this bug.