Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!mimsy!nocusuhs!nmrdc1!rdc30 From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) Newsgroups: news.software.b Subject: Re: warning to all sinners in regard to current C News patches Message-ID: <1991Mar28.200952.12309@nmrdc1.nmrdc.nnmc.navy.mil> Date: 28 Mar 91 20:09:52 GMT References: <1991Mar24.220537.14059@zoo.toronto.edu> <1991Mar27.152155.27218@nmrdc1.nmrdc.nnmc.navy.mil> <1991Mar27.190459.9384@zoo.toronto.edu> Organization: Naval Medical Research & Development Command Lines: 34 In article <1991Mar27.190459.9384@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes: >In article <1991Mar27.152155.27218@nmrdc1.nmrdc.nnmc.navy.mil> rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson) writes: >>The following date is unparsable according to Cnews patch 24Mar91: >> >>Mon Mar 25 20:40:20 1991 MET +0100 > >This is not a valid RFC1036 date because it is neither ctime(3) format >(which 1036 encourages you to accept for backward compatibility) nor >RFC 822 format. You can't specify both an alphabetic timezone and >a numeric timezone; it has to be one or the other. > >>"since older software still generates this format, news implementations are >>encouraged to accept this format and translate it into an acceptable format." >> >>Am I correct in assuming that C-News will no longer tolerate this "sin"? > >The quoted phrase refers to ctime(3) format, which this date isn't. > >However, your conclusion -- that C News will not tolerate this date -- >is correct. Thank you for the info, I've passed it on to the author of the offending news software, W-News. He has a real incentive to fix it quick since I transfer news to and from him and quite a few sites behind him in Europe. All articles generated from theses sites using W-News are being dropped on the floor here. One final question: Will C-News accept a 4 digit YYYY field since RFC1036 specifies a 2 digit YY field? -- Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil nmrdc1.nmrdc.nnmc.navy.mil | UUCP: ...uunet!mimsy!nmrdc1!rdc30 AT&T 3B2/600G Sys V R 3.2.2 | BITNET: dobson@usuhsb or nrd0mxd@vmnmdsc WIN/TCP for 3B2 | MCI-Mail: 377-2719 or 0003772719@mcimail.com