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