2001121219, but hardly new. If I reply to a newsgroup message and attempt to crosspost to an additional group, pressing send pops up an error message "cannot post to more than one server" or something to that effect. I can only reply to the group in which I've found the message.

This message appears if you are subscribed to the same newsgroup on several servers, and post to it. Regardless of wether it's a crosspost or not. Reporter, is this what you are seeing?

I'm subscribed to a nearly identical set of groups on two servers, but a reply post is only refused if I add another group before sending, not if the post I'm replying to already has more than one group. As a test I just sent a message successfully to comp.os.os2.setup.storage in reply to message ID <3BD6E564.777A56AD@atlantic.net> (Subject: Re: 40GB hard disk - different than other posts I think), which was originally crossposted to comp.os.os2.setup.misc. Then I tried another reply to the same post, but added a third group, comp.os.os2.bugs, and that too was accepted, contrary to my bug submission description. These three newsgroups are not the same as those I could not do before submitting the bug. Generally, I would find a post on an alt.comp.* group to reply to, and because these groups expire much too quickly off my server, I would crosspost to a related big 8 comp.* group to postpone the expire. Now investigating further, I see that the server I was reading and to which I thought I was replying was news.atlantic.net. However, the two posts mentioned above are already showing on 127.0.0.1 (my local Changi news spool), which with Netscape doesn't show a post unless 127.0.0.1 was the one I was reading from/replying to, or I had run Changi after posting to news.atlantic.net. Mozilla has posted these two new posts to 127.0.0.1, and *not* to news.atlantic.net, even though in prefs, the outgoing server is set to smtp.atlantic.net. Next I went to alt.comp.periphs.mainboard.tyan on news.atlantic.net and tried to reply to message <3C1A85B0.B0B3BF59@atlantic.net> (Subject: Re: Shopping for Motherboard for Linux), adding a (5th) new group (previously missing from the list), comp.os.linux.setup. This post was refused as described per my original filing of this bug. The exact error message: "Sending of message failed. You can only send a message to one news server at a time.".

*** This bug has been marked as a duplicate of 35338 ***

Bug 35338 is distinguishable from this bug in that it's focus is in attempting to post to multiple servers. This bug is about being refused crossposting on a single server. This bug is therefore not a dupe of bug 35338.

this bug is very closely related to bug 35338 I believe. Reporter could you try and rephrase what you are describing? I had trouble trying to follow what you are saying. Note that with news servers, you post directly to the news server not via an smtp server, so that has nothing to do with it. You are subscribed to 2 news servers no?

I am subscribed to several news servers with many of the same groups subscribed on more than one server, but I read news with an open connection to only one at a time. Example 1: 1-Go to your ISP's newsserver with Mozilla 2-Go to alt.os.linux.mandrake 3-Click compose 4-Add newsgroup comp.os.linux.setup 5-Enter subject 6-Compose message 7-Click send Example 2: 1-Go to your ISP's newsserver with Mozilla 2-Go to comp.os.os2.setup.storage 3-Read a crossposted message 4-Click reply 4-Add groups comp.os.os2.bugs and alt.test and remove group comp.os.os2.misc 6-Compose reply 7-Click send When I submitted this bug, and as recently as one week ago, either of these examples would cause Mozilla to fail to send the composed message. Today in 2002020216 (OS/2) it works as it should. In the past I would generally have had Mozilla open for quite some time, possibly opening and closing mailnews and various servers several times before attempting a crosspost. Today, I opened Mozilla shortly after unzipping a new build and did not open mailnews, nor did I open any other news server or download mail, prior to testing for comment #5. Appears to be fixed. Worksforme.

verified wfm.