2002031916 OS/2 This seems to be a regression of a bug I can't seem to find. It seems Mozilla has adopted the windoze concept of defaults and is misusing it. In advanced prefs for each news server I can choose to have either: 1-always use the "default" server, or 2-[my ISP's news server] This pair of choices is the same whether I am in advanced prefs for my ISP's news server, or for any other news server. I have set up six news server accounts. I can see no way have Mozilla tell me which news server is the default, but that is not directly the reason for this bug. Steps to reproduce. 1-Create more than one news server account 2-Subscribe to some of the same groups on more than one news server 3-Make one news server account unavailable. (I read most news (with Netscape 4.x) via local spool provided by Changi. Changi is at 127.0.0.1, but only when running. I use Mozilla to read news only on one other account, my ISP directly.) 4-Open an available news server account and read news on a group subscribed on more than one news server 5-Reply to an existing post, or try to compose a new post 6-Click send Actual behavior: Mozilla pops up two different cannot connect to server dialogs (one to the compose window, then focus shifts to the mailnews window, then the second popup appears). The compose window remains open under the mailnews window. Expected behavior: Successful post, compose window closed, focus returned to mailnews window.

Well, we don't have a default News server yet (see bug 16343). Also, the Advanced Account Settings dialog reflects SMTP server settings, and NNTP doesn't use SMTP to post messages. I've mailed both Seth and Jennifer about that dialog. I'll let you know by either commenting in this bug or filing a new bug about that dialog and cc:ing you on it.

Okay, the other bug is bug 109162. Note, the way we currently have it architectured is that news is as follows: If you have more than one server we default to the 'From' address of the account/server you currently have selected. You can use the dropdown box in the compose window to select another. For instance, I have news.mcom.com and news.mozilla.org setup. When I select news.mcom.com and hit Compose, the widget defaults to From 'Stephen Donner <stephend@netscape.com', and when you pulldown the widget, it says -news.mcom.com. I can then change this to be my other news account, 'Stephen Donner <stephend@netscape.com', -news.mozilla.org

I use primarily two news servers (although six are set up, and all are from migrating from 4.x): news1.atlantic.net 127.0.0.1 (Changi local news spool) For both my from address is UgaddaBkidding.due2UCE@atlantic.net, and my reply-to address is mrmazda@atlantic.net. Why isn't Mozilla doing like Netscape 4.x (and other newsreaders I've tried) and using the account being read from? I can't see any sense in making any other assumption or behavior.

2002033108 When I pull down the widget, there are seven listings of UgaddaBkidding.due2UCE@atlantic.net, one for each of six news servers, plus one for email, plus a second email address. When I choose the one with the (nearly invisible) news1.atlantic.net trailing, I still get the error dialog "cannot connect to server 127.0.0.1".

So, this bug really seems to be about the inability of Mozilla to post to an open Changi server running as localhost (loopback). Can you give us a log, when it fails? http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#nntp Thanks.

Please, could I really have been so unclear? Steps to reproduce 1-Shutdown Changi (127.0.0.1) 2-Migrate from 4.x, which has one email profile and 6 news servers with subscribed groups 4-Open news.atlantic.net server 5-Open to read on news.atlantic.net server a group subscribed on both news.atlantic.net and on 127.0.0.1 6-Compose a message 7-Choose send profile for news.atlantic.net, which in all particulars except server IP is identical to send profile for 127.0.0.1 8-Click send Actual results: Send fails due to 127.0.0.1 unavailable Expected results Send succeeds via open news server news.atlantic.net (like Netscape 3.x and 4.x) *** 1-Never once (IIRC) have I used 127.0.0.1 to read news with Mozilla. 2-If I start Changi, the post sent via news.atlantic.net will succeed, but only upon running Chanx, since Mozilla sends the post to the 127.0.0.1 spool dir instead of news.atlantic.net 3-I can post with Mozilla to news.atlantic.net without error, but only by deleting the entire 127.0.0.1 account from Mozilla

http://bugzilla.mozilla.org/show_bug.cgi?id=132477#c5 provides no instruction on logging OS/2 NNTP failure.

Gotcha, the real problem is that Mozilla is TRYING to connect to Changi, even when it should only be posting to news1.atlantic.net [209.208.44.28]. Seth is aware that our posting code is very weak (see bug 80542). Also, there are other, related (but not duplicate) bugs about similar behaviors. bug 54911 is really close, some of the comments in there suggest that it might even be a DUP.

Confirming.

Not Os/2 specific

OS/2 2002053008 trunk update: I've recreated by creating a new profile from scratch rather than the usual migrate from v4. I created first the ISP news server and tested for proper function. I then added Changi server 127.0.0.1. When I use Changi to read and try to reply, the reply is sent via the ISP server, which is confirmed by Mozilla timing out trying to connect to it if I have hung up the modem, and by Changi having nothing to post when running Chanx.

No improvement as of 1.0 release branch 2002060216. Same behavior as original report.

NAICT, bug 54911 is the bug I couldn't find when I first opened this. Changi/127.0.0.1 *is* the first listed server in 4.x, and remains the first listed server after migrate. *** This bug has been marked as a duplicate of 54911 ***

I believe so too, thanks for marking this a DUP. verified