Unoverica Message Transport v2.11 Appendix G: User Accounts, Aliases and Lists

Appendix G: User Accounts, Aliases and Lists

G.3 Managing Unoverica Message Transport User Accounts

Some of the benefits of storing user account information in Unoverica Message Transport’s internal directory are:

Support for multiple mail domains. By creating a user account in Unoverica Message Transport’s directory, you can associate the account with any of the domains that your mail server supports. A NetWare user account is associated with the mail server’s primary domain, so if you need to support a user with an alternative domain name, then they must be added to the mail server.
Support for duplicate NetWare user accounts. If your NDS tree has multiple user accounts with the same username (in different containers) – or if you have NetWare 3.x servers with duplicate usernames – then you must use the directory in order to define external mail accounts. If you do not do this, then the mail server will not be able to deliver mail to both accounts.
Support for remote users. By default, only users with NetWare accounts can receive mail at that server. In order for a user without a NetWare account to receive mail, they must be added to the directory manually.
Detailed account management control. By using Unoverica Message Transport’s directory, you can define a large amount of account information, such as multiple account names, the mailbox filename, and other attributes that are not definable outside of the directory.

Managing Unoverica Message Transport-specific mail 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.1: 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.2: 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.3: UCMCON's Directory menu.

To add, edit or delete user accounts from the directory, select the "Users" 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.

NOTE: Accounts in the list only apply to users defined within Unoverica Message Transport’s directory. NetWare users will not appear in this list unless they have been manually added, added as a result of directory synchronization, or have been imported through the Import option. By default, this list is blank, and all of the user accounts stored in the NetWare bindery (or accessible through the SET BINDERY CONTEXT NetWare command) are able to be used for local mail storage and retrieval.

Figure G.4: UCMCON's currently-defined user accounts.

To add a new user account to the directory, press the <Ins> key. To edit an existing Unoverica Message Transport mail user, select it and press <Enter>. To delete an existing Unoverica Message Transport mail user, select 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 user.

Figure G.5: UCMCON's user 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.
Login Name:	Some sites prefer to use different mail user accounts from their NetWare user accounts. The "Login Name" field defines the account name used for the POP3 login. This field does not affect the incoming mail address for the user, but can instead be used to provide a unique POP3 login name. This field will not be used by most people.
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 system’s 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 user’s 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.
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. The "OS Name" field can reference a NetWare 3.x bindery account, or a fully-qualified NDS user account. The "Use Directory (+DIRECTORY)" option must enabled for the fully-qualified NDS references to function as expected. See section 2 Choosing a Directory Provider for instructions on how to enable the "Use Directory (+DIRECTORY) option.
Description:	The "Description" field should be used to provide the user’s full name or any other string that may be useful for identifying the user’s identity.
Field X:	These fields only apply to Unoverica’s directory integration products, such as Unoverica’s 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.
Password:	If the user account does not contain any data in the "OS Name" field, then the account is explicitly not linked to a NetWare user account. Therefore, the "Password" field must contain a password to be used during POP3 authentication. *NOTE:* The "Password" field cannot be left blank. Leaving the "Password" field blank effectively disables the account from retrieving mail with POP3.
Mailbox:	The "Mailbox" field is used to provide an 8-digit string that tells Unoverica Message Transport where to store the user’s mail. The 8-digit string is appended with ".mbx", and a file is created with that name in the directory specified in the "Location of mailbox directory (+MAILBOXDIR)" option.
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 Unoverica’s directory integration products, such as Unoverica’s 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.6: Mail user attributes defined for users stored in Unoverica Message Transport’s internal directory.