Closed Bug 194566 Opened 22 years ago Closed 19 years ago

If sending to a newsgroup is cancelled before the message has been delivered the message send button becomes unresponsive.

Categories

(MailNews Core :: Networking: SMTP, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: farcusnz, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 Sometimes when sending a message to a newsgroup the message does not seem to be ablt to contact the smtp server and sits there continually trying to send. There is no time out or anything. If I hit the cancel send button the message stops trying to send, however, the throbber continues to throb and the status bar at the bottom continues to rotate (or however you descirbe this). If I try to hit the send button on this message to have another go at sending it the send button is totally unresponsive. I have to save the message, close the whole Mozilla application and re-open it and then try sending it again. 9 times out of 10 this solves the problem. I haven't seen this behaviour on a mail account - only one of my news accounts. However, that is not to say that the behaviour does not occur on my other accounts - I just haven't seen it yet. Reproducible: Sometimes Steps to Reproduce: 1.Compose news message 2.Hit send; spellcheck is activated; spellcheck is completed; hit send; message tries to go but cannot. 3. Hit cancel; try to hit the send button again; send button is unresponsive 4. Save message; close Mozilla; reopen Mozilla; send message
I have the same problem with version 1.7.2. I'm sure some of this problem is with my ISP, bellsouth.net. When I try to send to bellsouth's server, and the message won't send, I hit cancel, and get this message: There was an error copying the message to the sent folder. Retry? I shut down all programs, to restart, and get this message: The message was sent successfully, but could not be copied to your sent folder. I hit cancel, and Mozilla shuts down with no error message. It appears it was trying to send the message all the time, even after I canceled the message. I had the same problem with Netscape 7.02, except instead of closing like Mozilla, I would get the error message: This program has performed an illegal operation and will be shut down. I got tired of the problem with Netscape, and decided to try Mozilla, and the problem is the same.
Product: MailNews → Core
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: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.