Define the events that will trigger automatic server actions, then choose conditions for the events to define the triggers more narrowly.
|
Server |
||
|
Site |
||
|
Connection |
||
|
User |
||
|
File system |
You can set the following events to trigger automatic server actions.
Service Stop – The CuteFTP Server service stops.
Service Start - The CuteFTP Server service starts.
Site Stop – The site is stopped.
Site Start - The site is started.
You can more narrowly define connection events using Connection conditions.
User connect - a user connects to the site (this occurs before log in).
User connect failed - a user attempts to connect and fails (this can occur before log in).
User disconnect - a user disconnects from the site (this can occur before log in).
You can more narrowly define user events using User conditions and Connection conditions.
User account disable - the user account is disabled by the administrator or by the server.
User quota exceeded - the user has taken too much disk space on the server.
User logout - the user closes a session gracefully.
User login - the user logs in to the server.
User login failed - the user attempts an incorrect username or password.
User password changed - the user or administrator changes a user's password.
You can more narrowly define File system events using File system conditions, User conditions and Connection conditions.
File delete - a file is deleted from the site.
File upload - a file is uploaded to the site.
File download - a file is downloaded from the site.
File rename - a file on the site is renamed.
Folder create - a folder is created on the site.
Folder delete - a folder is deleted from the site.
Folder change - a user navigates to a new folder on the site.
Use these conditions to more narrowly define events that trigger automatic server actions.
You can only apply these conditions to Server events.
Service is running – The CuteFTP Server service is currently running.
Service is not running - The CuteFTP Server service is not currently running.
You can only apply these conditions to Site events.
Site is running – The site has already started and is currently running.
Site is not running - The site has already been stopped and is not currently running.
You can apply these conditions to Connection events, User events, and File system events.
a connection is made from a remote IP address that matches a predefined IP address or IP mask.
a connection is made from a remote IP address that does NOT match a predefined IP address or IP mask.
a connection is made to a local IP address that matches a predefined IP address or IP mask.
a connection is made to a local IP address that does not match a predefined IP address or IP mask.
a connection is made on a predefined port.
a connection is made NOT on the predefined port.
a connection is made on one of a predefined range of ports.
a connection is made NOT on one of a predefined range of ports.
an FTP connection has been made or is being used.
a connection has been made or is being used that is NOT an FTP connection.
You can apply user conditions to User events and File system events.
the user account belongs to a specific group or set of groups.
the user account does not belong to a specific group or set of groups.
a user name matches a specific word.
a user name does not match a specific word.
a user name contains a specific string of characters.
a user name does not contain a specific string of characters.
a user account is enabled.
a user account is disabled.
the user belongs to a predefined Setting Level.
the user does NOT belong to the predefined Settings Level.
a user's name matches a predefined name.
a user's full name does not match a predefined name.
a user's full name contains a predefined string of characters.
a user's full name does not contain a predefined string of characters.
the user's description matches a predefined description.
the user's description does NOT match a predefined description.
the user's description contains a predefined string of characters.
the user's description does NOT contain a predefined string of characters.
the user's comment matches a predefined comment.
the user's comment does NOT match a predefined comment.
the user's comment contains a predefined string of characters.
the user's comment does NOT contain a predefined string of characters.
the user's email address matches a predefined address.
the user's email address does NOT match a predefined address.
the user's email address contains a predefined string of characters.
the user's email address does NOT contain a predefined string of characters.
the user's phone number matches a predefined phone number.
the user's phone number does NOT match a predefined phone number.
the user's phone number contains a predefined string of characters.
the user's phone number does NOT contain a predefined string of characters.
the user's pager number matches a predefined number.
the user's pager number does NOT match a predefined number.
the user's pager number contains a predefined string of characters.
the user's pager number does NOT contain a predefined string of characters.
the user's fax number matches a predefined number.
the user's fax number does NOT match a predefined number.
the user's fax number contains a predefined string of characters.
the user's fax number does NOT contain a predefined string of characters.
the location of a user's home folder matches a predefined physical location.
the location of a user's home folder does NOT match a predefined physical location.
the user's home folder is their root directory.
the user's home folder is NOT their root directory.
the user's account has a size limit equal to a predefined size in Kilobytes.
the user's account has a size limit less than or equal to a predefined size in Kilobytes.
the user's account has a size limit less than a predefined size in Kilobytes.
the user's account has a size limit NOT equal to a predefined size in Kilobytes.
the user's account has a size limit NOT less than or equal to a predefined size in Kilobytes.
the user's account has a size limit NOT less than a predefined size in Kilobytes.
the user has used a predefined amount (in kb) of allowed disk space.
the user's filled disk space is less than or equal to a predefined amount (in kb) of allowed disk space.
the user has used less than a predefined amount (in kb) of allowed disk space.
the user has NOT used a predefined amount (in kb) of allowed disk space.
the user's filled disk space is NOT less than or equal to a predefined amount (in kb) of allowed disk space.
the user has NOT used less than a predefined amount (in kb) of allowed disk space.
the user has attempted and failed to login a predefined number of times.
the user's failed login attempts are less than or equal to a predefined number.
the user's failed login attempts are less than a predefined number.
the user has NOT attempted and failed to login a predefined number of times.
the user's failed login attempts are NOT less than or equal to a predefined number.
the user's failed login attempts are NOT less than a predefined number.
the user has permission to change their own password.
the user does not have permission to change their own password.
the user's allowed IP address matches a predefined IP address or set of IP addresses.
the user's allowed IP address does not match a predefined IP address or set of IP addresses.
You can apply file system conditions only to File system events.
the file or folder exists at a predefined virtual location.
the file or folder does NOT exist at a predefined virtual location.
the file or folder exists at a predefined physical location (the full folder path including the file name).
the file or folder does NOT exist at a predefined physical location (the full folder path including the file name).
the file or folder exists in a predefined physical folder (the folder path without a file name).
the file or folder does NOT exist in a predefined physical folder (the folder path without a file name).
the file name matches a predefined string of characters.
the file name does not match a predefined string of characters.
Customizing event rule email notifications
Using an event to trigger a custom command