Cannot post to a specific newsgroup and mozilla isn't sending any data to the newsserver...

RESOLVED EXPIRED

Status

--
critical
RESOLVED EXPIRED
16 years ago
10 years ago

People

(Reporter: bugzilla, Assigned: sspitzer)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

Since two days mozilla refuses to post messages to a specific newsgroup. Reading
other news in this groups works fine. There is no authentication or soemthing
else needed for the newsserver or the newsgroup, posting by using TELNET works
fine. Mozilla just opens a box with "Sending of message failed. The message
could not be posted because connecting to the news server failed. the server may
be unavailable or is refusing connections... [and so on]".

I made some test and created an nttp log...
First I posted to another newsgroup with no problems and then I tryped to post
to the "specific"...

0[2342d8]: (1ee4ef8) setting busy to 1
0[2342d8]: (1ee4ef8) ParseURL
0[2342d8]: (1ee4ef8) fullPath = /
0[2342d8]: (1ee4ef8) m_messageID = (null)
0[2342d8]: (1ee4ef8) group = (null)
0[2342d8]: (1ee4ef8) commandSpecificData = (null)
0[2342d8]: (1ee4ef8) m_key = -1
0[2342d8]: (1ee4ef8) Next state: SEND_FIRST_NNTP_COMMAND
0[2342d8]: (1ee4ef8) Sending: POST

0[2342d8]: (1ee4ef8) Next state: NNTP_RESPONSE
0[2342d8]: (1ee4ef8) Receiving: 340 Ok
0[2342d8]: (1ee4ef8) Next state: SEND_FIRST_NNTP_COMMAND_RESPONSE
0[2342d8]: (1ee4ef8) Next state: SETUP_NEWS_STREAM
0[2342d8]: (1ee4ef8) Next state: NNTP_SEND_POST_DATA
0[2342d8]: (1ee4ef8) nsNNTPProtocol::PostData()
0[2342d8]: (1ee4ef8) Sending: Date: Sun, 04 May 2003 00:38:36 +0200

From: Achim Friedland <ahzf@datenkommunismus.de>

Organization: Regionales Rechenzentrum Heinrich Hertz

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312

X-Accept-Language: en-us, en

MIME-Version: 1.0

Newsgroups: fem.talk.golan

Subject: sdsd

Content-Type: text/plain; charset=us-ascii; format=flowed

Content-Transfer-Encoding: 7bit



sdsd

-- 

Demokratie beruht auf drei Prinzipien: auf der Freihei
0[2342d8]: (1ee4ef8) Sending: 

.

0[2342d8]: (1ee4ef8) Next state: NNTP_RESPONSE
0[2342d8]: (1ee4ef8) Receiving: 240 Article posted
0[2342d8]: (1ee4ef8) Next state: NNTP_SEND_POST_DATA_RESPONSE
0[2342d8]: (1ee4ef8) Next state: NEWS_POST_DONE
0[2342d8]: (1ee4ef8) NEWS_POST_DONE
0[2342d8]: (1ee4ef8) Next state: NEWS_FREE
0[2342d8]: (1ee4ef8) CleanupAfterRunningUrl()
0[2342d8]: (1ee4ef8) setting busy to 0
0[2342d8]: (22289f0) setting busy to 1
0[2342d8]: (22289f0) setting busy to 1
0[2342d8]: (22289f0) ParseURL
0[2342d8]: (22289f0) fullPath = /
0[2342d8]: (22289f0) m_messageID = (null)
0[2342d8]: (22289f0) group = (null)
0[2342d8]: (22289f0) commandSpecificData = (null)
0[2342d8]: (22289f0) m_key = -1
0[2342d8]: (22289f0) Next state: SEND_FIRST_NNTP_COMMAND
0[2342d8]: (22289f0) Sending: POST

0[2342d8]: (22289f0) Next state: NNTP_RESPONSE
0[2342d8]: (22289f0) Receiving: 440 posting not allowed
0[2342d8]: (22289f0) Next state: SEND_FIRST_NNTP_COMMAND_RESPONSE
0[2342d8]: (22289f0) Next state: NEWS_ERROR
0[2342d8]: (22289f0) NEWS_ERROR
0[2342d8]: (22289f0) Next state: NEWS_FREE
0[2342d8]: (22289f0) CleanupAfterRunningUrl()
0[2342d8]: (22289f0) setting busy to 0

When I look at tcpdump on my linux bridge I see tcp packets for the first
posting, but not a single packet for the last... So I think the tcp connection
was never opend and the error "440 posting not allowed" was never received...
It must be another problem...




Reproducible: Always

Steps to Reproduce:
1. Try to post ;)
2.
3.

Actual Results:  
I see a boring box...

Expected Results:  
Post my message...

Comment 1

16 years ago
that looks like a similar bug that I had when I tried to post to a different
newsgroup that was under a different server.  does this bug describe it?  it did
have an connection refused error message.

this is an os/2 version.  Mozilla 1.3

Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.3) Gecko/20030313
Product: MailNews → Core
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
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.