Closed Bug 284137 Opened 20 years ago Closed 19 years ago

TB does not download messages from POP3 Server

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: frank.bolander, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050223 Firefox/1.0.1

TB does not download POP3 messages although it detects new messages on the
server. A status message of Receiving: Message 1 of XXXX occurs but then
disappears without downloading messages. I have included a session trace.

Reproducible: Always

Steps to Reproduce:
1. Click Get Mail
2.
3.

Actual Results:  
A status message of Receiving: Message 1 of XXXX occurs but then disappears
without downloading messages. 

Expected Results:  
Retrieve POP3 email messages.

I have tried TB 0.9,TB 1.0 with/without Antivirus on Windows and on Linux with
same results. Outlook Express on same XP machine downloads messages with no
problem. 


0[274860]: SEND: UIDL

0[274860]: Entering NET_ProcessPop3 33
0[274860]: POP3: Entering state: 3
0[274860]: RECV: +OK 71 messages (314122 octets)
0[274860]: POP3: Entering state: 12
0[274860]: Entering NET_ProcessPop3 483
0[274860]: POP3: Entering state: 12
0[274860]: RECV: 1 2
0[274860]: POP3: Entering state: 12
0[274860]: RECV: 2 3
0[274860]: POP3: Entering state: 12
0[274860]: RECV: 3 4
0[274860]: POP3: Entering state: 12

...

0[274860]: RECV: 70 71
0[274860]: POP3: Entering state: 12
0[274860]: RECV: 71 72
0[274860]: POP3: Entering state: 12
0[274860]: RECV: .
0[274860]: POP3: Entering state: 15
0[274860]: POP3: Entering state: 18
0[274860]: SEND: RETR 1

0[274860]: Entering NET_ProcessPop3 17
0[274860]: POP3: Entering state: 3
0[274860]: RECV: +OK 6087 octets
0[274860]: POP3: Entering state: 19
0[274860]: Opening message stream: MSG_IncorporateBegin
0[274860]: Done opening message stream!
0[274860]: RECV: (null)
Assignee: mscott → sspitzer
Severity: critical → major
Component: General → Networking: POP
Product: Thunderbird → Core
Version: unspecified → 1.7 Branch
Shouldn't this have been filed under component Talkback?
Btw.. I havent been able to make talkback work today either, the one that came
with trunk 2005022805, XP
No reply - changing component.
Assignee: sspitzer → jay
Component: Networking: POP → Talkback
QA Contact: chofmann
my bad - wrong product, not component
Hint: make sure you haven't installed on top of another installation (but
actually uninstalled old versions first)
And check your firewall. For each installation, Norton, for instance, needs to
be reconfigured.
Assignee: jay → mscott
Component: Talkback → General
Product: Core → Thunderbird
QA Contact: chofmann
Version: 1.7 Branch → 0.9
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.