Setup of the FTP Server is done in the section FTPserver and is in many respects similar to that of the Web Server. The default directory is ftproot. Virtual directories can be created.   (03.08.1999) 

Eserv saves logs in files with names of the type LOG\MMDDPROT.LOG, where MM is the double-digit month number, DD is the date, and PROT is the name of the server protocol that makes records in this log (http, ftp, socks, pop3, smtp, nntp) or the name of the service (sch: Scheduler log, eserv: Eserv’s basic flow log).

Records in a log look like text lines of the following format: hh:mm:ss nnn info, where hh:mm:ss is the time of the event, nnn is the serial number of the flow and info is a description of the event.

Eserv can keep logs of various levels of detailing. The existing levels and their assignments are:

0 - minimum; the most important messages are entered only; 
1 - starts and stops of services are entered; 
2 - client connections are entered (only facts of connection); 
3 - connections and character of inquiries are entered; 
4 - creation of flows for clients are entered; 
5 - protocol details of work with a client program are entered; 
6 - transmitted information (except HTTP files) is entered; 
7 - transmitted HTTP and FTP information is entered. 

The resolution (level of detailing) is set up in the field CommonSettings/LogFiles/LogLevel. Level 3 means log file record of events of levels 0,1,2 and 3.

Logs can be automatically deleted by Eserv when the age of a particular log exceeds the number of days set in the parameter KeepLogsDays. This is done by the Scheduler. If there is no such task in the Scheduler, Eserv will check the age of logs and delete old ones only at the moment of starting.   (24.11.1999) 

Eserv servers can be the objective of intruders as an intermediate vehicle for their traffic (proxy servers, SMTP Server, etc.) and as an information objects (NNTP Server, HTTP Server and FTP Server).

Access control facilities are provided for:

• Prevention of unauthorised access to files (mailboxes, news groups, contents of the HTTP Server and the FTP Server);
• Prevention of unauthorised access to Eserv services.

Correspondingly, external user access can be limited in a number of ways:

1. Making it thoroughly impossible to contact Eserv servers from any or some external networks, i.e. setting up the server for reception of connections outgoing only from the LAN (6.9.1).
2. Granting access to a limited and known circle of users on the basis of name and password authentication (6.9.2).
3. Making a part of the connection information unknown for external users, e.g. establishing non-standard port numbers (for more detail see 6.9.3.).

In Eserv, subnet restrictions are applied to all servers in the set. Setup is done in the section CommonSettings/AccessRight/AllowAddressesConnection. The options include a list of network masks granted access to the services of the server.

For instance, if you wish to grant access to the services of a server only to clients from the local network, and IP addresses in your local network look like 10.1.1.*, you can add a mask

10.1.1.0 255.255.255.0

To do this, enter the string 10.1.1.0 255.255.255.0 in the editing field below and click the Add button. The default mask is 0.0.0.0 0.0.0.0 - access is granted to anybody.   (03.08.1999) 

• Access to user mailboxes is granted to users (user programs) who have passed name and password authentication by the POP3 protocol;
• Access to files on the FTP Server is granted to users who have past name and password authentication by the FTP protocol;
• Access to news groups can be limited.
• Access to files on the HTTP Server is granted to users who have past name and password authentication by the HTTP protocol;

For all Eserv servers the program keeps a general list of users and a list of groups. These lists are kept in the sections CommonSettings/Users and CommonSettings/UserGroups.

To add a new user, enter his or her name in the editing field and click the Add button or the New icon. Then go to the section of this user and enter their password and other attributes.

To add a group, enter its name in the editing field and click the Add button or the New icon. Then enter the created group and in a similar way add the names of the users included in this group.

Group access to specific objects is set in the section Access_Right/Objects. This section has the form of a list. Each element of the list describes attributes of a certain object and a list of groups granted access to it. Addition of elements in this list is done similarly to that in user and user group lists. Object - is a path to diectory. For example, wwwroot\admin\ - folder on the web-server. In the object section you can insert list of users of groups to whom access is granted or denied. If access is grantet to all server users (having own mailboxes) - you can specify AllUsers predefinded group. If for anybody (including extern users and users with wrong names:passwords) - the group 'All'.

In Eserv, some of the objects (mailboxes) have pre-set access and do not need to be set up, as the name of the object coincides with the name of the user. Access for other objects, i.e. directories and files on the HTTP and FTP servers, news groups and proxy servers, is set in the Setup Program.

There is no need to set access to objects not included in the terms of reference of Eserv. For instance, there is no need to define access to directories and files outside the wwwroot and ftproot directories and virtual directories, as Eserv does not grant access to files located beyond these anyway.

The name of group or user, who granted to access to this resource (object) is entered in the left side (Property field). In the right side you must enter the access code. Code is calculated by bit mask DLRWX. D- user have the rights to Delete object
L - rights to List object's content (FTP list, for example)
R - rights to Read object
W - rights to Write and create objects
X - rights to eXecute object (for script folders of the Web-server)
Examples:
All 1 - anybody can access this resource as script (run this script) - this is suitable for public cgi-bin directory.
All 12 - all users have rights to list and read folder contents. Suitable for 'pub' directory of anonymous FTP.
Administrators 30 - users from Administrators group have full access rights, including write and delete, excluding execute.

If you want to restrict users access to your Eserv HTTP-proxy, you can add the object "http://" and in the access list of this object add the list of users and groups, who granted the access. In this case browsers will popup dialog boxes for username and password to access proxy.

If you want to restrict access to newsgroups - add the newsgroups names in the objects lists and enter the access list. In this context right W means user can post messages to this group, and R - user can read the messages from newsgroup.

You can use wildcards ("*" and "?") in the object names.  (24.11.1999) 

Eserv can support any number of interface languages. Translation into another language is done through translation of a simple text file containing Eserv messages. Persons and companies interested in translation of the interface and documentation into other languages are welcome to contact the developers.   (03.08.1999) 

To load a plugin, click the icon LoadPlugin, select the plugin file and click OK.

It is possible to use plugins, which will be autoloaded when Eserv started. These plugins must be saved to the plugin folder and have file name 'autorun*'.

So far, the Eserv plugin interface has not been described, and it is assumed that you will use the plugins offered by the Eserv developers. However, should other developers express interest, the interface can be uncovered in the future.   (24.11.1999)