The global configuration settings for file transfers are set in SCFG->File Options.
╔══════════════════════════════════════════════════════════════════════╗ ║ File Transfer Configuration ║ ╠══════════════════════════════════════════════════════════════════════╣ ║ │Min Bytes Free Disk Space 1G ║ ║ │Max Files in Batch UL Queue 25 ║ ║ │Max Files in Batch DL Queue 100 ║ ║ │Max Users in User Transfers 5 ║ ║ │Default Credit on Upload 100% ║ ║ │Default Credit on Download 90% ║ ║ │Leech Protocol Detection <disabled> ║ ║ │Allowed Filename Length 64 characters ║ ║ │Allowed Filename Characters Most ASCII, Including Spaces ║ ║ │Supported Archive Formats zip, z7, tgz ║ ║ │Viewable Files... ║ ║ │Testable Files... ║ ║ │Download Events... ║ ║ │Extractable Files... ║ ║ │Compressible Files... ║ ║ │Transfer Protocols... ║ ╚══════════════════════════════════════════════════════════════════════╝
| Option Name | Description |
|---|---|
| Min Bytes Free Disk Space | Minimum amount of disk space that is necessary for a user to be allowed to upload files. |
| Max Files in Batch UL Queue | Maximum number of files that can be stored in the batch upload queue. |
| Max Files in Batch DL Queue | Maximum number of files that can be stored in the batch download queue. |
| Max Users in User Transfers | Maximum number of destination users in user to user file transfers. |
| Default Credit on Upload | Default credit amount, given upon upload, used for newly created libraries. |
| Default Credit on Download | Default credit amount, given upon download, used for newly created directories. |
| Leech Protocol Detection | If enabled, determines sensitivity to counting/logging potential leeched file downloads. |
| Allowed Filename Length | Maximum uploaded filename length Allowed (in characters). Only 64 characters of filenames are indexed (searchable) and sometimes (depending on the terminal) only 64 or fewer characters of a filename may be displayed to a user. For these reasons, 64 characters is a reasonable maximum filename length to enforce (and thus, the default). The absolute maximum filename length supported is 65535 characters. |
| Allowed Filename Characters | Allowed Characters in Uploaded Filenames: - Safest Subset Only (A-Z, a-z, 0-9, -, _, and .) - Most ASCII Characters, Excluding Spaces - Most ASCII Characters, Including Spaces - Most CP437 Characters, Excluding Spaces - Most CP437 Characters, Including Spaces |
| Supported Archive Formats | This is a list of archive file types (extensions/suffixes, without the '.') that are supported by libarchive for the creation of QWK/REP packets and temporary archives of files for users to download. By default, the supported archive formats are: zip, 7z, tgz. This list has no impact on the types of files allowed to be uploaded into file areas or the ability to view, test, or extract archives of any type. |
This value is the sensitivity of the leech protocol detection feature of Synchronet. If the transfer is apparently unsuccessful, but the transfer time was at least this percentage of the estimated transfer time (based on the estimated CPS of the connection result code), then a leech protocol error is issued and the user's leech download counter is incremented. Setting this value to 0 disables leech protocol detection. This option also allows you to set the minimum amount of elapsed transfer time to be considered for a possible leech download.
Leech protocol programs are file transfer programs (usually using Zmodem technology) that attempt to “fool” the BBS into thinking the file was not successfully transferred, when in reality it was. This is accomplished by the transfer program requesting a reposition (ZRPOS) after the last successful block and then aborting (ZCAN). A file transferred in this manner will not be considered a successful transfer by Synchronet, but will be caught as a possible leech download and notify the sysop (if this option is used).
This feature is also useful for detecting the partial download of image (GIF) files. If you charge your users credits for downloads, this can be a very useful feature in detecting dishonest users. If the user accumulates a large number of leeches (as displayed in User Edit) and the user never successfully downloads a file previously logged as a possible leech download, the user is probably trying to get something for nothing, though this is hard to prove without actually watching the file transfer in progress.