REPLY: 2:221/360.0 5e42e95c   
   MSGID: 2:221/360.1 5e431a1f   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: hpt/w64-mvcdll 1.9.0-cur 2019-12-05   
   Hi August.   
      
   11 Feb 20 19:50:20, you wrote to Alan Ianson:   
      
    AA>>> Y2K-broken programs have probably left the FTN scene gracefully.   
      
    AI>> I hope so.. but we do have pktdate should the need arise..   
      
    AA> That reminds me, I recently discovered a date problem when I used   
    AA> Tommi's BBS (ie logged in manually) to send a netmail few weeks ago. His   
    AA> Concord BBS software produced a future date of 2056.  LOL   
      
    AA>   Date: Sat, 19 Feb 2056 21:45:16 GMT   
    AA>   Message-ID: <5473$netmail@JamNNTPd>   
    AA>   References: <5470$netmail@JamNNTPd>   
    AA>   X-JAM-From: August Abolins <2:221/360>   
    AA>   X-JAM-To: Martin Foster <2:310/31.3>   
    AA>   X-JAM-MSGID: 2:221/360 1ced0c7d   
    AA>   X-JAM-REPLYID: 2:310/31.3 f99352d3   
    AA>   X-JAM-PID: Concord 0.01 Beta-30d OS/2  ser#cc38c58d   
      
    AA> I should drop by and see if he had a chance to hack netmails with   
    AA> pktdate.   
      
   No, not yet. The problem is still there. Pktdate is able to fix every outbound   
   message but it is not in operation yet.   
      
   Or I can shut down the bbs. :)   
      
   'Tommi   
      
   ---   
    * Origin: Point One, Le Gros-Theil, France (2:221/360.1)   
   SEEN-BY: 1/123 90/1 203/0 221/0 1 6 360 227/114 229/426 1014 240/5832   
   SEEN-BY: 249/206 317 400 280/464 5003 292/789 854 8125 317/3 322/757   
   SEEN-BY: 335/364 342/200 423/81   
   PATH: 221/0 1 292/854 229/426