Closed
Bug 37046
Opened 24 years ago
Closed 24 years ago
POP has trouble downloading large number of email messages
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
M18
People
(Reporter: siffert, Assigned: jefft)
Details
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14-15mdk i686; en-US; m15) BuildID: 2000041811 While trying to download >1800 messages from a pop server, Talkback gives me "Error loading with many headers to download" - in this particular case, it times out on message number 56 (which might be a large email, but it is timing out because I wait a VERY long time) without giving any further feedback. Hitting "Stop" then leads to bug 26770. Sometimes I cannot hit stop. Reproducible: Always Steps to Reproduce: 1.Access pop account with large amounts of email 2.Hit "get" 3. Actual Results: See description Expected Results: Fixing Bug 26770 would be a stopgap. But Mozilla should give a "progress report" on individual message downloads somehow. It should be able to download large numbers of POP messages. It should give a more detailed report through the UI when it fails. Using "Master Password"... had "leave messages on server" checked. reproduced while having "delete when deleted locally" both set and unset.
Having a progress bar is the subject of another bug. Reassign to jeff. jeff - do you want a protocol log? I don't recall how to obtain one. Thanks. siffert - how large is that 56th message?
Assignee: selmer → jefft
(excuse if I miss something, it's my first bug report.) The 56th message is small; 1498. I've confirmed that's the actual message by doing the full pop download via communicator 4.7. Messages are in the same order as was downloaded via M15, and the message before it is the same as the last one successfully downloaded via M15, so I'm certain it dies on the 1498-byte message.
A log would help. Setting the following environment variables will create the log. NSPR_LOG_FILE=E:\tmp\pop50.txt NSPR_LOG_MODULES=pop3:5 You can try using the limit message size download to workaround the large message download problem. user_pref("mail.server.server1.limit_message_size", true); user_pref("mail.server.server1.max_size", 50);
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
While some of the previous messages before #56 were over a meg in size, message #56 itself is only 1.5 KB. When I limited the size of the download, it worked on the large messages but it still froze in exactly the same place. The logs show that it gets to the end of message #56 but it never appears in my inbox and doesn't go on to the other 1750 messages. I have two logs - the big one from when the size wasn't limited, and the smaller one for when it was. Unfortunately they contain the content of my emails which are sensitive in nature. Any other options I can set which will repress that when I generate a log? I'll include the part of the email that froze it: 1024[804faf0]: POP3: Entering state: 15 1024[804faf0]: POP3: Entering state: 16 1024[804faf0]: SEND: TOP 56 20 1024[804faf0]: Entering NET_ProcessPop3 1448 1024[804faf0]: POP3: Entering state: 3 1024[804faf0]: RECV: +OK Top of message follows 1024[804faf0]: POP3: Entering state: 17 1024[804faf0]: Opening message stream: MSG_IncorporateBegin 1024[804faf0]: Done opening message stream! 1024[804faf0]: RECV: Return-Path: <jcosio@corp.TalkCity.COM> 1024[804faf0]: RECV: Received: from corp.TalkCity.COM (root@sendmail.talkcity.com [216.206.164.99]) 1024[804faf0]: RECV: by getmail.talkcity.com (8.9.3/8.8.7) with ESMTP id RAA09992; 1024[804faf0]: RECV: Fri, 8 Oct 1999 17:17:01 -0700 1024[804faf0]: RECV: Received: from ycarr (139-cmp-216-206-164-0.liveworld.com [216.206.164.139]) 1024[804faf0]: RECV: by corp.TalkCity.COM (8.9.2/8.9.2) with SMTP id RAA195361024[804faf0]: RECV: for <talk-staff@corp.talkcity.com>; Fri, 8 Oct 1999 17:06:39 -0700 (PDT) 1024[804faf0]: RECV: Message-Id: <4.1.19991008165744.0099f310@getmail.talkcity.com> 1024[804faf0]: RECV: X-Sender: jcosio@getmail.talkcity.com 1024[804faf0]: RECV: X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 1024[804faf0]: RECV: Date: Fri, 08 Oct 1999 17:06:01 -0700 1024[804faf0]: RECV: To: talk-staff@corp.TalkCity.COM 1024[804faf0]: RECV: From: Janelle Cosio <jcosio@corp.TalkCity.COM> 1024[804faf0]: RECV: Subject: I Moved! 1024[804faf0]: RECV: Mime-Version: 1.0 1024[804faf0]: RECV: Content-Type: text/html; charset="us-ascii" 1024[804faf0]: RECV: Status: RO 1024[804faf0]: RECV: 1024[804faf0]: RECV: <html> 1024[804faf0]: RECV: <font size=4 color="#0000FF">Hi all, I case you have not notice I 1024[804faf0]: RECV: have moved to a new home. I'm on the 1st floor in suite 110 at 1024[804faf0]: RECV: Orchard City Drive. If you need to order office supplies I put a 1024[804faf0]: RECV: wall pocket with order forms and new catalogs by the fax/copy machine 1024[804faf0]: RECV: next to the HR forms book shelf. You can also find forms to use if 1024[804faf0]: RECV: your having phone problems. You don't need to run down stairs just 1024[804faf0]: RECV: put the forms in my mail hanging folder and I'll pick up your 1024[804faf0]: RECV: request. If it is urgent than e-mail me your request. Thanks 1024[804faf0]: Entering NET_ProcessPop3 1 1024[804faf0]: POP3: Entering state: 17
Sounds like we were stopping in handling Top responses. I need to find a to reproduce this problem.
Comment 6•24 years ago
|
||
Moving to M18 and nominating for beta3.
Keywords: nsbeta3
Target Milestone: M17 → M18
siffert - do you still have this problem with the latest Mozilla builds?
hmm, pratik, does this sound similar to the bug you filed about the summary files and POP on the Mac? siffert - do you still see this in the nightly builds? Thanks.
Comment 9•24 years ago
|
||
It does sounds similar to bug 44801. I haven't come across this problem in the recent build on MAC.
Comment 10•24 years ago
|
||
Mark duplicate of 44801 for now. *** This bug has been marked as a duplicate of 44801 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•