On Tue, 2021-07-13 at 05:30 +, Trigon via agora-business wrote:
> I call the following CFJ: This CFJ was called on 13 Jul 2021.
>
> Caller's Evidence: This message sure seems to think so.
>
> So as not to be dinged for No Faking, it is completely possible that
> nothing here worked.
Gratuitous evidence:
>From the headers of the above-quoted message:
> Received: from localhost ([73.127.1.41])
> by smtp.gmail.com with ESMTPSA id k189sm16420598pgk.14.2021.07.11.22.30.52
> for
> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);
> Sun, 11 Jul 2021 22:30:52 -0700 (PDT)
> Message-ID: <60ebd38c.1c69fb81.da881.1...@mx.google.com>
> Date: Tue, 13 Jul 2021 05:30:00 +
These headers are out of order (the Date timestamp should precede every
Received timestamp, or at most be out by a few seconds due to clocks
not being synchronized), implying that at least one of them was forged.
(I strongly suspect it's the Date header, given that 13 Jul 2021 hasn't
happend yet.)
Gratuitous arguments:
I think there's a difference between the situation where an email
header "looks" genuine, and one which has been provably forged. In the
latter case, the contradiction within the email headers means that the
message is failing to clearly state the date on which it was sent. It'd
be like trying to take an action by announcement, "I do X but do not do
X", which I would expect to unambiguously fail.
This may cause some complication determining the exact moment at which
the email was actually sent, but it clearly wasn't tomorrow.
--
ais523
