REPLY: 1:320/219@fidonet 5dc75662   
   MSGID: 2:280/464.47@fidonet 5dc7d614   
   CHRS: UTF-8 4   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
    AL>>> mbcico (the mailer included with MBSE BBS) rejects the M_GOT   
    AL>>> with the 64-bit value and ends up trying to send the file again   
    AL>>> in the next session.  I suspect that ifcico (which mbcico was   
    AL>>> based on) will do the same, although I haven't tested it yet.   
      
    Ol>> Every mailer should reject that M_GOT, the value doesn't make any   
    Ol>> sense.   
      
    AL> Incidentally, I discovered that the timestamp of that file on disk was   
    AL> showing as November 25, 1961, so it should be a negative value.   
    AL> Converting the decimal to hex yields FFFF FFFF F0C4 3650, which in 2's   
    AL> complement notation is -255576496.  A quick Unix time conversion   
    AL> results in Sat 25 Nov 1961 10:31:44 PM UTC.  Therefore, it appears   
    AL> that the value is a correct 64-bit Unixtime for the file timestamp as   
    AL> it was on disk.   
      
   I polled your system with tcpdump running and sent a .pkt from 1966. It looks   
   like a binkd bug to me:   
      
   M_FILE 7eee1e8f.pkt 450 18446744073609551616 0   
      
   instead of   
      
   M_FILE 7eee1e8f.pkt 450 -100000000 0   
      
   --- 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