No option to enter password after intitial IMAP Install/config

RESOLVED INCOMPLETE

Status

RESOLVED INCOMPLETE
14 years ago
10 years ago

People

(Reporter: ksnider, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

14 years ago
After an itital install of TB09 with no migration, setting up an imap account
using SSL (port 993) results in me never being asked for a password - instead,
I'm told "Password Failed".

Use secure auth is *disabled*. Server supports plain/login and is a simple UW
IMAP server (RHEL3).

Attached is the logfile from client -> server. Note I have *not* been prompted
for a password at this point:

Steps:
- New tarball install of TB09
- no existing .thunderbird directory, no migration
- create IMAP account
- set IMAP account to "Use SSL"
- Exit TB
- on startup, server tries to check mail on the new acct, does *not* prompt for
a password.
- Login fails (obviously).

I'm attaching the NSPR log.
(Reporter)

Comment 1

14 years ago
Created attachment 166082 [details]
NSPR log of phantom auth
QA Contact: general
Assignee: mscott → nobody

Comment 2

10 years ago
Do you see problem using thunderbird 2? Or, better yet, Thunderbird 3 beta 2**?

If you do, please comment.
If you do not, please close the bug with resolution WORKSFORME (or some appropriate resolution, but not FIXED)

** Beta 2 has big fix of Bug 239131 Thunderbird should use the new password manager
http://www.mozillamessaging.com/en-US/thunderbird/early_releases/
(suggest you backup your profile before using beta release)
Component: General → Security
QA Contact: general → thunderbird
No response from reporter - I think if this was really still a problem we'd be seeing many more bug reports/duplicates about it (and the new account wizard dialog would probably have caught it as well).

Therefore marking incomplete as we don't have enough info about this bug to make another resolution.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.