Xref: utzoo news.software.nntp:1400 news.software.b:8290
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!rutgers!ucla-cs!twinsun!eggert
From: eggert@twinsun.com (Paul Eggert)
Newsgroups: news.software.nntp,news.software.b
Subject: Re: NNTPD hates Message-IDs with TWO '@'s in them.
Message-ID: <1991Jun16.224724.4234@twinsun.com>
Date: 16 Jun 91 22:47:24 GMT
References: <1991Jun13.043253.20660@zoo.toronto.edu> <6014@gazette.bcm.tmc.edu> <1991Jun15.212751.1558@twinsun.com> <6020@gazette.bcm.tmc.edu>
Sender: usenet@twinsun.com
Organization: Twin Sun, Inc
Lines: 14
Nntp-Posting-Host: ata

sob@tmc.edu (Stan Barber) writes:

>This is inconsistant. If CNEWS is discarding articles with bad dates ...
>then it should do that for all headers.

Actually, C News is consistent in not checking for complete RFC conformance.
It doesn't check _dates_ completely either; e.g. it accepts nonconforming dates
like `Sonntag, 16 Jun 91 22:47:05 GMT'.

It would be tricky and a little expensive for C News to check for complete
conformance to the RFCs, because the rules are so convoluted.  C News does the
checking that's cheap and easy, and doesn't bother with the rest.  Alas,
this means C News can output a non-RFC-conforming article that was originally
posted from another host.