151314 - prompts for a password for a user that doesn't exist by stripping email address-style username

Status: RESOLVED EXPIRED

(MailNews Core :: Networking: SMTP, defect)

Description

[Steven Hasty]

User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.0) Gecko/20020530
BuildID:    2002053012

My username for my SMTP server IS my e-mail address.
I correctly set this in the "Server Settings" tab of Mail and Newsgroup Account
Settings.
When I download new messages (for the first time) it prompted for the password
to [e-mail]@myserver:port and I entered it (with some
difficulty, the only was to focus on the text box was to check the 'remember my
password' checkbox).
Alternately, when I tried to send e-mail from the same account, it prompted me
for the password for the username 'myhost@myserver:port', which is not my
username. I'm guessing it parsed the username and found that it contained
invalid (?) characters (the @) and thus returned my username as 'myhost'.

Reproducible: Always
Steps to Reproduce:
1.Create a new mail account
2.in News and Mail account settings, set the username to a valid e-mail address
3.compose a new message and try to send it

Actual Results:  When I tried to send e-mail from the same account, it prompted
me for the password for the username 'myhost@myserver:port', which is not my
username. I'm guessing it parsed the username and found that it contained
invalid (?) characters (the @) and thus returned my username as 'myhost'.

Expected Results:  It should have returned a prompt for password for the
username '[e-mail]@myserver:port'.

Modern/Classical themes both have this issue.
I'd like to see an option for storing my password in the Mail & News account
settings > server settings to preclude this entire event.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.