189151 - SMTP authentication uses wrong username if different from POP3 Username

Status: RESOLVED FIXED

(MailNews Core :: Networking: SMTP, defect)

Description

[Tim Lee]

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.22; Mac_PowerPC)
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.2.1) Gecko/20021130

Mozilla appears to ignore the SMTP authentication username in at least some cases. 
Specifically, if there is one POP3 email account and a message is sent from that address, 
Mozilla will attempt to authenticate with the username of the POP3 account, rather than 
the username specified in the SMTP configuration. This has been tested under Windows 
98 and Mac OS X with identical results.

Reproducible: Always

Steps to Reproduce:
1. From a fresh Mozilla build, create a new POP3 email account.
2. Under "Mail and Newsgroup Settings", choose "Outgoing Server (SMTP)". Change the 
SMTP server to a server that requires a username different from the username used to 
authenticate POP3.
3. Check "Use name and Password" and enter the username for SMTP authentication, 
which should be different from the POP3 username. In my case I had SSL set to "always," 
although I suspect this isn't relevant.
4. Create a new message and send it. 

Actual Results:  
Mozilla will say "enter password for [e-mail]." However, the username will 
*not* be the SMTP username entered above. It will be the POP3 username.

Expected Results:  
Mozilla should have used the SMTP username.

This was tried on Mac OS X and on Windows 98. It's reasonable to expect similar 
behavior on other platforms.

Comment 1

[Christian Eyrich]

Can't confirm this with 20030412 on Linux.

Comment 2

[WADA:World Anti-bad-Duping Agency]

This is password prompt message problem.
When user name=<username> and server name=<server.name>,
old Mozilla asked with "<username>@<server.name>"
instead of "<username> at <server.name>".
Because of this, if username contains "@", eg. <username>@<mail.domain.name>, 
message became "<username>@<mail.domain.name>@<server.name>"
instead of "<username>@<mail.domain.name> at <server.name>.
What a good message!

This problem on SMTP was finaly resolved by Bug 235246.
Closing as FIXED, with putting Bug 235246 in "Depends on:".
(Needless to say, POP3 also had similar problem :-) and fixed by other bug(s).)