Closed Bug 286031 Opened 20 years ago Closed 4 years ago

If the SMTP server sends an error message, TB prompts for password but does not display the message itself

Categories

(Thunderbird :: Security, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tal, Assigned: mscott)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 1.0.3705) Build Identifier: TB 1.0 When TB is configured to "use name and password" for SMTP, if the mail server sends an error message, TB does not display the message; it just prompts for the password again. The SMTP server I'm using (012.net.il) often graylists target emails for 60 seconds on the first "send" attempt, so I have to re-send the mail after a minute. If SMTP is *not* configured to use name/password, TB pops up a dialog window with the message from the server. No problem here. If SMTP *is* configured to use name/password, however, the message is not displayed; just the password dialog box, which keeps popping up. (... and the password is not remembered, either -- even though it should be.) Reproducible: Always Steps to Reproduce: 1. Enable SMTP user/password usage. 2. Send a mail via a mail server that uses generates some error message even if a correct password is used (e.g., 012.net.il). 3. Enter correct username and password in popup window (optionally: check the "save password" checkbox). Actual Results: Password dialog box re-appears (password is not saved if the checkbox was used). User thinks an incorrect password was provided, and keeps retrying... Expected Results: 1. Display the exact error message text from the server. 2. Prompt for password (but retain the previous value as a default if "save password" was checked).
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
I've observed this using Thunderbird 12.0.1 on Fedora 16, talking to an smtp server that was powered down. I can provide extra information if desired in order to reproduce it. Contrary to the message immediately above, I lack permission to re-open it for your consideration: I'll send you email, just in case bugzilla doesn't... --dave
Reopening due to comment 3. Gerv
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: EXPIRED → ---
Component: General → Security

Nikolay does what is being said here make sense, and still exists?

Flags: needinfo?(shopik)

I'm pretty sure I've seen error messages displayed, and only re-promt password if password fails.

Flags: needinfo?(shopik)

WFM per comment 6.

Status: REOPENED → RESOLVED
Closed: 20 years ago4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.