Maintenance release: Syncplify.me Server! v3.1.21.61

We have just released version 3.1.21.61 of our Syncplify.me Server!

This new maintenance release fixes a bug in the Configuration Manager that prevented the hash code of some CA-issued certifricates (especially wildcard ones) from being calculated. This was just a visualization bug, all certificates were still working correctly in the SFTP/FTP(S) server, but if you use a CA-issued wildcard certificate you might want to install this update.

As usual you can download the latest version from our web site. Thank you!

Maintenance release: Syncplify.me Server! v3.1.20.60

We have just released version 3.1.20.60 of our Syncplify.me Server!

This new maintenance release fixes a bug in the AppendStringToFile function of the event-handling scripting framework. This update is not necessary if you aren’t running scripts containing the above mentioned function.

As usual you can download the latest version from our web site. Thank you!

Maintenance release: Syncplify.me Server! v3.1.18.58

We have just released version 3.1.18.58 of our Syncplify.me Server!

This new maintenance release only features a “cosmetic” change: there is now a button to run the Configuration Manager directly from within the Instance Controller.

As usual you can download the latest version from our web site. Thank you!

Maintenance release: Syncplify.me Server! v3.1.17.57

We have just released version 3.1.17.57 of our Syncplify.me Server!

This new maintenance release fixes a bug in the global speed limit configuration. Under certain circumstances, in fact, only user-specific speed limits were enforced, while global speed limits were ignored; now it’s fixed.

As usual you can download the latest version from our web site. Thank you!

Maintenance release: Syncplify.me Server! v3.1.16.56

We have just released version 3.1.16.56 of our Syncplify.me Server!

This new maintenance release fixes a bug in the FileToString function that was erroneously assuming the file encoding was always UTF. Now the file encoding is properly detected before the “read” operation takes place.

As usual you can download the latest version from our web site. Thank you!

Syncplify.me Server! v4: from Blacklist to Protector!

This article refers to Syncplify.me Server! v4.0, which – at the time the article is being written – is still in beta, and is not yet available for purchase by customers. The purpose of this article is to inform our users about some important upcoming features.

One of the most popular and widely appreciated features of Syncplify.me Server! has always been its powerful and automatic blacklist. The upcoming Synplify.me Server! v4 is going to bring that concept to an even higher level with its Syncplify.me Protector!™ technology.

Protector! is a leap forward versus the blacklist as our users know it. It’s still fully automatic, but its controls are now 10 times more accurate and integrated much deeper in the protocols themselves. If used to its full potential, Protector! can be very harsh, therefore we felt the need to let our users configure its “sensitivity”. It is possible to set Protector! to either one of the following 4 “aggressiveness thresholds”: Continue reading

Maintenance release: Syncplify.me Server! v3.1.15.55

We have just released version 3.1.15.55 of our Syncplify.me Server!

This new minor update (maintenance release) fixes a bug that affected only Windows Server 2012 and 2012R2 and prevented Syncplify.me Server! from correctly identifying overridden home folders for network user.

As usual you can download the latest version from our web site. Thank you!