User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1 T-Bird 1.0 and 1.02 will not send a message after the first one is sent, i.e., if I compose and send a message, then compose a second message in the same session, pressing the "Send" button, or selecting "Send Now" or "Send Later" has no effect. It's necessary to close the application completely, saving the message, then reopening to send the saved message. No problems on receive, no problem with first sent message. Reproducible: Always Steps to Reproduce: 1.Compose a message and send 2.Compose a second message and attempt to send 3. Actual Results: No response whatever to click on "Send", "Send Now", or "Send Later". No known sequence to correct situation other than closing entire mail client, then restarting. Expected Results: Should have sent the subsequent message as requested, else offered an explanation as to why not. On only one occasion, the second message also could not be saved and had to be discarded. Normally, the message can be saved on closing, then reopened to send later.
Noticed additionally that problem occurs whether or not first message is actually sent. If a compose window is opened, then cancelled, no further messages can be sent until entire app is closed and reopened. However, the first message composed always sends OK, and if the app is closed with a saved message, the message can be sent when the app reopens. Suggestions what interactions could cause this condition? Extensions? OS problem? Problem did not occurr prior to vs 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.