From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; 0.8.1) BuildID: 2001040604 sending news messages to a news server that requires authentification doesn't work, this is a regression over 0.8 No error message is printed despite the failure. Reproducible: Always Steps to Reproduce: 1. Have an account on a news server that requires authentification (I am using Hamster (http://www.alphalink.com.au/~johnf/hamster.htm), and with it you can very easily create on your own windows machine local newsgroups for testing). 2. Log on the server and read a message 3. Click on reply. Send the reply 4. No error message is displayed, but in fact the sending of the message has failed. Actual Results: From Mozilla, there's no way to see something is wrong, except when you discover later that your message does not appear on the server. In the server log (Hamster), appears the following lines : 2001/04/06 19:09:51 {d6} > MODE READER 2001/04/06 19:09:51 {d6} < 200 ignored 2001/04/06 19:09:51 {d6} > POST 2001/04/06 19:09:51 {d6} < 480 Authentication required Mozilla does not respond to the 480 Authentication required message, and the sending is rejected. Mozilla does not print an error message. Expected Results: Here is the result of my investigation about the cause for this bug, but it requires a much more complete log of what happens with the server. Here is what happens in case of success with Moz 0.8 : Mozilla connects to the server and then uses the same network connexion to send the reply. As Mozilla is already connected, the authentification is not required by the server and the sending is a succes. 2001/04/06 10:11:19 {c3} Client 127.0.0.1:119 (448) connected 2001/04/06 10:11:19 {b6} < 200 Hamster-NNTP, Hamster classic Vr. 1.3 (Build 1.3.22.0) 2001/04/06 10:11:19 {b6} > MODE READER 2001/04/06 10:11:19 {b6} < 200 ignored 2001/04/06 10:11:19 {b6} > GROUP fr.lettres.langue.japonaise 2001/04/06 10:11:19 {b6} < 480 Authentication required 2001/04/06 10:11:19 {b6} > AUTHINFO user jmd 2001/04/06 10:11:19 {b6} < 381 More authentication information required 2001/04/06 10:11:19 {b6} > AUTHINFO PASS [...] 2001/04/06 10:11:19 {b6} < 281 Authentication accepted 2001/04/06 10:11:19 {b6} > GROUP fr.lettres.langue.japonaise 2001/04/06 10:11:19 {b6} < 211 2611 5900 8510 fr.lettres.langue.japonaise 2001/04/06 10:13:58 {b9} > ARTICLE 8504 2001/04/06 10:13:58 {b9} < 220 8504 <3acd3fbf.8531822@lord.usenet-edu.net> article 2001/04/06 10:13:58 {b9} < . 2001/04/06 10:15:27 {b9} > POST 2001/04/06 10:15:27 {b9} < 340 send article to be posted. End with <CR-LF>.<CR-LF> 2001/04/06 10:15:27 {b9} < 240 article posted ok <3ACD7B1F.6070408@club-internet.fr> Full log of failure with the latest beta : First there's a connexion to the server with succesful authentification, I read a message, but when I click on the send button of the reply, Mozilla opens a separate network connexion to the server to send the message. As it has not authentified itself yet on this new connexion, the server requires the authentification which Mozilla fails to provide. 2001/04/06 19:09:10 {c3} Client 192.168.212.165:119 (584) connected 2001/04/06 19:09:10 {ca} < 200 Hamster-NNTP, Hamster classic Vr. 1.3 (Build 1.3.22.0) 2001/04/06 19:09:10 {ca} > MODE READER 2001/04/06 19:09:10 {ca} < 200 ignored 2001/04/06 19:09:10 {ca} > GROUP fr.lettres.langue.japonaise 2001/04/06 19:09:10 {ca} < 480 Authentication required 2001/04/06 19:09:10 {ca} > AUTHINFO user jmd 2001/04/06 19:09:10 {ca} < 381 More authentication information required 2001/04/06 19:09:10 {ca} > AUTHINFO PASS [...] 2001/04/06 19:09:10 {ca} < 281 Authentication accepted 2001/04/06 19:09:19 {ca} > GROUP fr.lettres.langue.japonaise 2001/04/06 19:09:19 {ca} < 211 2623 5900 8522 fr.lettres.langue.japonaise 2001/04/06 19:09:19 {ca} > XOVER 8425-8522 2001/04/06 19:09:19 {ca} < 224 Overview information follows 2001/04/06 19:09:39 {ca} > ARTICLE 8522 2001/04/06 19:09:39 {ca} < 220 8522 <QHlz6.974$vY6.1769699@nnrp4.proxad.net> article 2001/04/06 19:09:39 {ca} < . 2001/04/06 19:09:51 {c3} Client 192.168.212.165:119 (308) connected 2001/04/06 19:09:51 {c3} Client 192.168.212.165:119 (228) connected 2001/04/06 19:09:51 {cc} < 200 Hamster-NNTP, Hamster classic Vr. 1.3 (Build 1.3.22.0) 2001/04/06 19:09:51 {d6} < 200 Hamster-NNTP, Hamster classic Vr. 1.3 (Build 1.3.22.0) 2001/04/06 19:09:51 {d6} > MODE READER 2001/04/06 19:09:51 {d6} < 200 ignored 2001/04/06 19:09:51 {d6} > POST 2001/04/06 19:09:51 {d6} < 480 Authentication required There are two failures here : Mozilla should answer to 480 messages in every case, not just only when the programmer is expecting a 480 message to occur. Or you just will always find new cases when some server sends 480 and it's unexpected. Mozilla should print an user error message when something goes wrong in the connexion with the news server.

Confirming. This is bad. Although I can reply to people's postings (IE, their mailbox), post a test message of my own and see all of the above in my Sent folder, my newsgroup posting, when replying, never appears on the server poisonivy.mcom.com, group "xrated" which is an auth group. All OSs from today's builds. Nominating for nsbeta1 in the hope that it's a simple fix that we might have time to get to.

Even worse is that I can *appear* to -send- fine without authenticating with poisonivy.mcom.com (on standard port 119). Only when I -read- messages, am I prompted for my username/password.

smells like a dup of the "no msg window in the news code" which I still need to fix.

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

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

fix in hand for the "Even worse is that I can *appear* to -send- fine without authenticating with poisonivy.mcom.com (on standard port 119). Only when I - read- messages, am I prompted for my username/password."

fixed. nothing to do with the "no msg window" problem. my fault 100%.

Verified on: Windows 2000 build 2001050704. Mac OS 9.1/OS X build 2001050708. Waiting on a divine miracle to sort out what needs to be done about bug 78874, which prevents me from launching even the Moz installer.

Much thanks to Sheela, who let me use her Linux build, since mine was horked. Verified fixed on: 2001050708 RedHat 6.2

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