Why didn’t I receive a reply to my support request email?

Here at Syncplify we take your support requests very seriously, and we always reply. Usually within 2-4 hours, and never beyond the second business day.

Sometimes, though, the requester does not receive our reply. Here’s a list of some of the most common causes:

1) Wrong requester e-mail address

Believe it or not, the most common reasonĀ for not receiving a reply from our support team is that you have mistyped your own email address while filling in the support request form. If you type john.doe@gmil.com (instead of gmail.com) we hit the “reply” button, and then get an “undeliverable” back from the server.

2) Your antispam rejects our reply

Sometimes we spend a lot of time typing a reply, just to find out that when we finally hit “send”, we receive an error like this:

554 5.7.1 <support@syncplify.me>: Sender address rejected: Blocked by this recipient

If you send us a support request, and wish to receive our reply back, please, make sure your antispam isĀ not rejecting emails coming from the syncplify.me domain name. We never spam anyone, so whitelisting our domain name is a safe choice. Continue reading

Scripting lesson: email a list of all uploaded files

Syncplify.me Server! version: 3.1.21+

One of the ready-made script examples that is installed along with Syncplify.me Server! shows how to notify someone via email each time a file is uploaded. But what if you wanted to send only one email, at the end of the file transfer session, with the list of all files that were uploaded in such session?

You can easily do that with 2 simple scripts bound to 2 different event handlers.

First of all you will need a script bound to the “AfterFileUpload” event handler, to keep the list up to date:

Continue reading

Receive a notification email when someone tries to log in

A very common request from our customers is to be able to receive an email notification whenever someone tries to log into their FTP(S)/SFTP server with the wrong credentials.

You can do that by taking advantage of the new “after a failed authentication” event handler that we’ve introduced in Syncplify.me Server! version 1.0.5.15. Here is how to do it:

Continue reading