• Echomail Date Test

    From Michael Batts@21:4/156.1 to All on Friday, June 26, 2020 03:36:18
    Is the date OK?
    --- FreeMail 1.10 alpha-3
    * Origin: The Rock - Spitfire 3.7 - Goshen, IN, USA (21:4/156.1)
  • From Al@21:4/106.1 to Michael Batts on Thursday, June 25, 2020 15:59:58
    Is the date OK?

    It's dated 26 June, 2020 03:36:18 so it seems to come from the future a bit but
    that's livable. It tossed fine here.. :)

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Warpslide@21:3/110 to Michael Batts on Thursday, June 25, 2020 19:05:07
    On 26 Jun 2020, Michael Batts said the following...

    Is the date OK?
    --- FreeMail 1.10 alpha-3
    * Origin: The Rock - Spitfire 3.7 - Goshen, IN, USA (21:4/156.1)

    The date is tomorrow from where I am...

    Jay

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
    * Origin: Northern Realms BBS | bbs.nrbbs.net | Binbrook, ON (21:3/110)
  • From stizzed@21:4/156 to Al on Thursday, June 25, 2020 19:15:05
    On |1525 Jun 2020|08, |15Al |08said the following...

    Is the date OK?

    It's dated 26 June, 2020 03:36:18 so it seems to come from the future a bit but that's livable. It tossed fine here.. :)


    Yeah, thats wierd. It works fine on Riddells board (Leisure Time) but my
    time is in the future. I checked the time on the server and its good. The program is actually timestamping the logfile with the wrong time too:

    ! 26 Jun 20 03:36:18 PKTD Pktdate Rev. 1.5: processing c:\sf\mail\out\0004009C. KT (type: 2+)
    ! 26 Jun 20 03:36:18 PKTD Packet header date (D/M/Y): 25.6.2020 is OK.
    ! 26 Jun 20 03:36:18 PKTD Packet sender: 21:4/156.1
    ! 26 Jun 20 03:36:18 PKTD Msg #001: Date "064983 Jan 22 0655" fixed to "26 Jun 20 03:36:18" (rc 2).
    ! 26 Jun 20 03:36:18 PKTD Keeping a copy of the corrupted PKT as c:\sf\mail\out 0004009C.y2k for manual inspection.

    Now to further investigate where the program is getting that goofy time... ZULU?

    .\\ichael Batts
    a.k.a. stizzed (because, why not?)
    SysOp, The ROCK BBS III

    --- Mystic BBS v1.12 A46 2020/06/11 (Windows/32)
    * Origin: The ROCK III - therockbbs.net - TELNET:10023 (21:4/156)
  • From Al@21:4/106.1 to stizzed on Thursday, June 25, 2020 16:27:00
    Yeah, thats wierd. It works fine on Riddells board (Leisure Time) but my time is in the future. I checked the time on the server and its good. The program is actually timestamping the logfile with the wrong time too:

    Yeah, I saw a message from Leisure Time and it looked OK.

    ! 26 Jun 20 03:36:18 PKTD Msg #001: Date "064983 Jan 22 0655" fixed to "26 Ju
    20 03:36:18" (rc 2).

    Now to further investigate where the program is getting that goofy time... ZULU?

    It looks like it's using UTC or ZULU time for some reason. I wonder if there is
    a TZUTC environment variable set, or if pktdate would use it?

    On my old fashioned BBBS I have to set both TZ and TZUTC so BBBS knows what the
    correct time is.

    --- BBBS/Li6 v4.10 Toy-4
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)
  • From Jikey@21:3/108 to Michael Batts on Thursday, June 25, 2020 17:24:52

    Is the date OK?

    This one looks fine yes..

    --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32)
    * Origin: Buckeye Telegraph (21:3/108)