Great News! After a long development cycle, BPFTP Server Secure Edition is nearing completion! This version includes a significant redesign of the underlying code to support FTP over SSL/TLS via Implicit and Explicit aka FTPS, as well as some UI improvements over the previous versions.
We’d love to hear about your experience with using this version. Your feedback will help to improve the product. Please email me at the following email address: beta [at] bpftpserver [dot] com. When submitting your email, please include enough information for me to understand what you are doing, what you have done, what happens and how that is different than what you expected.
30 Day Beta License Beta Tester-July 2016
This version will replace the version you are running on your computer. If you are running a production server, in which you can not tolerate any problems, please do not use this software. However, if you are interested in Secure FTP aka FTPS aka FTP over SSL/TLS, please give it a shot. In addition, it is possible to have both this BETA version and the current production (More Info).
In some Windows configurations, it might be necessary to enter the license-code via the command-line. Specifically, in Windows Server where “Internet Explorer Enhanced Security” is turned on (More Info: here, here, here, here and here). When IE ESC is turned on, you’ll need to turn it off; this is because the dialog-box that appears for entering your registration code uses the IE WebKit and as a result the links won’t work correctly.
However, you don’t have to disable IE ESC, you can also enter it via the command-line:
1) Start -> Run -> "cmd" (enter)
3) cd "C:\Program Files (x86)\BulletProof FTP Server"
4) Working with a license-code that looks like...
Enter the following command:
bpftpserver.exe QUIETREGISTER John Doe 00012X-8d7DJF2-6F323F-JVQBUA-8DJF3F-28RR4E-02Z6PC-ZXG37G-QBFDH2-NPDPBM-9XS9D9-MPH56G
Today, we are proud to announce a new release of our BulletProof FTP Server for Windows. This release contains several fixes and improvements to the Events Manager -> SMTP and the handling of %VARIABLES when sending emails during OnEvents; like OnFileUpload. This version is a maintenance version of v2014.1.0.21, while v2015.1.0.22 is still in testing (which allows for Secure-FTP and includes a new ftp-engine).
Version 2014.1.2.22 - 2015-FEB-03
A summary of this release comprises of:
- Fixes for Events Mgr -> SMTP and processing of %VARIABLES
x Fixed, + Added, * Improved/Changed, i Information, ! Wish-List from Customers
Version 2014.1.2.22 - 2015-FEB-03
x Fixed: Management -> Events Manager -> SMTP: Added support for %VARIABLE in TO/CC/BCC
x Fixed: Management -> Events Manager -> SMTP: TO was always using the Email address of the sender configured in Management -> Settings -> Email
x Fixed: Management -> Events Manager -> SMTP: BCC/CC was not correctly being used
x Fixed: Management -> Events Manager -> SMTP: Fixed a problem where the last-line of the email body was being duplicated
x Fixed: Management -> Events Manager -> SMTP: Added UUENCODE and max-line-length of 76
x Fixed: Management -> Events Manager -> SMTP: Resolved a problem parsing for the %VARIABLE in the message body. It was output all variables instead
Thank you for your interest in BulletProof FTP Server.
Below is a list of HOWTO articles that have been written over the years to help customers in getting up and running with BulletProof FTP Server. Note: Some of the screen-shots show older versions of the software. The UI hasn’t changed much between different versions, but you might find some of the buttons labeled differently than what appears.
It’s VERY common that people think only one-port is needed for ftp (default: tcp/ip 21). However, this is not true.
FTP requires at least two ports, one for the control-port (used to login and issue commands, default tcp/ip 21) and a data-port (default tcp/ip 30000 to 30100). One data-port is needed for every concurrent data-connection, for this reason we suggest using a range of 100 ports which will handle most needs.
This HOWTO video shows the process of executing the “reload” command at the command line to reload changes made to the USERS file.
1) BPS currently running as a SERVICE
2) Logging into BPS using “ftp.exe”
3) While the ftp-client is still connected
4) Change the “bpftpserver-users.ini” and edit the password
5) Issue the “bpftpserver -reload” command
6) BPS launches another instance to instruct the current instance to reload the configuration
7) The original ftp-client is still connected
8) Disconnect original ftp-client and try to login as old password (doesn’t work, since it was changed)
9) Try to login as the new password, it works.