The user administration serves the purpose to let several users access the server and their respective Mail boxes. That makes sense, if the hamster is used for example on a network or for different people to use, you did not like the same computer however that the other one can read your Mails. Everyone, which accesses the hamster, gets an account with user name and password assigned, over which they can log into the hamster.
In the original state there is only the user ' admin ', who
has all rights for this server. With ' ADD' new users can be
created. Hamster asks then first for the user name of the account and
the full name of the user. One click on 'Edit ' opens the
administration of the respective account. By clicking on 'CHANGE ' the password can be changed.
Since version 1.3.5 the following applies: If a user ' NNTP default ' is created with password ' * ', these adjustments are used, if a user tries to announce itself without user names and password at the hamster. Thus it is also possible, without operating for user name/password or to let in this case special restrictions work. (depending on, which are set to options for ' NNTP default ') main concerns that the Newsclient of Netscape, since no password for the new server can be stored there.
|Account: User ID
|The internal ID of the user.
|The users name.
|With click on ' CHANGES ' can the password for this user account be modified.
|The full name of the user (e.g. Hans's Mueller)
|Local NNTP servers
|Here can be determined, which groups of new the user for reading and/or writing for order to be to be supposed. Regular ones of printouts (Regular of expression) can be used.
|It determines whether the respective user is to have a mailbox available or not. This refers to the post office input. Can be assigned to the respective user also local Mail address, which is to be entered in the field under it, separated with blanks from each other. Mails to these local addresses are not sent via SMTP but are kept locally.
|Local SMTP servers
|It determines whether the user can transmit Mails or not.
The only possibility of controlling the access from the outside on the server (to release), is the IPaccess.hst in the hamster master directory. In the default status this file does not exist yet, it must be created thus manually.
In a local network each computer has an IP address, which is entered in this file. It is determined, for which service which rules for which IP addresses to work to be supposed. So that every other computer can access the computer of the hamster, a host file on everyone must exist the computer, into all IP addresses with the respective Aliases is [ c:\windows\hosts for Windows9x and c:\winnt\system32\drivers\etc\hosts for WinNT. ]
NNTP: Local NNTP server
POP3: Local POP3-Server
Smtp: Local SMTP server
MAIL: Local POP3 and SMTP server
ALL: All local servers
RW: Permits reading/writing
WHERE: Permitted only writing
RO: Permitted only reading
WELL: No access permits
|Table, which would be if...
Client can read articles.
Client can read articles and posts.
Client can fetch Mails.
Client can transmit Mails.
Connection is refused.
Example on the basis the standard adjustment:
# treats all local IP addresses like 127.0.0.1:
ALL, WELL, LOCAL ONE, 127.0.0.1
# of full access to all services for local host:
ALL, RW, 127.0.0.1
# of full access to all services for LAN:
ALL, RW, 192,168,0,0, 192.168.255.255
# of full access to all services for selected ADDR meals:
ALL, RW, 11,22,33,44 # John Doe
ALL, RW, 44,33,22,11 # Jane Doe
# only reading access for the new sport for all other addresses:
NNTP, RO, 0,0,0,0, 255.255.255.255
# no access for all other addresses and services:
ALL, WELL, 0,0,0,0, 255.255.255.255