Closed Bug 144643 Opened 22 years ago Closed 20 years ago

SMTP login prompt for mail account which doesn't exist

Categories

(MailNews Core :: Networking: SMTP, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 90507
mozilla1.4beta

People

(Reporter: jeesun, Assigned: sspitzer)

References

Details

SMTP login prompt for mail account which doesn't exist
Build: 0512 PR1

Steps:
1. In a new user profile, add two mail accounts - I used accounts from messeging
server version. Make sure that the user names are different on these two
accounts. e.g. abc@first.com and xyz@second.com
2. Login (enter your password) to the first account, abc@first.com. Remember
that this server is default SMTP. Send a mail. You'll be prompted for password
again for the same account (don't know why). Anyway, you can send a msg successfully
3. Now, go to the second account, xyz@second.com. When you try to send a
message, you'll be prompted for another password. Notice that in that prompt,
the userid and server name combination is weird. It'll read "xyz@first.com".
Userid from the second account is mixed with SMTP servername. xyz@first.com is
not existing!

As a result, I can't send a msg from the second account.
varada's been looking into these account manager / smtp type bugs. 
Assignee: mscott → varada
change qa contact-> account manager related
QA Contact: sheelar → nbaca
Keywords: nsbeta1
It depends on which mail server you use for your default account (SMTP). Some
servers don't promt for password when sending out emails and the others do. When
it's not asking for your password, you can send out a msg. But the "from" field
of received mail will show non-existing account (mixture of userid of
non-default account (you sent a mail from here) + smtp server name)
Discussed in Mail News bug meeting.  Decided to make this bug [ADT2 RTM].
Keywords: nsbeta1nsbeta1+
Whiteboard: [ADT2 RTM]
Target Milestone: --- → mozilla1.0.1
Branch build 2002-06-04: WinMe
I have not reproduced the problem yet.

In a new profile I configured it using the following accounts and successfully
sent messages. The From entries always appeared correct. My understanding is
that these servers do not require SMTP authentication.
- qatest22 on nsmail-2
- qatest33 on nsmail-1

Jeesun, can you be more specific as to which servers you are connecting to? In
the Outgoing SMTP Server panel what settings are selected (i.e. Are you using
SSL Never, When Available or Always)?
I was able to reproduce the problem using ISPs which require SMTP authentication.

Steps to reproduce:
1. Add an account which requires a password when sending a message (SMTP
authentication) (i.e. abc@first.com)
2. Add another account (i.e. xyz@second.com)
3. Send a message from the 1st account, it prompts for a password (the dialog
appears due to SMTP authentication)and references abc@first.com which is
correct. In this case it sends the message successfully.
4. Send a message from the 2nd account and it prompts for a password

Actual Results: this is where the dialog displays xyz@first.com. It has the
correct User Name but the SMTP Server it references is wrong.

Expected Results: it should display xyz@second.com

I'm sure this problem occurs due to the design of adding an additional account.
When adding another POP/IMAP account the Account Wizard never prompts for
another SMTP Server so it uses the first account's SMTP Server when
authenticating, which obviously fails. 

Workaround: Try going into Edit|Mail/News Account Settings, selecting the
Outgoing SMTP Server panel, selecting the Advanced button to add the second SMTP
Server. After you have created the server now you need to associate it with the
correct account. In the Account Settings dialog select the second account's top
level (aka identity panel which displays Account Name, Email Address, Signatures
etc...). Click on the Advanced button and select the second SMTP Server. Now try
to send from the second account.


marking nsbeta1-.  We have a way to make this work by using the Advanced
settings.   This sounds like a usability problem and we'll have to look into
ways of solving this in the next release.
Keywords: nsbeta1+nsbeta1-
Target Milestone: mozilla1.0.1 → mozilla1.2alpha
Blocks: 157673
>This sounds like a usability problem and we'll have to look into
>ways of solving this in the next release.

As putterman said, we need to include this in the next release. Renominating.
Keywords: nsbeta1-nsbeta1
Not an international bug. Removed tracking number
No longer blocks: 157673
taking all of varada's bugs.
Assignee: varada → sspitzer
Changing the platform & os info
OS: Windows 2000 → All
Hardware: PC → All
Mail triage team: need info from Rafael.
Assignee: sspitzer → rebron
Whiteboard: [ADT2 RTM] → [need info]
"I'm sure this problem occurs due to the design of adding an additional account.
When adding another POP/IMAP account the Account Wizard never prompts for
another SMTP Server so it uses the first account's SMTP Server when
authenticating, which obviously fails."

I think that nbaca is correct.

recently I made a change (for webmail), so that if the first account we created
was webmail, we *would not* use the webmail smtp server as the smtp server for
the next accounts created.  the user would get the text box to specify the smtp
server.

we could make that the common case, but, if the user enters the same smtp
hostname as an existing smtp server, we just reuse it, to avoid duplicates.

comments?
Assignee: rebron → sspitzer
Whiteboard: [need info]
Target Milestone: mozilla1.2alpha → mozilla1.4beta
adt: nsbeta1-
Keywords: nsbeta1nsbeta1-
I have also encountered this bug.  When I initially installed 1.4beta I could
send mail (with no prompt for username/password from the SMTP server).  Then one
day our email server went down and when I brought mozilla mail back up (once
everything was working again) this login with the weird account name just
started showing up every time I try to sent an email. 

I do not have multiple profiles set up. Today I tried uninstalling 1.4beta and
installed the 1.4 release and I still can't send e-mail because of this bug.  I
uninstalled 1.4 and re-installed 1.3, which seems to work fine.

A friend of mine has also encountered the same problem.  He also does not have
multiple profiles set up.
Product: MailNews → Core
This bug is caused by duplicate SMTP entries.
(1) On first account definition
    (1-1) smtp1    (xyz@first.com) is defined
          smtp1 is set as defautlt SMTP 
    (1-2) account1 (xyz@first.com) is defined
          SMTP for this accout is set as "smtp1"
(2) On second account definition
    (2-1) smtp2    (xyz@first.com) is defined (=> Duplicate SMTP entry)
          (As you want to use xyz@first.com, supply xyz@first.com)
    (2-2) account2 (xyz@first.com) is defined
          SMTP for this accout is set as "smtp2"
(3) Set up SMTP correctly but only on "smtp1" entry.
(4) Use first account
    Successfull because properly setup'ed "smtp1" entry is used.
(5) Use first account
    Error/Password prompt because not-setup'ed-yet "smtp2" entry is used.

Problem of duplicate SMTP entry is already resolved by Bug 90507,
although manual recovery(consolidation of duplicated SMTP) is required. 
 (a) Delete "smtp2" entry
 (b) Change account2's SMTP choice to "smtp1" or "Always use default SMTP".

See next FAQ for multiple SMTP server use.
http://kb.mozillazine.org/Thunderbird_:_FAQs_:_Multiple_SMTP_Servers

Bug 222388 is for problem of "Always use defrault SMTP server" is not set on
account definition.
Bug 202468 is for difficulty in multiple SMTP use(unkind UI improvement.)

Anyway, closing as DUP of Bug 90507, since one problem per bug.

*** This bug has been marked as a duplicate of 90507 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
*** Bug 146704 has been marked as a duplicate of this bug. ***
*** Bug 162564 has been marked as a duplicate of this bug. ***
*** Bug 167259 has been marked as a duplicate of this bug. ***
*** Bug 187635 has been marked as a duplicate of this bug. ***
*** Bug 160813 has been marked as a duplicate of this bug. ***
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.