AL> The file had a timestamp of 01-01-1998 on my OS/2 system;
 AL> somehow the timestamp got grunged when I sent it over to the Linux
 AL> machine using binkd 1.1a-99/OS2.  I just tried sending it again, and
 AL> the same timestamp corruption occurred.

It's getting weirder ...

 Ol>> now. The question is which of the two mailers doesn't handle the
 Ol>> negative unix timestamp well.

 AL> Yes, and also the 64-bit vs. 32-bit question.  I'll work on further
 AL> testing today.

I don't see a 32-bit vs. 64-bit question at the binkp protocol level. It's just
an ASCII string. Fun fact: FTS-1026 uses a number in the examples that cannot
be encoded in 32-bit.

M_FILE "config.sys 125 2476327846 100"

2476327846 -> June 21, 2048 4:50:46 AM

--- GoldED+/LNX 1.1.5-b20180707