Closed Bug 288140 Opened 20 years ago Closed 20 years ago

Slow internet connection conflicts with 'check mail every xx minutes'

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bennettf, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6) Gecko/20050321 Firefox/1.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.6) Gecko/20050321 Firefox/1.0.2 On a computer with very slow internet, receiving a very large attachment, if 'check mail every xx minutes' is checked, then if checking mail takes longer than xx minutes, it reinitiates the mailcheck. Obviously this is easy to workaround but it shouldn't begin a new mailcheck while one is already in progress. Especially in the case where xx==1. Reproducible: Always Steps to Reproduce: 1. Set 'check mail every xx minutes' to 1 minute. 2. Send self a very large attachment which will take more than 1 minute to download. 3. That's it. Actual Results: Kept restarting the mail download Expected Results: Waited until current processes were finished before checking again.
UNABLE to reproduce the bug. 1. i've sent myself a 1MB mail 2. set downloadspeed to 1kb/s 3. checked for mail 4. waited 30 minutes actual and expected result: the download of the mail was still running and TB had NOT reinitiated the mail check. --> WFM
(In reply to comment #1) > > actual and expected result: the download of the mail was still running and TB > had NOT reinitiated the mail check. I presently have no way to throttle my download so I cant test, but what was your setting of "automatically check mail every <xx> minutes" set too ? As i read your text you tested with a manual check mail ?
(In reply to comment #2) > I presently have no way to throttle my download so I cant test if you are on windows: http://www.netlimiter.com > was your setting of "automatically check mail every <xx> minutes" set too ? it was set to 10 minutes (sorry I forgot to mention it) > As i read your text you tested with a manual check mail ? yes, but I just tried again with interval set to 1 minute and restarting TB to initiate the normal startup mail check still --> WFM btw. TB Version 1.0 (20041206) on Win2k Bennett Foddy: what TB Version are you using? Can you reproduce the bug with a recent nightly?
I was using TB 1.02, on a connection giving about 1kb/sec, downloading mail with large pdf attachments. It is reproducible here, but I guess it's also possibly due to some internal timeout if there s no data received for a certain length of time. It *seems* to be fixed by setting the mail checker to 20 instead of 10 minutes, but then again echinacea tablets *seem* to prevent me from getting colds.
Version: unspecified → 1.0
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: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.