From: daz Date: 2004-06-05T15:03:57+09:00 Subject: Gateway trial - day xxx (was Re: Reply wasn't posted; will test new post) From: "Dennis Oelkers" Newsgroups: comp.lang.ruby Sent: Thursday, June 03, 2004 3:49 PM > > >>- my solution: as mua's are more or less allowed to do whatever they > >> want my fear is that we get more and more of such borderline cases > >> so the only solution is that we establish identical posting policies > >> on both the mailing-list host and the gateway/nntp host we're posting > >> too. > > > > > > The point is that the policy of ruby-talk is quite sleazy whilc > they're very strict for Usenet postings. People can send almost any > garbage to the mailing list if they're subscribed to it and allowed > to post. In my opinion it is the right behaviour to drop any mail > which is not well-formed as soon as possible. > > This leads to the conclusion that we'll either have some sort of > inconsistency between those two medias, or we would have to synchronize > the policies up to a certain point where those inconsistencies converge > against 0. > Hi Dennis, You present a strong defence but I bring some grim prosecution evidence :-| A news posting[1] by Sean Russell to c.l.ruby via Google which has an 'In-Reply-To:' but no 'References:' header (i.e. "not well-formed") which made the trip from Sean's den around Usenet through the gateway and out to the ruby-talk ML[2] like a Ferrari round Nurburgring. The accusation is that your server at news.zrz.tu-berlin.de is applying a filter to outgoing news messages which is of no help to the gateway. > I get a 441 - "Followup without a reference" from http://www.w3.org/Protocols/rfc977/rfc977.html --------------------------------------------------------------- RFC 977 - Network News Transfer Protocol --------------------------------------------------------------- 2.4.2. Status Responses 4xx - Command was correct, but couldn't be performed for some reason. [...] x4x - Posting [...] x8x - Nonstandard (private implementation) extensions [...] 4.7.2. Responses 441 posting failed --------------------------------------------------------------- "Followup without a reference" looks like a private implementation message and error code 48x is provided for use with such extensions. IMHO, the missing postings don't fail - they're denied. Is there any way the g/way can be made exempt from these non-RFC checks ? (e.g. ignore errors_like_that if source == gateway) Your endurance is much appreciated. daz [1] The headers (before mirroring to ML): ================================================================================== Path: internal1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com! nntp.giganews.com!cyclone1.gnilink.net!gnilink.net!news.glorb.com! postnews1.google.com!not-for-mail From: "SER" Newsgroups: comp.lang.ruby Subject: Re: CSV bug? Date: 18 May 2004 06:51:12 -0700 Organization: http://groups.google.com Lines: 9 Message-ID: NNTP-Posting-Host: odah37.prod.google.com Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: posting.google.com 1084888273 29869 127.0.0.1 (18 May 2004 13:51:13 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 18 May 2004 13:51:13 +0000 (UTC) In-Reply-To: <40A9A7EB.3030208@keynauts.com> User-Agent: G2/0.1 Xref: number1.nntp.dca.giganews.com comp.lang.ruby:99924 ================================================================================== [2] After mirroring to ML http://blade.nagaokaut.ac.jp/ruby/ruby-talk/100614