Call now to talk to an automation expert — (512) 345-2211

Change Log

Change Log for Robo-FTP Server v3.2.2 (Released: 2009-03-23)

Back to list of releases


  • Added support for older ssl sites that don't close the data channel correctly, add /allowerrors to FTPLOGON
  • Improved PGP error handling
  • multiline responses are now written to the trace log in their entirety
  • PGP implementation now correctly handles CAST5 symmetrically encrypted files
  • added support for XFTP server's directory format
  • SENDMAIL now writes the smtp transcript to the trace log even upon an apparent success
  • http protocol now supports the referrer request header
  • added event_logonname and event_logonhome variables to all events
  • Changed upload and download events to have event_uploadfile, event_uploadfolder, and event_uploadpath

Bug Fixes

  • GETNEXTFILE no longer descends into directories when /subdirs is specified
  • SSL layer no longer treats a TCP FIN as a correctly closed data channel
  • anonymous logins could fail because the email address provided in the configurator could not be decrypted
  • possible logging error in HTTP stack when there were no cookies
  • configurator and dashboard could not be run at the same time
  • HTTP wouldn't allow ? characters to be used in request uri
  • HTTP only returned the first cookie received in responses in the following requests
  • IFDATETIME and IFDATE were not working when default comparing to %sitefiledatetime
  • SENDMAIL would issue a STARTSSL even if the server didn't advertise it. On some buggy servers this caused undefined behavior
  • AS400 directory parsing could mix up month and day
  • IBM Host features could cause FTPCD to hang
  • standard unix directory listings that printed the month in all lower case were not handled correctly
  • LOGNTEVENT now returns invalid argument when arguments are invalid
  • http no longer sets %uploadsize variable incorrectly to the size of a returned error page
  • fixed a rare buffer overrun in the trace logging
  • fixed a crash that could occur if the DCOM permissions did not allow the server to load correctly
  • improved the ini import used to migrate old 3.1 and before configurations to the new 3.2 server.
  • fixed a bug where the console tried to load RSCommannds.ini when attempting to configure remote server commands security.
  • Listen interface is now correctly displayed in the console.

Need help figuring out where to start?

Our sales staff is available to answer product questions and help you determine if Robo-FTP is a good match for your project.

Call Now: (512) 345-2211