Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucla-cs!twinsun!eggert
From: eggert@twinsun.com (Paul Eggert)
Newsgroups: news.software.nntp
Subject: Re: NNTPD hates Message-IDs with TWO '@'s in them. (BIG log file attached to this posting)
Message-ID: <1991Jun18.022244.8086@twinsun.com>
Date: 18 Jun 91 02:22:44 GMT
References: <1991Jun9.232828.17956@europa.asd.contel.com> <5930@gazette.bcm.tmc.edu> <1991Jun13.043253.20660@zoo.toronto.edu> <6014@gazette.bcm.tmc.edu> <1991Jun17.192620.27934@zoo.toronto.edu>
Sender: usenet@twinsun.com
Organization: Twin Sun, Inc
Lines: 23
Nntp-Posting-Host: ata

henry@zoo.toronto.edu (Henry Spencer) writes:

>A superficial reading of 1036's comments on message IDs suggests a loosening
>of rules, although this is arguably contradicted by the phrasing about news
>articles conforming to 822.

Perhaps a superficial reading of 1036 suggests looser rules, but Stan
Barber's more careful reading is the only supportable one.  RFC 1036
emphatically states that every article must conform to RFC 822, and
justifies this restriction at length.  Although it's a natural mistake
to not know that section 2.1.5 of RFC 1036 does not exempt an article
from the overall RFC 822 requirement, this mistake deserves no more
sympathy than the even more natural mistake of not knowing that RFC 822
is amended by RFC 1123.


>(We don't want full 822 message IDs,
>including obscenities like quoted white space, to be legal in news... if
>only because most news systems have never accepted them.)

Fortunately, we don't have to worry about this: RFC 1036 section 2.1.5
clearly allows only non-white-space, printing ASCII characters in a
conforming Usenet Message-ID.