Subj : FTN Packet's message date question
To   : slacker
From : deon
Date : Wed Dec 11 2024 08:29 am

 Re: FTN Packet's message date question
 By: Digital Man to slacker on Tue Dec 10 2024 12:03 pm

Howdy,

> 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?).

Depending on what you are doing mailer wize, during a BINKP (and EMSI) session, the remote's time is passed to you - from there you know their local time, and I think you'd know whether it was UTC or local.

Example of what I see with clrghouz:

:+ M_NUL [SYS SkyNet BBS] {"pid":6247}
:+ M_NUL [LOC Medellin, Colombia] {"pid":6247}
:+ M_NUL [ZYZ DavidG] {"pid":6247}
:+ M_NUL [TIME Tue, 10 Dec 2024 07:54:14 -0500] {"pid":6247}
:+ M_NUL [VER Mystic/1.12A48 binkp/1.0] {"pid":6247}
:+ M_NUL [BUILD 2023/01/15 15:29:47 Windows/32] {"pid":6247}

So you can see that David is UTC-5 and his localtime. It doesnt help if his packets have been sitting there a while (created hours/days ago) though - so you cant validate the time in the packet by recalculating it.

It might be helpful nonetheless...


...����
--- SBBSecho 3.20-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)