Form tabs
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.
Finger tab
Use this tab to configure the Finger protocol.
Finger port
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.
Request timeout
The time the server will wait for a Finger request before disconnecting the remote user.
LDAP tab
Use this tab to configure the LDAP protocol.
LDAP port
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.
LDAP timeout
The time, in minutes, the server will wait for an LDAP request before disconnecting the remote user.
Country
The ISO code for your country.
Organization
Your organization's name.
Organizational unit
A name describing the members of your organization who use this server (for example, Administration).
SSL
Enable SSL connections on your site for the LDAP protocol, the certificate name, and port number (default is 943). If you choose Enabled, both secure and nonsecure logins are allowed. If you choose Required, only secure logins are allowed.
For information on creating security certificates, see Creating Internet security certificates in the Internet Services Administrator's Guide in online help.
Aliases tab
Use this tab to indicate users' inbound mail aliases.
Space character
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@firstclass.com.
You can also define an Internet mail alias on a User Information Form (UIF). In that case, the alias will be used and the space character substitution ignored.
Automatic aliases
FirstClass can generate Internet aliases automatically by chosing one of these options:
Note
The Automatic aliases and Inbound mail addressing settings affect each other. For an explanation of how to configure these settings, see Advanced forms.
• Use user IDs as aliases
The aliases are the same as the users' user ID. This guarantees unique aliases, but exposes FirstClass user IDs and therefore reduces the security of your system.
• Use first initial and last name as aliases
The aliases consist 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 have to check for duplicates on your system.
• Use initials and last name as aliases
The aliases consist of the first character of the first name plus the first character of the middle name plus the last name (for example, James Lee Brown would have the alias jlbrown). This is not guaranteed to be unique. Because user IDs must be unique, you will have to check for duplicates on your system.
• Use first name and last initial as aliases
The aliases consist of the first name plus the first character of the last name (for example, James Lee Brown would have the alias jamesb). This is not guaranteed to be unique. Because user IDs must be unique, you will have to check for duplicates on your system.
• Use first and last names as aliases
The aliases consist of the first name plus the last name (for example, James Lee Brown would have the alias jamesbrown). This is not guaranteed to be unique. Because user IDs must be unique, you will have to check for duplicates on your system.
• Use last and first names as aliases
The aliases consist of the last name plus the first name (for example, James Lee Brown would have the alias brownjames). This is not guaranteed to be unique. Because user IDs must be unique, you will have to check for duplicates on your system.
• Use first initial and client ID as aliases
The aliases consist of the first character of the first name plus the client ID (for example, James Lee Brown with a client ID of 1289 would have the alias j1289). This guarantees unique aliases and doesn't expose your FirstClass user ID.
If you chose Do not create automatic aliases, only the users first and last names will be used:
firstname_lastname@yoursite.com.
You can override the Internet alias generated for a user by updating the "Mail aliases" field on the User Information Form (UIF) for that user.
Inbound mail addressing
Inbound mail addressing lets you decide the level of matching to allow on your system in conjunction with your choice of Automatic aliases:
• Allow short forms
Allows short forms of mail aliases, for example, ro_al@huskyplanes.com for Roy Allen.
• Exact match only
Requires the recipient's name to match the entire entry in the "Mail aliases field" on a user's User Information form, for example, roy_allen@huskyplanes.com or roy@huskyplanes.com. This selection will also match a user's firstname_lastname entry in the Directory.
• Aliases only
Allows only exact matches to the aliases set on the User Information form.
|