Re: エラーメッセージ


"Don Kirkman" <spambuster@xxxxxxxxx> wrote in message news:j2em41p6ncmmrnsdqrsfmt5j9d3t6thveu@xxxxxxxxxx 
It seems to me I heard somewhere that B. Ito wrote in article
<d2el2i$p7u$1@xxxxxxxxxxxxxxxxxx>:

"Don Kirkman" <spambuster@xxxxxxxxx> wrote in message
news:lglj41h6g996an9s5anl7i4823dl8lsuok@xxxxxxxxxx

It seems to me I heard somewhere that B. Ito wrote in article
<d2bfqu$49m$1@xxxxxxxxxxxxxxxxxx>:

"Bart Mathias" <mathias@xxxxxxxxxx> wrote in message
news:LD12e.27345$191.21513@xxxxxxxxxxx
Cindy wrote:
B. Ito wrote: 

Ｐ．Ｓ．
下記のようなアナウンスがあり、何度も送信失敗しました。
メッセージを投稿できませんでした。  件名  'Re: ...koiten janee', アカウント


: 'news-wst.ocn.ad.jp', サーバー : 'news-wst.ocn.ad.jp', プロトコル :
NNTP,
サーバーの応答 : '441 Line 3 too long', ポート : 119, セキュリティ
(SSL): なし, サーバー エラー : 441, エラー番号 : 0x800CCCA9

どうしたらよいのでしょうか？ 

I used to get something like that, and had to trim or get rid of the
References: (or was it the Path:) line in the header.


It was easy to do with NewsRog on my Amiga, but I can't figure out how
to do it in Mozilla.

I did the trimming of the References and succeeded to send my new post
but that was only one chance. My second trial of the same wouldn't work. 

Tonight I added my comments without any trimming even though the thread
was unneccessary too long.  And my first sending click worked.


As you see I copied the error reference number, "441, エラー番号 :
0x800CCCA9."


I neglected to note that I copied the following from the help section of
one of my most-used programs.  There are sites on the Web that have long
lists of error message codes.

A few of the reasons for "441" are 

441 400 Bad file number Writing history file - Throttling
441 400 loadav [innwatch.load] 305 gt 300
441 Can't send connect request to server, No such File or Directory


Thank you, Don, for your kind instruction and suggestion.
For quick study, I phoned my provider but the person on the phone were not
able
to give me the exact reason of the problem with the quoted error remarks.
But I
roughly understood that such trouble may sometimes happy more often when
some free service providers are in between the internet web connection.


This may also sound my provider's commercial explanation.

I will try if this post will be transmitted to your browser with the least
problem.


Don't know about other readers, but I got it fine.
--
Don
Old age is when you start saying "I wish I knew now what I knew then."
ーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーー
You got my last post fine. I'm glad to hear that.
Anyway I've learned some extra way to transmit my post even in such special cases.

There is another strange case in which I won't be able to confirm on my own browser
my own actual post until someone has replied to it. Then I firstly confirm that
my post had actually transmitted thanks to his reference quoting details of my post.

If noboday has replied, I have no ways of confirming my post at the moment. In such
case, someone says that the "second recovering posting" will be OKed.
-------------------------------------------------------------------
B. Ito 

.