User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021029 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021029 Sending of nwesgroup message failed if i change my main messenger window Reproducible: Always Steps to Reproduce: 1.subscribed to newsgroup netscape.test 2.click on group, compose test msg 3.go back to main mail and news window, click on sent, type in a search "jg" or whatever will bring something up. (the search is an essential step, could not replicate without it) go back to compose window, paste somthign from searched sent folder, click send Actual Results: Sending of message failed Please verify that your Mail & newsgroup account settings are correct and try again Expected Results: Should have let me send the msg please note that as soon as i changed the mail and news window back to netscape.test the msg sent fine i did not change the newsgroup post address from when it did not work submited in utf8
Summary: Sending of nwesgroup message failed if i change my main messenger window → Sending of newsgroup message failed if I change my main messenger window
I've seen sporatic but relatively common examples of this error using 1.3 (released version) on two different Win2k boxes. I have not seen as consistent a process to cause the error as Seth describes. In all of the cases I've observed, the message is actually delivered successfully. This behaviour began when I upgraded from 1.2.1 (released version). In my case, the two profiles (for 2 machines) in use were originally created using NS 4.79, updated using NS 7.0 and then 1.2.1 and 1.3. Concurrent use between those browser versions has been rare if done at all. Note that bug 163892 <http://bugzilla.mozilla.org/show_bug.cgi?id=163892> may have the same underlying cause. But, again in that description, delivery seems to fail and that's not what I've seen.
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.