Closed Bug 312239 Opened 19 years ago Closed 15 years ago

Bad password behavior with MS Exchange IMAP causes lockout

Categories

(Thunderbird :: Security, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 182362

People

(Reporter: dunn5557, Unassigned)

Details

I encountered a fairly ugly experience with TBird. I use TBird to connect to my
company MS Exchange server which is linked to the domain access and password.
Recently I was forced to change my domain password and as result my exchange
password changed.

However, Thunderbird attempted to contact the exchange server numerous times
(Using the old cached password). This resulted in my corporate account being
locked out due to multiple failed login attempts. <Bummer>

At no time did Thunderbird offer to change my password or account login relative
to that IMAP account. And I had to dig fairly deeply in the FAQ to learn how to
delete the stored password.
Summary: Bad passwd behavior with MS Exchange IMAP causes lockout → Bad password behavior with MS Exchange IMAP causes lockout
At my company we are seeing the exact same behaviour: Our Active Directory allows three login attempts, then locks the acount. When a password is changed, Thunderbird will keep trying to login using various methods. It does 4 attempts apperently. Obviously this will fail and the Active Directory account is locked.

This behaviour happens in Thunderbird 1.5.0.4 on Windows XP.
do you see this in v2?
Assignee: mscott → nobody
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
I am not in a position to verify or close this bug. I can not break or modify my production exchange account. The TB QA team should be in best position to verify and close provided they have an exchange test acct to tinker with.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.