Use this form to configure the Finger and LDAP protocols and to set up Internet aliases. You do not have to modify the protocols unless you have an unusual Internet setup.
Use this tab to configure the Finger protocol.
The TCP port to which Finger users will connect. Normally, you will accept the default 79. Do not change this port number unless advised to do so by your LAN administrator.
The time the server will wait for a Finger request before disconnecting the remote user.
Use this tab to configure the LDAP protocol.
The TCP port to which LDAP users will connect. Normally, you will accept the default 389. Do not change this port number unless advised to do so by your LAN administrator.
The time, in minutes, the server will wait for an LDAP request before disconnecting the remote user.
Enable a security certificate for the LDAP Directory protocol.
The ISO code for your country.
Your organization's name.
A name describing the members of your organization who use this server (for example, Administration).
Use this tab to indicate what to use as Internet aliases.
The ASCII character you want to substitute for a space in a user name when translating it into an Internet address. For example, the FirstClass user name Roy Allen is unacceptable as an Internet address because of the space. If you choose _ as the space character, Roy's Internet address will be Roy_Allen@centrinity.com.
You can also define an Internet mail alias on a user's information form. In that case, the alias will be used and the space character substitution ignored.
FirstClass can generate users' Internet aliases automatically in two ways. If you choose user IDs as aliases, the aliases are the same as users' user IDs. This guarantees unique aliases, but exposes FirstClass user IDs and therefore reduces the security of your system. If you choose initials and last names as aliases, an alias consists of the first character of the first name plus the last name (for example, James Lee Brown would have the alias jbrown). This is not guaranteed to be unique. Because user IDs must be unique, you will then have to check for duplicates.
If you specify that no automatic aliases are to be created, mail sent to the Internet will be seen to come from an address such as:
The sender's name will be whatever auto matches in the Directory.
You can override the Internet alias generated for a user by updating the "Mail aliases" field on the user information form for that user. In addition, users with the Edit user information privilege can add their own aliases on this form.
Inbound mail addressing
Inbound mail addressing lets you decide the level of matching to allow on your system:
Allow short forms
Allows short forms of mail aliases, for example, email@example.com for Roy Allen.
Exact match only
Requires the recipient's name has to match the entire entry on his User Information form, for example, firstname.lastname@example.org or email@example.com. Both of these email addresses are on Roy Allens User Information form.
Allows only exact matches to the aliases set on the User Information form.