Subj : Re: FTN Packet's message date question
To   : deon
From : slacker
Date : Mon Dec 23 2024 07:23 pm

Thanks for all the info! Sorry for the late reply on this...

I *think* I found the issue at least on some messages. It seems like it might be related to daylight savings and the kludge not getting updated on remote systems.

Example this message from earlier today:
AREA: FSX_STA :: MSG_ID: 21:1/100 67694287 :: FROM: 21:1/100 :: TO: 21:3/193 :: SUBJ: [NET1] Node Queue

FTSC_DATE: 23 Dec 24 23:59:18 :: TZOFFSET: 1200

BBS Log:
[2024-12-23 06:04:11.85648] [13813] [error] Parsed date time: 2024-12-23T11:59:18 is after current UTC date: 2024-12-23T11:04:11 even after TZ correction 1200 :: Using current UTC date for value.

I think coming from hub 1, the TZUTC offset should be 1300 now instead of 1200 for daylight savings, right? If I corrected for 1300, the time would have been valid and just 5 min before the current UTC time when I processed the packet. 

Link to the message on clrghouz: https://clrghouz.bbs.dege.au/echomail/view/635493

I think I might be driving myself nuts for no reason lol. I poll every 30 min so current UTC of processing for received messages should be 'close enough'. I'll also take a look at using the packet date as you mentioned in a previous message. Maybe that would be a better choice than what I'm doing.. but again, I think I might just be over thinking this. :)


--- NE BBS v0.76 (linux; x64)
 * Origin: NE BBS - nebbs.servehttp.com:9223  (21:3/193)

.