Global events, whereby actions such as messages to the FTP client, email messages to the Server Administrator or sounds on the server can be configured in response to various events, such as users logging onto the server, uploading or downloading files.
This is identical to events configured user by user, and if there is a conflict, the User Event will supersede any Global event configured here.
CAUTION - Do not configure Actions for Events that may be triggered very often, for example if an attack is mounted on FileCOPA. If the server is flooded with Connects or Bad Logins, then a continuous sound or 1000 email messages may not be welcome!
The Event On Failed Login (introduced with Version 6) is best used as a User Event, rather than as a Global Event. An attack which floods the server with a string of usernames and passwords would repeatedly trigger this Event, and could, for instance, send hundreds (or even thousands of email messages).
Data that can be inserted in messages
Note that some options may be disabled where they are not appropriate to the context.
Client's IP Address |
Long Date |
Client's Host Name |
Filepath |
Username |
Filename |
Time |
Old filename |
Date |
Transferred Data Size |
The Short Date Format for events is taken from the System Time Format, not from the user's configuration. The two may coincide, or they may not!
System Time Format is defined in a Registry entry:
HKEY_USERS\.DEFAULT\Control Panel\International\sShortDate
For US Date Format this should be MM/dd/yyyy
For UK (and most other countries) Format this should be dd/MM/yyyy