TBird does not give a second chance to log in
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thunderbird (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: thunderbird
I have several email accounts that I have set up, at my company email. Email in these accounts are downloaded by IMAP over SSL, and the SMTP outgoing is using the "TLS-if-available" option.
Account1 is the default account. When I log on to TBird I type in the password and all is fine.
Account2 is another account. I typed in the wrong password, and then TBird showed me the list of folders under that account as Account2 -> Inbox -> Trash, and that is all. There are no messages in the inbox or anywhere else, and none of the expected folders appear. This is reasonable considering that I have not properly logged in.
What is not very reasonable is that I cannot fix the error, by just clicking "Get Mail" to encourage TB to prompt me for the account password again. Instead, it simply reports "There Are No New Messages On the Server" in the status bar. This isnt really true --- it has no idea if there are no new messages. It should at least be honest and say something like, you are not logged in so I cannot get new mail for you. And then it should allow me to log in properly.
INFO -------
fjones@core:~$ lsb_release -rd
Description: Ubuntu 8.04.2
Release: 8.04
fjones@core:~$
fjones@core:~$ apt-cache policy thunderbird
thunderbird:
Installed: 2.0.0.19+
Candidate: 2.0.0.19+
Version table:
*** 2.0.0.19+
500 http://
500 http://
100 /var/lib/
2.
500 http://
fjones@core:~$
ProblemType: Bug
Architecture: i386
Date: Fri Jan 23 17:52:14 2009
DistroRelease: Ubuntu 8.04
NonfreeKernelMo
Package: mozilla-thunderbird 2.0.0.19+
PackageArchitec
ProcEnviron:
PATH=/
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: thunderbird
Uname: Linux 2.6.24-23-generic i686
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.