All users were logged out of Bugzilla on October 13th, 2018
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116 I have multiple news server configured : 1) news.free.fr for general internet news from my ISP 2) news.mozilla.org (guess why) 3) msnews.microsoft.com Concerning the reading, everything works smoothly. Problem occurs with posting. If I do a reply to a news, it works. If I do a reply to a mail that also contains a newsgroup address, the send operation fails because it does not chose the right news server to post the news. At least it does not take the first one and there is no way to specify a default news server (as for SMTP). This is very annoying because usually when you help someone in a newsgroup, and do not crypt you address, the guy usually talk to you directly via email adding a copy to the original newgroup. But then you cannot answer the email directly via reply-all. Reproducible: Always Steps to Reproduce: 1. Configure several news server and add newsgroup to read for each servers 2. Send to yourself a mail including a newgroup address 3. Try to reply to this mail Actual Results: The sending of the mail fails because it does not find the newsgroup because it probably talk to the last (or unspecified news server). Expected Results: Either 1) explicitely ask for the news server with a default value, 2) OR autamagically parse the newsgroup configuration to find the relevant server and only if not found ask for the news server address
Yes it is close to bug 230899 but not quite the same as it typically involve one mail addresse (the original news poster mail) and a single newsgroup address (the newsgroup in which the original news was posted and later responded and re-responded). The bug 230899 involves multiple newsgroup residing on different servers. I also think it is tottaly différent than 228597 as only one account is involved.
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.