User-Agent: Mozilla/5.0 (Win95; en-US; rv:1.7) Gecko/20040626 Firefox/0.8 Build Identifier: If there are more than one newsgroup accounts, the reply function does not work for at least one of the accounts. Reproducible: Always Steps to Reproduce: 1. Have at least two newsgroup accounts (e.g: Local newsgroup account, netscape newsgroup account) 2. make sure full newsgroup list has been downloaded for both accounts 3. Select a message on either account and press the "reply" button. Actual Results: Nothing happened. Expected Results: A window should have popped up for me to write my message. Tested with official TB0.9 build, as well as the 20041201 RC1 build.
If valid, this is a major bug. However, I cannot reproduce the problem. Is this bug a regression? That is -- did it work with an earlier build, but now has stopped working? Using a nightly build, examine the settings for each of the news-related identities -- what differences are there? (e.g. does one identity compose in HTML while another composes in plain text?)
I can't reproduce this.
Well, I reproduced it by creating a new profile, manually importing all of my E-mails from my old profile and then adding two newsgroup servers I frequently use. When I do this I can not reply to one of the newsgroups; the buttons reply, reply all and forward does not work, right-clicking on the message and selecting "reply" does not work. -- And yes, I had no problems whatsoever with an earlier build of TB (0.8).
Same bug here with TB 1.0. I only have one newsgroup account. Deleting all newsgroup data in the document & settings directory, and recreating the account, did not help. I uninstalled TB 1.0 and tried with TB 0.9 : same bug.
Same bug with TB 1.0.2. I only have one newsgroup account.
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.