Closed Bug 67894 Opened 25 years ago Closed 21 years ago

Checking mail stalls after powerbook goes to sleep

Categories

(MailNews Core :: Networking: IMAP, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 243605

People

(Reporter: mikepinkerton, Assigned: Bienvenu)

Details

(Keywords: regression)

- launch mail, check your IMAP mail - put machine to sleep (powerbook, in this case) - wake machine - click "get msg" expected: - should check mail and stop throbber actual: - spins with throbber loading for a long time, mail not retrieved If i click "stop" then click "get msg" again, it's all ok. Only that first time after wakeup is affected. I let it sit for over a minute and it never timed out, just happy as a clam spinning the throbber.
there is a workaround (not dogfood), but i'm pretty sure it didn't use to do this.
Keywords: regression
QA Contact: esther → sheelar
I'm having the problem described, but the workaround doesn't work, because this particular bug freezes mozilla up on my machine. I have to force quit to get out of it. running 0.9.6. OS9.0.4. Reproduceable every time. I can wake from sleep and browse the web no problem. If I force quit i can launch mozilla back up and it seems to behave properly again.
*** Bug 183645 has been marked as a duplicate of this bug. ***
seems to be OS: All?
After resuming my laptop from standby mail will no longer automatically fetches mail from my POP account. I have this set: “Check for new messages every 1 minutes”. If I change the minute value to anything else the same thing happens. If I restart mail it will fetch new mail until the next standby/resume cycle. Clicking the "Get Msgs" DOES get mail after resume. The system has to be in standby for at least a couple minutes, not just a few seconds. I'm running Mozilla 1.2.1 on Windows XP.
Ok, this morning when I resumed my laptop from standby mail checked for new messages as it should. It seams to me that mail stops checking for new messages on resume if it tries to check for new messages as the standby process starts. Does mail stop trying to get new messages if it fails once?
seems to work fine with 1.1 milestone on my powerbook. This bug, RE the title, is for the Mac, so I'd say set this to WORKSFORME (since i'm the orig reporter), if you're having a problem on XP then create a new bug andset the platform to All or XP...?
I had a new bug filed, but it was set as a duplicate of this bug.
works on mac, but not on XP
OS: Mac System 9.x → Windows XP
Hardware: Macintosh → PC
I have this problem with 1.5b on Mac OS X 10.2.6. After sleep, getting mail or reading a message with IMAP just hangs until it times out. Sometimes at the end of the timeout it will have the mail, usually not. This actually was never a problem for me until recently, so it seems like a regression to me. I'm fairly certain that 1.3 did not do this, I can't quite remember if it started with 1.4 or 1.5a.
I'm experiencing something very similar on Mac OS X 10.3.3 with many different 1.7 builds including Mozilla 1.7 RC2. My mail configuration is as follows (3 accounts): 1. IMAP account, check mail automatically every 3 minutes, client of UW IMAP server 2. POP account, check mail automatically every 3 minutes, client of Netscape POP server 3. IMAP account, no automatic mail checking, client of UW POP server. I don't have problems with wake/sleep normally, but if I change locations (IP addresses), I get the "Spinning ball of death" from Mozilla on Mac OS X upon waking up. No amount of waiting seems to fix it, and sometimes the OS reports that the application is no longer responding. Nothing seems to bring it back, except killing it and restarting the application. I can avoid the problem if I "Go Offline" prior to changing locations. The problem first appeared coincident with the introduction of IMAP IDLE support (1.7 alpha?), but I'm not sure if its directly related to it.
can you try a 1.8 trunk build from today?
Assignee: mscott → bienvenu
I see this bug too on 1.7rc1 & rc2 on MacOSX 10.3.3. See talkback TBS6002Z 5/22/04 1:58PDT (I did a kill -SEGV to get a talkback, rather than doing Force Quit). It did (and does) not occur on 1.6. Situation: use Moz mail (IMAPS) at work on wireless. Sleep. Awaken at home on wireless. Change Location (which changes networks). Wait for menu bar to show wireless is now active (meaning Mac has changed addresses & connected on wireless). Give master password to Moz. Do a Get New Messages. I then get the spinning circle. I waited 10 minutes here. I cannot get Moz to respond at all - no other window comes to top, etc. Netstat -a shows old (work 192.12.5.33) net address to imaps host but no new (home 192.168.1.11) net connection to imaps. (It happens when I move from home to work too). Normally I have to do Force Quit to stop Mozilla, thus losing my state. Under the above conditions, it seems to happen every time in 1.7rc1 & rc2. In 1.6 it generally makes a new connection without much if any delay. I will try the 1.8 alpha 1 (dated 5/20) but probably can't test it until Monday 5/24.
Sorry, that Talkback Incident ID should have read TB56002Z
OS: Windows XP → MacOS X
Hardware: PC → Macintosh
I have a bunch of dupes on this bug with OS X users seeing this in Thunderbird 0.6. Something definetly aggravated this situation between 1.6 and 1.7 based products. Unfortunately, Mac talkback is not working very well. The only thing the talkback ID shows is: libSystem.B.dylib.71.0.0 + 0x17048 (0x90017048)
In Mozilla 1.8a1 (Build ID: 2004052008), I did not experience this bug today when I changed networks (from home to work) as I have in 1.7rc1 & rc2. I do see 5 connections from my laptop's work address to my IMAPS server (port 993) and none from my home address to the IMAPS server.
Someone needs to throw a bunch of new OS libs onto the Talkback server for the various Mac OS X 10.3 versions, so that you get system symbols.
I have used 1.8a1 seven times when this bug would have been triggered in 1.7rc2 and it worked like a charm each time. Any chance this fix could get moved into the 1.7 release, so it is in the next release to the general public? Otherwise Mac users will be severely impacted. For instance, I will not use 1.7 in such a case. I would rate this severity as critical because when this occurs (and it occured everytime I changed networks as previously described), the only resolution is to kill Mozilla and restart. (You can't even read web pages once this happens.) By the way, I believe the bug we are talking about now is not the bug originally reported years ago. The problem described in Comment #11 and #13 deal with a change of IP address and only started occuring in the Moz 1.7 (and Tbird 0.6) systems.
Mabry, does your imap server support IDLE? This might have been fixed in 1.8 by a change to the way we handle ending the idle session - I think I only checked that fix into 1.8...
this could easily be tested by turning off IDLE support in 1.7 and trying to reproduce the issue there again. Can you try turning off IDLE? Account Settings / Server / advanced. Thanks!
I'm thinking the fix in http://bugzilla.mozilla.org/show_bug.cgi?id=243605 might help.
Flags: blocking1.7?
the next nightly 1.7 rc build should have the aforemention change in it...please let me know if you try that and it works for you. Thx.
As per comment #20, in 1.7RC2, I turned off "Use IDLE" in Mozilla for my IMAPS server. When I changed networks (from work to home) tonight, I had no problems.
*** This bug has been marked as a duplicate of 243605 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Flags: blocking1.7? → blocking1.7-
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.