B 139.0.2 on Win10 and TB on Android 11.0b2. Yesterday I got an email at 11:42 am. That time shown was consistent across TB desktop, android, and other email systems (e.g… (tuilleadh eolais)
B 139.0.2 on Win10 and TB on Android 11.0b2. Yesterday I got an email at 11:42 am. That time shown was consistent across TB desktop, android, and other email systems (e.g. ipad mail). Then at 3:00 pm I noticed the same email had the arrival time changed to 3:35 pm (so in the future?). The new time shows both on TB desktop and Android, but other email systems (ipad mail, Gmail) still show the original time of 11:42 am.
I opened the email in a text editor. Near the top it says:
Delivered-To: replacename@gmail.com
Received: by (bunch of letters/numbers) with SMTP id z9csp1572268pxu;
Fri, 27 Jun 2025 11:42:33 -0700 (PDT)
X-Received: by (bunch of letters/numbers) with SMTP id d85a73u69752e-4a7fcac4408mr84193.1751049752874;
Fri, 27 Jun 2025 11:42:32 -0700 (PDT)
So that looks correct, as the email first arrived at 11:42 into my inbox.
But further down in the email text file there is:
In-Reply-To: <dc3bf(bunch of letters/numbers)ed74@gmail.com>
From: Shiela <office@business.ca>
Date: Fri, 27 Jun 2025 11:35:51 -1100
X-Gm-Features: Ac12(bunch of letters/numbers)Pb1yxp7nGDpJl8
Message-ID: <CAP6Ti(bunch of letters/numbers)soGigQ@mail.gmail.com>
Subject: Re: Estimate 2806 "2462 Deer Ave"
The date line then says -1100 with a time of 11:35 and the inbox email. So one part says -0700 and another says -1100 for time zone. TB desktop and android reads this second time zone and switched the email in my inbox to read arrival at 3:35 pm whereas other email programs read the first time zone of -7000.
Any ideas of what happened or why TB reads the second time zone where other clients read (correctly) the first?