238584 - incorrect error message with 1.7b Mac OS X regarding secure authentication on startup

Status: RESOLVED EXPIRED

(MailNews Core :: Security, defect)

Description

[David Escalante]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7b) Gecko/20040316

I've used Mozilla on various platforms since 0.89 -- first time I've seen this
one.  On my Mac, when I start Mozilla I get a dialog that says: "You canot log
in to mail.bc.edu because you have enabled secure authentication and this server
does not support it.  To log in, turn off secure authentication for this
account."  When I click "OK", it logs me in anyway and everything appears to
work fine.  We only encourage secure authentication, don't enforce it, so I'm
not sure if there's a problem where it's failing then dropping back to insecure
automatically, or if the message is being displayed erroneously.  In either
case, the dialog box text is deceptive.

Reproducible: Always
Steps to Reproduce:
1. Start Mozilla, opening Mail & News on startup automatically
2. Have secure authentication turned on in preferences for the default account
3. Go after an IMAP server
Actual Results:  
See "details"

Expected Results:  
Either not report the message if it's wrong, or if it is failing back to no
authentication, state that.

I have a screen shot of the dialog if needed.

Comment 1

[David Escalante]

Attachment: screenshot in TIFF of dialog

Comment 2

[mozilla-bugzilla]

(In reply to comment #1)
> Created an attachment (id=144710)
> screenshot in TIFF of dialog
> 

I can confirm this bug, and am also able to reproduce it on demand.

Using OSX 10.3.4, with same version of Mozilla.

Comment 3

[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 4

[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.