Xref: utzoo news.software.nntp:1407 news.software.b:8304
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!bcm!tmc.edu!sob
From: sob@tmc.edu (Stan Barber)
Newsgroups: news.software.nntp,news.software.b
Subject: Re: NNTPD hates Message-IDs with TWO '@'s in them.
Message-ID: <6038@gazette.bcm.tmc.edu>
Date: 18 Jun 91 03:50:15 GMT
References: <1991Jun15.212751.1558@twinsun.com> <6020@gazette.bcm.tmc.edu> <1991Jun17.191642.27639@zoo.toronto.edu>
Sender: usenet@bcm.tmc.edu
Followup-To: news.software.nntp
Organization: Baylor College of Medicine, Houston, TX
Lines: 30
Nntp-Posting-Host: tmc.edu

In article <1991Jun17.191642.27639@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
>C News doesn't do 100% RFC822/1036 header enforcement because that is
>complex and time-consuming and unnecessary.  We generally enforce only
>those restrictions that appear to be necessary for some specific reason.
>(In the case of dates, it is essential to have a parsable date to avoid
>recirculation of stale news.)  We are somewhat reluctant to tighten up
>checking just because somebody else's software is breaking -- we tend
>to feel that this is the breakee's problem -- although we have done so
>on occasion.

I see.

I guess this means that badly installed CNEWS sites are no cause for 
concern.

It is interesting to hear that a CNEWS author considers to be irrelevant
if implementing the standard is too hard or too complex. 

However, I do believe we now have seen a case where it is necessary. 
There is news posting software out there that generates bad message-ids.
This should be stopped by the news transport software.

Otherwise, USENET will eventually stop transporting some news....Ummm.
Actually, I guess this has already happened.


-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: rutgers!bcm!sob             and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine