When I am trying to connect to my work mail server, which happens automatically when Thunderbird starts up, it will fail if I haven't started up the VPN. I can hit the "Stop" button, which I thought Mozilla MailNews (1.2/1.3ish) used to correctly interpret as an attempt to cease trying to reach the IMAP (/SSL) server. This does not work in Thunderbird. If I'm misremembering the old behaviour, then this is an RFE. Otherwise, it's a bug that this doesn't work the way it used to in mozilla 1.3 or so. I think this may be Platform/OS: all, but I can't verify that right now.

Same problem with 0.8. Cannot abort this transmission.

Meant 0.6, of course

Also in 0.7.2

isn't this the same as 238692?

or bug 248927?

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.

Confirmed on W2000pro with TB 0.9. As far as I know this has never worked. It neither aborts connections to POP servers.

Also does not work in Linux. Is this bug 138632?

Duplicate of 269462

Woops, meant Confirmed in 1.0.1

*** Bug 301512 has been marked as a duplicate of this bug. ***

Any news on this bug? At this stage the Stop button appears to have no function at all, it's just cluttering the UI.

*** Bug 269462 has been marked as a duplicate of this bug. ***

*** Bug 238692 has been marked as a duplicate of this bug. ***

(In reply to comment #12) > Any news on this bug? At this stage the Stop button appears to have no function > at all, it's just cluttering the UI. what he said. this is very disconcerting.

The Stop button does work when retrieving messages from an IMAP server. However, it does *not* work when checking the server (IMAP nor POP3) for new messages when the server is not available or does not respond.

This hasn't been fixed in 1.5. With an internet connection as faulty as mine, this should be a priority. I find it hard to believe a bug like this has gone unfixed for over a year.

Further to this, I am using 1.5 on OS X 10.4. The stop button is *disabled* while tbird is automatically checking for new mail after I wake my laptop, but before I have established a network connection. Pressing 'get mail' doesn't cause tbird to retry the connection attempt, nor does pressing stop (because you can't!). The only solution is to wait a rather long time for it to time out, or to quit the app, which is rather of a kludge.

This problem also occurs when trying to connect to an NNTP (newsgroup) server. If Thunderbird cannot connect, even selecting a different server account does not stop the attempt. The Stop button is useless for this.

Similar or possibly duplicate to bug 120795 and bug 138632

Persists in 2.0.0.4/Windows XP. This is especially unnerving, when you routinely have to check more than one account.

Continues to be frustrating waste of time in TB 2.0.0.9/WinXP, SP2.

It's MUCH worse for me! I have a lot of email addresses to check. When something along the way prevents Thunderbird to reach and/or retreive email from any of the SMTP servers, sometimes the activity will stop and Thunderbird gives an error message. This is bad enough and very frustrating since it then takes a long time for it to cycle through all of my email accounts. HOWEVER... sometimes it just keeps going and going and going! Unlike the Energizer Bunny, this IS NOT GOOD at all! Because the "Stop" button DOES NOT STOP the process, and just keeps going, I'm then totally unable to get and/or send email! WORSE... if I then try to shut down Thunderbird by "File>Exit" or clicking the "X" on the Title Bar, even though Thunderbird looks like it's closing... I can't start it again because in actuality it's STILL RUNNING, as shown in Task Manager! The ONLY way that I can reload Thunderbird to send and receive email... is to CLOSE ALL applications, SHUT DOWN my computer, start my computer again (running Vista Home Premium), then RE LOAD ALL PROGRAMS! Even more buggy... usually, my computer won't even shut down or re-start! This only happens when this situation occurs with Thunderbird... AND when FireFox stops working and won't go anywhere! Maybe they're related problems? Whatever it is, it causes a SERIOUS problem in the way of LOST TIME! Thanks! Steve

I'm also going to tag another closely-related point on here: Sometimes tbird just *forgets* to keep checking my e-mail at regular intervals (I'm using IMAP, FWIW), so it gets stuck -- perhaps something to do with my IMAP server, but tbird should have no problem working around this -- and forgets to ever check my e-mail again, until I come along and force it to. I suspect there are some greater issues with tbird's threading model, or perhaps it's just very immature.

PSE, could someone explain, what makes this bug so negligible, that it is not being addressed? The list of bugs, which have in deed been removed and that of all the improvements done to TBird are amazing. But at some moment, disregard becomes an effort, and I wonder to what purpose...

Continues in TB 2.0.0.23/WinXP, SP2.

This would be great to get, but we wouldn't hold 3.1 for it if it were the last bug standing. Marking wanted-thunderbird+, blocking3.1-.

Sorry Dan, it wasn't my intention to set a flag.

The "Stop" button does function properly, stopping the current transfer, in Thunderbird, version 2.0.0.24 (Windows XP, SP3). (Perhaps this information could prove helpful to anyone fixing this deficiency in TB3.x.) It is a function that I find useful with sufficient frequency that I have been forced to stop using TB3.x and have reinstalled TB2.0.0.24. Time marches on! I (as did monsterslayer@email.de above) am still perplexed as to why this bug has persisted for so long without any satisfactory explanation.

If the Stop button does indeed stop attempting to transfer headers or messages, then something has been done to correct bug #311948. Is that true?

I'm still running 2.0.0.24. Ever since reading Kennison's post, I've had several opportunities to test the Stop button and as I reported earlier, it doesn't work in 2.0.0.24. I'm still running XP SP2. Surely the SP wouldn't affect this? Kennison, you said the button stops "the current transfer" -- are you using it to stop file transfers? If so, up, down or both? I haven't tried using it for that, but that would shed new light on this bug. As noted in many of the previous comments, the desire is to interrupt TB message retrieval when one (or all) of the mail servers are unresponsive for whatever reason (e.g., mail server down or internet connection down).

ESC Key nor Stop Button will not stop mail msgs from being received in WinXP SP3 with TB 3.1.6. This has been going on for as long as I can remember regarding Escape, but believe the Stop button is relatively new.

(In reply to comment #32) > I'm still running 2.0.0.24. Ever since reading Kennison's post, I've had > several opportunities to test the Stop button and as I reported earlier, it > doesn't work in 2.0.0.24. I'm still running XP SP2. Surely the SP wouldn't > affect this? > > Kennison, you said the button stops "the current transfer" -- are you using it > to stop file transfers? If so, up, down or both? I haven't tried using it for > that, but that would shed new light on this bug. > ginahoy@aol.com: I frequently use the "Stop" button, in Thunderbird 2.0.0.24 (Windows XP, SP3), to interrupt or stop lengthy sessions of downloading messages from responsive POP mail servers. (I can not use it to interrupt sending a message to an SMTP server; the button doesn't even become activated when sending messages.) The "Stop" button in Thunderbird 3.1.6 (Windows XP, SP3; Windows 2000, SP4) appears to remain activated at all times, even when there is nothing happening for it to stop. However, when I attempt to use it to interrupt or stop lengthy sessions of downloading messages from responsive POP mail servers, the "Stop" button does not work.

(In reply to comment #34) > I frequently use the "Stop" button, in Thunderbird 2.0.0.24 (Windows XP, SP3), > to interrupt or stop lengthy sessions of downloading messages from responsive > POP mail servers. (I can not use it to interrupt sending a message to an SMTP > server; the button doesn't even become activated when sending messages.) > I guess I've never needed to stop a session with a responsive server, or at least it never occurred to me to try. I just tested that scenario and it works for me (2.0.0.24 XP SP2). So, the stop button is apparently completely broken in 3.1.6, and has limited function in 2.0.0.24 -- e.g., does not terminate session when IMAP or POP server is unresponsive. Doubting this bug will ever be fixed in 2.0.0.24, wonder if bugzilla protocol requires a new bug report for Version 3?

(In reply to comment #35) > (In reply to comment #34) > ... > So, the stop button is apparently completely broken in 3.1.6, and has limited > function in 2.0.0.24 -- e.g., does not terminate session when IMAP or POP > server is unresponsive. > > Doubting this bug will ever be fixed in 2.0.0.24, wonder if bugzilla protocol > requires a new bug report for Version 3? ... or if protocol prohibits a new bug report for Version 3.1.6 It seems that, since Version 3.1.6 doesn't even perform to the level of Version 2.0.0.24, a new bug report should be warranted. If protocol doesn't prohibit a new bug report, I think that a new report, specifically for Version 3.1.6, would stand a better chance of generating a fix.

is bug 311948 essentially a duplicate? the regression in Bug 579576 which kills the escape key functionality makes fixing this bug more imperative

The quick filter bar erroneously co-opted the "cmd_stop" command entirely on all 3-pane tabs which causes both the 'escape does not stop' and 'stop button does not stop' problems. The likely solution would probably still leave the quick filter bar in control of the escape key but fix up the stop button. That can be reflected into bugs in whatever way makes sense.

I'm going to fix this on bug 579576, marking dependency.

I have two ISP accounts. RoadRunner is the provider for my broadband Internet connection. Sunset.net is the host for my rossde.com domain for both my Web site and E-mail (although, I also have a RoadRunner E-mail account that I normally use only for testing). On 29 May 2014, at approximately noon Pacific time, Sunset.net went down for emergency services to its servers. As I submit this comment, Sunset.net is still down. If I use Thunderbird to Get Messages in an attempt to check if Sunset.net is again functional, Thunderbird keeps trying. The Stop button does not terminate the attempt. Yes, eventually Thunderbird times-out on the attempt; but I don't need to wait that long. By the way, there is no message when Thunderbird times-out. Should there not be a "Failed to connect to mail server" message?