REPLY: 1:320/219@fidonet 5dc01648   
   MSGID: 2:280/464.47@fidonet 5dc51bc5   
   CHRS: UTF-8 4   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
    AL> I have recently noticed that some versions of BinkD are listing a   
    AL> 64-bit value for the Unixtime sent in M_GOT frames acknowledging   
    AL> received files.   
      
   Which versions do this and what bit width is used with the M_FILE command?   
      
    AL> This, of course, can cause issues for mailers that   
    AL> are expecting a 32-bit value. FTS-1026.001 (Binkp/1.0 protocol   
    AL> specification) does not specify the size of this field.   
      
    AL> I can see the value of switching to a 64-bit Unixtime; it will solve   
    AL> the upcoming year 2038 problem.  However, if it breaks compatibility   
    AL> with other existing Binkp mailers, we should implement some mechanism   
    AL> to only enable this feature if the remote mailer explicitly supports   
    AL> it.   
      
   Does it break compatibility with any mailer? You didn't mention any specific   
   example.   
      
   --- GoldED+/LNX 1.1.5-b20180707   
    * Origin: * nigirO (2:280/464.47)   
   SEEN-BY: 1/123 90/1 103/705 154/10 203/0 221/0 227/114 229/101 200   
   SEEN-BY: 229/354 426 1014 240/5832 249/307 317 280/464 5003 5555 292/854   
   SEEN-BY: 310/31 342/200 396/45 423/120 712/848 770/1 2452/250   
   PATH: 280/464 229/426