Hellow Andy, Andy Smith <[email protected]> writes:
> Hi, > > On Fri, Feb 13, 2026 at 11:09:45AM +0900, Byunghee HWANG (황병희) wrote: >> <quote: from Gmail Inbox> >> Received: from yw-1204.doraji.xyz (yw-1204.doraji.xyz. >> [2a03:ebc0:5000:12::10]) >> by mx.google.com with ESMTPS id >> ffacd0b85a97d-43796a60b98si1372478f8f.41.2026.02.12.16.42.29 >> for <[email protected]> >> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); >> Thu, 12 Feb 2026 16:42:29 -0800 (PST) >> </quote> >> >> As above sample, mx.google.com use PST as timezone. >> Will it be okay if i change the time zone to PST? > > This header is added by Google's infrastructure as the mail comes in to > them. No matter what time zone you use on your computers, those headers > wuill continue to say PST. It doesn't matter what you do, so [continue > to] use a time zone that makes sense for you. > > Thanks, > Andy > > PS multiple Google employees have told me informally that the decision > to use PST time zone on their servers is regarded as a mistake by > many there. It's common to advocate for UTC on servers, for many > reasons such as; having end users all over the world who see logs and > headers in a time zone like PST which they may be less familiar with > than UTC; picking a time zone that does daylight savings adjustments > twice a year is unnecessarily confusing; and so on. On desktops, > especially single user machines, it is more firmly a personal choice. Oh very cool information... Maybe i'll have to stick with UTC timezone for a while, thanks a lot for your reply. Sincerely, Byunghee
signature.asc
Description: PGP signature
