mdtm bug

I read about the bug in the following thread:
https://www.smartftp.com/forums/keep-fil ... t8180.html
There's a link to a development version, but it doesn't work.

One of my users needs to upload large files to my FTP server, and I can tell from the server logs that SmartFTP is causing trouble. It sends a MDTM to the server, thinks the file is too new and instead of resuming the transfer, it tries to *RESTART* the transfer from the beginning which is really nasty. Thankfully, my server is configured not to allow them to be overwritten.

Is there any setting that can be configured in SmartFTP to work around this particular bug?
(Anything except changing timezones/times manually)
Or is there a beta version available somewhere that fixes this bug?

Incomplete bug report. Post logs and the system information.

Thanks
-Mat
SmartFTP


Incomplete bug report. Post logs and the system information.

Thanks
-Mat
SmartFTP

Is that a joke? I gave you a link to a post which you personally confirmed is a bug.
I need to know if there's a work around or a beta/dev/whatever version that is not affected by it.

Please read the thread more thoroughly, the bug was fixed. The issues discussed further down in the thread were based on user configuration errors.