MSGID: 1:320/219@fidonet 5dc01648   
   CHRS: CP437 2   
   TZUTC: -0500   
   TID: MBSE-FIDO 1.0.7.13 (GNU/Linux-x86_64)   
   Hello everybody!   
      
   I have recently noticed that some versions of BinkD are listing a 64-bit value    
   for the Unixtime sent in M_GOT frames acknowledging received files.  This, of    
   course, can cause issues for mailers that are expecting a 32-bit value.    
   FTS-1026.001 (Binkp/1.0 protocol specification) does not specify the size of    
   this field.   
      
   I can see the value of switching to a 64-bit Unixtime; it will solve the    
   upcoming year 2038 problem.  However, if it breaks compatibility with other    
   existing Binkp mailers, we should implement some mechanism to only enable this    
   feature if the remote mailer explicitly supports it.  This could be done with    
   an M_NUL OPT frame sent by mailers that support 64-bit Unixtimes.   
      
   ie: M_NUL OPT TIME64   
      
   Until this frame is received from the remote, it should be assumed that the    
   remote does NOT support 64-bit Unixtimes, and all Unixtimes sent should be    
   32-bit.   
      
   Andrew   
      
   --- GoldED+/LNX 1.1.5-b20180707   
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)   
   SEEN-BY: 1/19 123 16/0 103/705 120/544 123/130 131 132/174 142/926   
   SEEN-BY: 154/10 203/0 221/0 1 6 242 360 227/114 229/101 200 354 426   
   SEEN-BY: 229/1014 230/0 240/5832 249/307 317 261/38 280/464 5003 5555   
   SEEN-BY: 292/854 310/31 320/119 219 322/0 342/200 396/45 423/81 120   
   SEEN-BY: 640/1384 712/848 770/1 2452/250   
   PATH: 320/219 221/1 280/464 229/426