Hello Oli!

08 Nov 19 08:39, you wrote to me:

 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.

 Ol> Which versions do this and what bit width is used with the M_FILE
 Ol> command?

Here is the log from an example session:

=== Cut ===
  09-Nov-2019 05:40:20 mbcico[11948] MBCICO v1.0.7.13
  09-Nov-2019 05:40:20 mbcico[11948] Cmd: mbcico f126.n1.z21.fsxnet
+ 09-Nov-2019 05:40:20 mbcico[11948] Options: Call WaZOO EMSI Freqs Zmodem 
ZedZap Hydra PLZ GZ/BZ2 NoNR CRC
+ 09-Nov-2019 05:40:20 mbcico[11948] Calling 21:1/126@fsxnet (HappyLand BBS, 
phone (null))
+ 09-Nov-2019 05:40:20 mbcico[11948] Open TCP connection to 
"magickabbs.com:24554"
+ 09-Nov-2019 05:40:21 mbcico[11948] Trying IPv4 103.43.75.189 port 24554
+ 09-Nov-2019 05:40:21 mbcico[11948] Established IBN/TCP IPv4 connection with 
103.43.75.189, port 24554
+ 09-Nov-2019 05:40:21 mbcico[11948] GeoIP location: Australia, AU OC
+ 09-Nov-2019 05:40:21 mbcico[11948] Start outbound Binkp session with 
21:1/126@fsxnet
+ 09-Nov-2019 05:40:21 mbcico[11948] Binkp: start session
+ 09-Nov-2019 05:40:21 mbcico[11948] Binkp: node 21:1/126@fsxnet
+ 09-Nov-2019 05:40:22 mbcico[11948] Options : 
CRAM-MD5-9258b98853ea366d0a156189662da0ee
+ 09-Nov-2019 05:40:22 mbcico[11948] System  : HappyLand
+ 09-Nov-2019 05:40:22 mbcico[11948] Sysop   : apam
+ 09-Nov-2019 05:40:22 mbcico[11948] Location: Toowoomba, QLD
+ 09-Nov-2019 05:40:22 mbcico[11948] Flags   : 115200,TCP,BINKP
+ 09-Nov-2019 05:40:22 mbcico[11948] Time    : Sat,  9 Nov 2019 20:40:21 +1000
+ 09-Nov-2019 05:40:22 mbcico[11948] Uses    : binkd/1.1a-99/Linux binkp/1.1
+ 09-Nov-2019 05:40:22 mbcico[11948] address : 21:1/126@fsxnet
+ 09-Nov-2019 05:40:22 mbcico[11948] address : 77:3/103@scinet
+ 09-Nov-2019 05:40:22 mbcico[11948] Options : EXTCMD GZ
+ 09-Nov-2019 05:40:22 mbcico[11948] Binkp: EXTCMD is active
+ 09-Nov-2019 05:40:22 mbcico[11948] Binkp: GZ compression active
+ 09-Nov-2019 05:40:22 mbcico[11948] Binkp: MD5 unprotected session
+ 09-Nov-2019 05:40:22 mbcico[11948] Binkp: mail 0, files 21096 bytes
+ 09-Nov-2019 05:40:22 mbcico[11948] Binkp: send 
"/opt/mbse/var/inbound/zip/SIOREG.ZIP" as "SIOREG.ZIP"
+ 09-Nov-2019 05:40:22 mbcico[11948] Binkp: size 21096 bytes, dated Nov 25 
17:31:44, comp No
+ 09-Nov-2019 05:40:22 mbcico[11948] Binkp: OK 21096 bytes sent in 0.006 
seconds (3433.594 Kb/s)
+ 09-Nov-2019 05:40:22 mbcico[11948] Binkp: M_GOT "SIOREG.ZIP 21096 
18446744073453975120"
+ 09-Nov-2019 05:40:22 mbcico[11948] Binkp: unexpected M_GOT "SIOREG.ZIP"
=== Cut ===

I need to add logging of the sent M_FILE messages to confirm that mbcico is 
sending a 32-bit value in the M_FILE.  You can see that the remote (binkd 
1.1a-99/Linux) is sending a 64-bit value for the Unixtime in the M_GOT frame.

I suspect this is dependent on the particular Linux distribution in use and if 
the __WORDSIZE_TIME64_COMPAT32 is defined when compiling the system's glibc.

 Ol> Does it break compatibility with any mailer? You didn't mention any
 Ol> specific example.

mbcico (the mailer included with MBSE BBS) rejects the M_GOT with the 64-bit 
value and ends up trying to send the file again in the next session.  I 
suspect that ifcico (which mbcico was based on) will do the same, although I 
haven't tested it yet.

Andrew

--- GoldED+/LNX 1.1.5-b20180707