Just as user accounts can reside in multiple places, so can alias accounts. Aliases can reside in the internal Unoverica Message Transport directory, or can also be located in external text files, sharable by other SENMDAIL-based mail systems on your network.
Managing Unoverica Message Transport-based alias accounts is achieved through the use of UCMCON.NLM management tool. UCMCON.NLM is a NetWare Loadable Module that runs on the NetWare server. To load UCMCON, type the following command at the NetWare console prompt:
:LOAD UCMCON <Enter>
You will be presented with a screen similar to the following:

Figure G.7: UCMCON's main menu.
Select the "Configuration" menu item and press <Enter>. You will then be presented with a set of configuration menu choices similar to the following:

Figure G.8: UCMCON's Configuration menu.
Select the "Directory" menu option and press <Enter>. You will then be presented with a list of directory-specific choices, similar to the following:

Figure G.9: UCMCON's Directory menu.
To add, edit or delete alias accounts from the directory, select the "Aliases" menu and press <Enter>. You will then be presented with a list of the currently-defined users. If you have not yet defined any local users in the Unoverica Message Transport directory, then the list will be empty.

Figure G.10: UCMCON's currently-defined alias accounts.
To add a new alias account to the directory, press the <Ins> key. To edit an existing Unoverica Message Transport alias, select it and press <Enter>. To delete an existing Unoverica Message Transport alias, select it and press <Enter>.
If you are adding a new user to the directory, press <Ins>. You will be presented with a dialog box that allows you to define the mail-specific attributes of that alias.

Figure G.11: UCMCON's alias detail form.
The various fields in this form define the attributes associated with a mail user capable of receiving mail. The fields are:
|
Field |
Description |
|
Mail Name: |
The "Mail Name" field defines a unique identifier for the user account. No two users can have the same mail name. In simple installations, the "Mail Name" is the simplest form of identification for the mail user; it is the username at which the recipient receives mail, and the username used to retrieve mail via POP3. |
|
Org Name: |
This field is currently not in use, and is ignored by Unoverica Message Transport. |
|
Ext Name: |
If a user needs to receive mail at a domain name that is not the systems default (as defined in the $w class), then you must define the fully-qualified name here, in user@domain syntax. Mail sent to the user account specified in the "Ext Name" field is placed into this users mailbox. Similarly, out-bound mail sent from this user will be re-written so that it appears to be from the user@domain syntax specified in the "Ext Name" field. This field will not be used by most people. |
|
Description: |
The "Description" field should be used to provide the users full name or any other string that may be useful for identifying the users identity. |
|
Field X: |
These fields only apply to Unovericas directory integration products, such as Unovericas Directory Services for Z-Mail. These fields can be used to provide additional information about the user account (such as location, phone number, etc.) to the mail clients that support it. |
|
Active: |
Not all user accounts need to be active all of the time. Some users may be relocated, or some system accounts may not need to receive mail. Setting the "Active" field to "No" indicates that this account is not currently active, and cannot receive mail, or retrieve mail using POP3. |
|
Listed: |
The "Listed" field only applies to Unovericas directory integration products, such as Unovericas Directory Services for Z-Mail. Setting the "Listed" field to "No" indicates that this account is not to be returned in the list of users found on this system. |
Figure G.12: Mail user attributes defined for alias accounts.
Although the alias form and the user form appear to be quite similar, there are four fields missing from the alias form. These fields are:
|
Field |
Description |
|
Login Name: |
The "Login Name" field defines the account name used for the POP3 login. Aliases do not have login names. |
|
OS Name: |
If the user account references an existing NetWare user account, then you must provide a pointer to the specific NetWare account in order for the POP3 password authentication to function as expected. Aliases do not login via POP3. |
|
Password: |
The "Password" field is used during POP3 authentication. Aliases do not login via POP3. |
|
Mailbox: |
The "Mailbox" field is used to provide an 8-digit string that tells Unoverica Message Transport where to store the users mail. Aliases do not have mailboxes. |
Figure G.13: Mail user attributes missing from alias accounts.
Since aliases are not users, they do not need to have a mailbox, nor do they have POP3 access to any mailboxes. They are only used to redirect incoming mail to a real user.
Copyright 1997 Unoverica Corporation, All Rights Reserved page
Send comments to docs@unoverica.com