Reproduction: 1. Set up a server/proxy host with n (n > 1) newsservers running at different ports. The 2 newsservers should carry (at least partly) different groups. 2. Set up Mozilla news accounts for each of them 3. Try to read groups from each of them 4. Try to post to each of them, to groups which don't exist on the respecitive other newsserver. Actual result: Step 3 works. Step 4 fails (at least for n-1 servers) Expected result: All steps work for all newsservers Additional Comments: I use this setup to access different news servers through my proxy.

Workaround: Add a fake hostnames to your /ets/hosts, pointing at the IP of the server/proxy. Then, use these fake hostnames as hotnames in Mozilla's accounts. The problem seems to be that some code thinks that an identical hostname means an identical server, which is wrong.

cc networking guys.

I guess that "some code" is in Mailnews.

Looks like bug 55540 to me *** This bug has been marked as a duplicate of 55540 ***

The other bug is about the Account Manager, which works fine for me. REOPENing.

Ben, could you try my patch (attachment 53095 [details] [diff] [review]) ? This patch mades only *minimal* changes to code, and not the best possible one, I think. May be I'll come with better patch later :-)

I don't have a current Mozilla build atm.

I'm not sure I about the hardcoded ':' part; if there are standard URI parsing facilities available, we should use those. Bbaetz or Darin would probably know about that. Denis, perhaps if you looked at how other protocols handle this, we could do this consistently for news? Thanks

use nsnull instead of NULL. There aren't parsing problems with this, since we're generating a host:port string, not parsing one. I'm not sure what the mailnews people think of the default paramaters, though.

This port situation is quite unique for nntp service :-). Also, other protocol handlers (imap, for example), uses hardcoded chars/string when constructing character strings for URIs. As for default parameters, it's not a problem, I can make them non-default. Also, I think it's a good idea to change parameter order of FindServerWithNewsgroup and FindHostFromGroup: (groupName, host, port) sequence looks more clear that (host, groupName, port). What do you think? I'll come with new patch in a moment...

Probably dup of bug 54911.

*** Bug 170673 has been marked as a duplicate of this bug. ***

sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.

Filter on "Nobody_NScomTLD_20080620"

Not quite. It's the same problem as 38137, I believe.