news.software.readers

Frank Slootweg's response:

> -Lost wrote:
> [deleted]
>
>> I wonder this though, is it stil considered broken in this case:
>>
>> NNTP-Posting-Date: Sun, 29 Feb 2004 15:38:32 -0600
>> Date: Mon, 28 Dec 2015 16:38:17 -0500
>>
>> The actual time the message was posted is dated correctly. It is the
>> date header that is screwed. Does this still make the news server
>> broken?
>
> Yeah, like Whiskers, I consider this to be seriously broken. The
> "Date:" header is a required header and it should be correct. The
> server can either reject a posting with a bad "Date:" header or
> rewrite the header with the correct/current date/time. If it wants to
> play nice, it can report *that* in a special (X- [1])
> header, . the *opposite* of what GigaNews is doing.
>
> I haven't checked the most current formal status of
> "NNTP-Posting-Date:", if any, but normally it's used to give the real
> posting date/time of *slightly* *old* postings, . for example those
> who are posted by an offline newsreader (but with a "Date:" header).
>
> So bottom line: GigaNews *can* (as in: is allowed to) generate a
> "NNTP-Posting-Date:" header, but *should not* accept articles with a
> "Date:" far in the future.
>
> [1] For example the moderator-bot for the
> group uses "X-Original-Date:".

Noted and archived. Thanks.

--
-Lost
Remove the extra words to reply by e-mail. Don't e-mail me. I am
kidding. No I am not.