Subj : FTN Packet's message date question
To   : slacker
From : Digital Man
Date : Tue Dec 10 2024 12:03 pm

  Re: FTN Packet's message date question
  By: slacker to All on Tue Dec 10 2024 02:49 pm

 > Hi All,
 >
 > I'm trying to make sure that I'm importing messages with the right date and
 > time based on the message date as well as the TZUTC kludge. What I noticed
 > is that not all messages have a TZUTC kludge and the date of the message is
 > given in their local time.

That's right. It's dumb, but it's right. :-)

 > I've also noticed that some messages have a TZUTC kludge but after adjusting
 > the date of the message to UTC based on that, sometimes the date is still a
 > little ahead of UTC. I'm guessing perhaps that one is just due to drifting
 > origin BBS server times.

The *date* is ahead, or the *time* is ahead? If the time is ahead, I'd say yeah, drift, but if your *hours* off (enough to put you into a future date), then I'd say eitehr the originating system is misconfigured or someone is modifying the date or TZUTC value of the message in-flight.

 > Anyone have an idea how to parse the date when no timezone info is given? Am
 > I thinking to much about this and should just be using the date when I
 > import the message into my BBS instead of the actual message's date?

When no timezone info is given, the best you can do is guess that it's either UTC or *your* local timezone. Unless you have some other way to know/guess the originator's timezone (nodelist maybe?).
-- 
                                            digital man (rob)

Rush quote #5:
Some are born to rule the world, to live their fantasies
Norco, CA WX: 70.0øF, 7.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs

.