Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 Apollo 4/10/84; site apollo.uucp Path: utzoo!linus!decvax!wivax!apollo!rees From: rees@apollo.UUCP Newsgroups: net.news.b Subject: Case sensitivity in message-ID? Message-ID: <202b777f.1147@apollo.uucp> Date: Mon, 25-Jun-84 09:10:58 EDT Article-I.D.: apollo.202b777f.1147 Posted: Mon Jun 25 09:10:58 1984 Date-Received: Tue, 26-Jun-84 06:21:02 EDT Organization: Apollo Computer, Chelmsford, Mass. Lines: 31 I recently got two articles with the following message-ids: <300@oddjob.UCHICAGO.UUCP> <300@oddjob.UChicago.UUCP> My news software rejected the second as being a duplicate of the first. I don't consider case to be significant in the "domain" part of the message-id. Apparently other 2.10 implementations do, or I would never have gotten both of these (we are a leaf node). The standards say this about message-ids: In order to conform to RFC 822, the Message-ID must have the format "<" "unique" "@" "full domain name" ">" where ``full domain name'' is the full name of the host at which the article entered the network, including a domain that host is in, and unique is any string of printing ASCII characters, not including "<", ">", or "@". RFC822 makes it clear that case is not significant in the "domain" part of a message-id. Because my software rejected the second article, I don't know whether the two were identical. How were these two article IDs generated? Were the articles themselves the same? Should news 2.10 implementation consider case significant or not in message-ids?