Certain File Storage names have special meanings.
empty: An empty-name file is retrieved via HTTP when no file name is specified in the Access URL, such ashttp://server:port/~username, or http://server:port/~username/subfolder/
In this case, a file with a predefined name is retrieved. This predefined name is set as an Account Setting, and is usually set to default.html. So, an HTTP retrieval request for the http://server:port/~username/subfolder/ URL produces the same result as the http://server:port/~username/subfolder/default.html request.
freebusy.vfb: This text file contains the user Free/Busy information. When the Account Main Calendar is modified with the CommuniGate Pro MAPI module, XIMSS interface, or AirSync, CalDAV, or the WebUser Interface module, the file is deleted. When this file is being accessed and it does not exist, the Server opens the Account Main Calendar, builds the Free/Busy information, and stores the information in the freebusy.vfb file. If the Free/Busy information cannot be built (for example, if no Main Calendar Mailbox exists in the Account), the HTTP module generates an empty Free/Busy dataset and sends it to the client.
any_name.meta: these names are reserved and cannot be used.
private/logs/calls-yyyy-mmm: These text files are created and filled with the Signal Dialog objects. yyyy is a 4-digit year number, and mmm is a 3-letter month name. Each file record has tab-delimited fields and contains information about one call made from or to the Account.
private/IM/userName@domainName.log: These text files contain Instant Messages send to and received from the userName@domainName address. Each Instant Message is stored as one text line, with the following tab-delimited fields:
Note: names starting with the tilda (~) symbol are used to specify Foreign Files, and, as a result, this symbol cannot be used as the first symbol of a file nam