269070 - Get Mail button not working

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

[Geoff Partridge]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

Using latest build of thunderbird 0.9, with one pop3 account working, the "get
mail" button does nothing on click.  Have reproduced this on fresh built XP Pro
SP2 PC with thunderbird 0.9

Reproducible: Always
Steps to Reproduce:
1. Open Thunderbird
2. Click "Get Mail"
3. Nothing Happens

Actual Results:  
No function for this button.

Expected Results:  
initiated a pop3 connection to an email server.

Comment 1

[Marius Scurtescu]

This seems to be similar to 261096.

Comment 2

[Janice]

The last two times I logged on I got no notice, for the first time ever, that I
had no new mail; I clicked the "Get Mail" button and nothing happened.  I tried
to send myself an email and the program seemed unable to connect to my pop3
account, although it was already open as I was browsing Firefox.  I am not a
programmer - just a user - so if the answer isn't really simple I'll have a lot
of trouble understanding instructions; also, as I can't receive new mail, how do
I get your advice?

Comment 3

[Joshua Cranmer [:jcranmer]]

Does this problem still manifest itself with 2.0.0.* or recent Trunk builds? If no response within 3 weeks, I will close this bug as RESO INCO.

Comment 4

[Joanne Moore]

I am having the same problem.  This morning when I opened TB it would not connect.  When I checked my email online at verizon.net there were 51 messages.

I tried again this afternoon with the same result.

Comment 5

[Joshua Cranmer [:jcranmer]]

(In reply to comment #4)
> This morning when I opened TB it would not connect.

Could you elaborate on this? It sounds like a separate issue altogether...

Comment 6

[Joshua Cranmer [:jcranmer]]

RESO INCO per lack of answer to previous question. If you feel this change was made in error, please respond to this bug with your reasons why.