Closed
Bug 119900
Opened 23 years ago
Closed 22 years ago
Mozilla will not allow duplicate same outgoing mail server's
Categories
(SeaMonkey :: MailNews: Account Configuration, enhancement)
Tracking
(Not tracked)
People
(Reporter: akumapwr, Assigned: racham)
Details
Attachments
(3 files, 2 obsolete files)
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901
BuildID: 2001090111
I use gmx.net for email.
I have two different accounts, one bob@gmx.net, other john@gmx.net
Both need to auth to send mail, with there own username. They use the same
outgoing mail server (which seems to be the problem)
Bug:
Edit -> Mail/News account settings
edit outgoing server (SMTP)
add
mail.gmx.net
bob@gmx.net
ssh when avilable
default:
mail.gmx.net
john@gmx.net
ssh when avilable
Select an account -> Advanced -> Select drop down
Now, when you try to select the entries to assign them in accounts. You get
blank white spaces, and only the default mail server comes up. This ONLY happens
if you use the SAME out going mail server name. ie. mail.gmx.net
Reproducible: Always
Steps to Reproduce:
Edit -> Mail/News account settings
edit outgoing server (SMTP)
add
mail.gmx.net
bob@gmx.net
ssh when avilable
default:
mail.gmx.net
john@gmx.net
ssh when avilable
make two different email accounts, try to assign these to each. John to John,
Bob to Bob.. Only the default will come up.
Actual Results: Only the default comes up.
Expected Results: Both servers listed.
a. i've never met ssh when available. you probably mean ssl.
b. i thought that the outbound mail server was just a server and not a username+server
c. as a workaround (and i have needed to do this for inbound) you can find a second dns/ip entry that resolves to the same computer. [currently: 213.165.64.20]
Severity: major → enhancement
Comment 3•23 years ago
|
||
I've similar problem with my windows box (XP Pro) and Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US; rv:1.0rc1) Gecko/20020417
I have 2 account (same username, different domain) with 2 (different) mail
server and smtp auth is needed for sending mail....
if I add 2 mail server in mail configuration (setting up the correct
authentication for both account) I have the same problem...
Select an account -> Advanced -> Select drop down
I can see only default mail server and some blank white spaces
Comment 4•23 years ago
|
||
Attach 1/2
Comment 5•23 years ago
|
||
Cannot select mail servers
Attach 2/2
wfm linux build 2002072704.
akumapwr@gmx.net: can you try a recent nightly build and see if you still can
reproduce it?
Comment 7•22 years ago
|
||
I've tried with Build 2002072818 and this bug is still present...
I've created 2 new attach with screenshot
Comment 8•22 years ago
|
||
Attachment #81650 -
Attachment is obsolete: true
Comment 9•22 years ago
|
||
Attachment #81651 -
Attachment is obsolete: true
Comment 10•22 years ago
|
||
Also with latest build on my (Suse) linux box (with kde 2.2)
Comment 11•22 years ago
|
||
Comment 12•22 years ago
|
||
If this is still happening with 1.1 or later, why is this not a dupe of bug 41929?
pi
Comment 13•22 years ago
|
||
So....here comes my first bug report....I am not not very experienced but still:
Here you are.
First of all my system's configuration: I am using mozilla 1.1 on a Windows XP
Professional system, but I have "experienced" ;-) this problem on Windows 98,
too. I have also had this problem with the outgoing servers with some older
releases (p.ex.: 1.0, 0.98 etc.).
I have several mail accounts of "GMX" and "WEB.DE" being managed by one mozilla
account.
THE BUG:
The dialog "Advanced Account Settings" contains empty entries, even though I
have entered 5 outgoing servers in the dialog on the screen shot 2. I don't
know, why this happens, but it really sucks.
Chris
Comment 14•22 years ago
|
||
Comment 15•22 years ago
|
||
I think this is best dealt with in bug 41929.
pi
*** This bug has been marked as a duplicate of 41929 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•