Closed
Bug 248927
Opened 20 years ago
Closed 19 years ago
No "stop" functionality within IMAP
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: minfrin, Assigned: Bienvenu)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040623 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040623 Over a dialup link, do the following: - Select a large mail folder to synchronise - Start synchronising that folder - Notice that fetching mail is impossible while folder synchronisation is taking place - Notice that stopping the synchronisation, in fact stopping any IMAP operation (especially in the case where an IMAP server has become unresponsive for any of a million reasons) is impossible without quitting mozilla and restarting it. Reproducible: Always Steps to Reproduce: xxx
Reporter | ||
Comment 2•20 years ago
|
||
No, no duplicate - bug 21829 describes the stop button not working inside IMAP, this bug describes the fact that the stop button (or equivalent functionality that could substitute, such as a stop menu option) is missing entirely from Mozilla.
Assignee | ||
Comment 3•20 years ago
|
||
if this bug is about the stop button being missing from the ui, have you tried configuring your toolbar such that it has a stop button? Edit | Preferences | Mail & Newsgroups - check the stop button in the "select the buttons you want to see in the toolbar" area. Also, pressing <esc> should be equivalent to hitting the stop button.
Reporter | ||
Comment 4•20 years ago
|
||
Having switched the stop button back on in the UI (no idea why the thing is off by default), I can confirm it makes no difference. The stop button doesn't seem to apply to all the open IMAP connections (in fact, I can see no clear pattern as to which connection the stop button might be referring to, as the majority of the time the stop button is greyed out). The problem is that a combination of bugs in either mailnews, or in the IMAP server, or both causes the IMAP state to become "stuck" over time. Right now for example, I can check mail, I can compress my inbox, but messages being sent are sitting hung solid saying "copying to sent folder", and I am unable to move mail messages from one folder to another (attempts to do so are ignored/queued by Mozilla, but never actually completed). Expecting every single bug that might cause this problem in mailnews and courier-imap to be fixed before this problem is solved is impractical: I need a button that disconnects all current IMAP connections (whether mailnews believes them to be working or not), so that outstanding IMAP synchronisation can be retried with new IMAP connections. Right now the only way to achieve this is to shut down mailnews, and navigator, and close all 20 tabs in my browser - a highly inelegant and inconvenient solution.
Reporter | ||
Comment 5•20 years ago
|
||
Is there any progress on this bug? MailNews remains an extremely unreliable IMAP implementation, and failures cannot be recovered from without shutting down both browser and mail reader.
Assignee | ||
Comment 6•20 years ago
|
||
If you toggle the offline button off and on, that will close every open imap connection
Comment 7•20 years ago
|
||
Stop button does not work at all in Thunderbird 0.6-0.8. :-( Please fix this, as this is a very elementary UI element and function that simply does NOTHING. Cf. Bug 239616
Updated•20 years ago
|
Product: MailNews → Core
Comment 8•19 years ago
|
||
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/
Comment 9•19 years ago
|
||
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
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
•