ROODE@SRI-NIC.ARPA (01/30/84)
I think that a user's time zone should be settable, at least for message timestamps, on a system which serves more than one zone. Thus he should be able to insure that messages will be stamped with the time he was experiencing as he set them. Failing that, maybe the system in Cupertino could keep Eastern time. I know of one information retrieval utility that uses Eastern time on its system (for everyone) allthough it is located in the Pacific time zone. -------
abc@brl-bmd.ARPA (01/30/84)
For what it's worth, I use the sender's date/time field for nearly all the reasons mentioned by others. The application most-often invoked, however, seems to be to identify duplicate messages (suspected) when reading mail. Brint
RICH.GVT@OFFICE-3.ARPA (02/04/84)
I, too, sometimes use the sender's date/time field to get an idea of when the author sent the message, but you must remember that it can't be relied upon because of networking. I, for instance, am in St. Louis on CST but the host I usually send mail from is in Cupertino, CA and is on PST; you will therefore see PST time-stamps on some messages I send (and CST on others, because one of my mail systems allows me to specify which time-zone to use). Seeing PST time stamps on my messages won't much help anyone tell when I sent it (if they want to know if it's too early/late to phone me, or something like tht). -Rich