Frank Slootweg <th...@ddress.is.invalid> wrote:
>>>>Injection-Date: Fri, 01 Jan 2021 11:21:35 +0000 <----
>>The problem as I see it is Google puts their timezone
>>(PST) into the 'Date' header
> If 'notyalckram' is a UK poster, that's indeed a silly thing to do for
No, it's not, for Google Groups doesn't allow the user to state local
time. From the perspective of Google Groups, local time with
respect to Google headquartes is -0800/-0700. Google Groups is just a
Web interface. The client is remote to the user.
>>and adds an 'Injection- Date' header with the posters timezone which
> The 'Injection-Date' header is indeed reported in UTC, but that does
>not mean that the poster lives in the UTC timezone. . . .
+0000 is a statement that UTC is used as local time, like GMT as one's
local time zone. -0000 is UTC without reference to local time.
> All in all, I think that as - as I described before - 'Date' and
>'Injection-Date' contain the exact same time, it looks like Gravity can
>not handle the syntactically correct 'Date' header. That's rather
>strange, because using a timezone code like '(PST)' is long standing
It's in parentheses and MUST BE ignored as a comment. As you and others
correctly pointed out, the four digit time zone offset is standard and
that's what Gravity has failed to parse.
PST, not in parentheses, is the time zone offset obsoleted by RFC 2822. RFC
822 had multiple standard ways of expressing the time zone offset and
notoriously misstated single letter military time zones.
>>. . .