eDirectory Object Configuration Options

This section reviews the NetMail configuration options for the following eDirectory objects:

For an overview of each object's function within NetMail, see Existing Directory Objects.


Container Objects

Option Function
Internet Mail

 

Domain

The domain assigned to the current container. Changes to this property are implemented immediately.

Use Container Domains in conjunction with Global Domains; that is, if a Container Domain is defined, include it in the SMTP Agent's or Parent object's Global Domains list.

Container Domains are referenced by the Address Book Agent in returning users' address book information or in determining what address book contexts a user can access. See Address Book Agent for more information.

The Modular Web Agent can also use Container Domains to generate users' Internet e-mail addresses. See User E-Mail Addresses.

IMPORTANT:  Container Domains do not allow you to have non-unique user IDs in different containers.

Message Store

The drive or volume and, optionally, the directory where the mailboxes for users in the current container are located. If only a drive or volume are designated, the mail directories are created at the root.

Changes to this property are implemented within 5 minutes.

Only the users' mailbox directories are located in the container message store. The message queue and SCMS directories are always in the default location defined in the NMAP Agent.


Server Objects

Option Function
Internet Mail

 

 

A view-only page indicating that a NetMail messaging server is running on the current server.

Syslog

 

 

NetMail 3.5 uses Nsure Audit to log messaging system activity. The syslog option in the NCP Server object is provided for backward compatibility only. For information on using Novell Nsure Audit to log messaging system activity, see Auditing Your Messaging System.

IMPORTANT:  You must restart the messaging server to effect changes in the Internet Services' Syslog configuration. For more information about restarting the messaging server, see Loading and Unloading NetMail Agents.

Location

The location of the syslog file for servers running NetMail 3.1 or earlier. If no path is specified, the current server does not write events to a syslog file.

On NetWare systems, the default path and filename is sys:\etc\syslog.If a filename is specified in the log file field, the designated file is created in the sys:\etc\syslog.d directory on every messaging server in the tree. If a full path and filename are specified, the designated file and directory structure is created on every messaging server in the tree.

On Windows systems, the default path and filename are defined in the syslog keys in the Windows registry files. If a filename is specified in the log file field, the designated file is created in the default directory on every messaging server in the tree. If a full path and filename are specified, the designated file and directory structure is created on every messaging server in the tree.

On Linux, the Syslog is part of the operating system. It is typically configured by editing the /etc/syslog.conf file.

The maximum syslog file size is 1 MB. When the file exceeds 1 MB, it creates a new file.


User Objects

Option Function
General

 

Identification

All changes to User object properties are implemented immediately.

Internet E-Mail Address

The user's Internet e-mail address. This address must include the user's complete e-mail address, including the domain. You can automatically populate this field using the Alias Agent's Internet E-mail Address feature.

ModWeb does not verify that the domain listed in the User object's Internet E-mail Address property is a supported Global or Hosting domain. Therefore, we recommend that you use the Alias Agent to populate this property or manually ensure the domain is valid.

 

If the User object's Reply To Address field is empty, ModWeb uses the Internet E-Mail Address as the user's reply-to address. This address appears on the From: line of the user's outgoing mail.

IMPORTANT:  Typing the Internet E-Mail Address does not automatically enable the user to receive mail at this address. If the Internet E-Mail Address differs from the user's actual e-mail address, you must create an alias that associates the Internet E-Mail Address with the user's system e-mail address. You can either create an eDirectory Alias object or use the Alias Agent to create the alias. For more information, see Managing User Aliases. (You cannot create Alias objects in WebAdmin; therefore, you must use another administrative tool, such as iManager, to create Alias objects.)

Internet Mail

 

 

All changes to User object properties are implemented immediately.

IMPORTANT:  The implementation of these options depends on the Default Inheritance setting in the Parent object.

Internet Mail

 

User Status

By default, all users are enabled. To exclude the current user from the messaging system, select Disabled.

Though the user might reside in a supported NMAP context, selecting Disabled prevents the user from sending or receiving mail through NetMail.

This option only affects the NetMail messaging system. It does not disable the User object in eDirectory.

Timeout

The amount of idle time before the user is automatically logged out of the Modular Web client.

Specific actions, such as opening or sending an item, generate a call to the Web server. Other actions, such as scrolling through items in the Item List, composing a message without sending it, or reading Help topics, do not generate a call to the Web server. If, for a period of time, you leave the Modular Web client alone or perform actions that don't generate a call, the client logs you out. Doing so not only secures your mailbox, but it also ensures that the Web server and Modular Web client run efficiently. When you have timed out, and therefore are automatically logged out, and you attempt to perform a function, you are prompted to log in again.

If you are logged out while composing a message, NetMail prompts you with a login dialog when you attempt to send the message or go to another page, If you login successfully, NetMail resumes the original session so the message is not lost.

You can type a value (in minutes) between 1 and 40.

Privacy

Sets the user's level of privacy within the messaging system. The privacy level controls what the Address Book Agent reveals about the user.

The privacy options are executed as follows:

  • None: The current user's e-mail address, first name, last name, and full name is returned in address book queries.

  • Limited: Only the current user's e-mail address is returned in address book queries.

  • Unlisted: The current user's personal information is not available.

Reply To Address

The user's preferred reply-to address. The reply-to address appears on the From: line of the user's outgoing mail.

IMPORTANT:  Typing the Reply To Address does not automatically enable the user to receive mail at this address. If the reply-to address differs from the user's actual e-mail address, you must create an alias that associates the reply-to address with the user's system e-mail address. You can user either an eDirectory Alias object or the Alias Agent to create the alias. For more information, see Managing User Aliases. (You cannot create Alias objects in WebAdmin; therefore, you must use another administrative tool, such as iManager, to create Alias objects.)

If this field is left empty, ModWeb uses the Internet E-mail Address attribute from the User object as the user's Reply To address.

ModWeb does not verify that the domain listed in the User object's Internet E-mail Address property is a supported Global or Hosting domain. Therefore, we recommend that you use the Alias Agent to populate this property or manually ensure the domain is valid.

If the Internet E-mail Address property is not configured in the User object, ModWeb dynamically generates the user's e-mail address as follows:

  1. If the user belongs to a Hosting Domain, ModWeb simply uses the username as the e-mail address.
  2. If the user belongs to a Global Domain, ModWeb generates the e-mail address from the username and the user's Internet domain (username@domain).

To identify the user's Internet domain, ModWeb looks in the following objects:

  • If the user is associated with a Parent object, ModWeb looks in the Parent object's Global Domains list.
  • If no Global Domain is configured in the Parent object, ModWeb looks for the user's Container Domain.
  • If no Container Domain is configured, ModWeb uses the messaging server's Official Domain.

Changes to this property are implemented immediately.

Quota

If enabled, the designated disk quota is enforced for the current user.

This property overrides the System-Wide Mailbox Quota set in the NMAP Agent. For the Quota to take effect, you must enable the Per User Quota option in the NMAP Agent's configuration or the user's Parent object must defer the quota parameters to the User object.

Use the Disk Quota property to allot additional mailbox space on a case-by-case basis (e.g. system administrators, the messaging server's postmaster, or company VIPs).

Amount

The user's mailbox quota. The user's messages, folders, and calendar items count against the mailbox quota.

Forwarding

Message Forwarding can be defined by the administrator on the Parent object or the User object.

If Message Forwarding is enabled in the Features page, the user can define his or her own forwarding preferences in WebAccess or Webmail.

Enabled

Forwards the current user's incoming messages to the designated e-mail address. Incoming messages are simply forwarded; they are not delivered to the user's NetMail mailbox

The AutoReply Agent must run a messaging server within the user's messaging system for this option to function.

Enabled and Keep Local Copy

Forwards the current user's incoming messages to the designated e-mail address and keeps a copy of all forwarded messages in the user's NetMail mailbox.

Disabled

Disables message forwarding as configured in the User object.

IMPORTANT:  This option does not disable the Forwarding feature. To disable message forwarding in WebAccess and WebAdmin, disable Forwarding on the Features page in the User or Parent object.

Forward Mail to

The e-mail address where the current user's incoming messages are forwarded.

AutoReply

AutoReply can be defined by the administrator on the Parent object or the User object.

If AutoReply is enabled in the Features page, the user can define his or her own autoreply preferences in WebAccess or Webmail.

Enabled

Sends the defined message in response to incoming messages.

Disabled

Disables autoreply as configured in the User object.

IMPORTANT:  This option does not disable the AutoReply feature. To disable message forwarding in WebAccess and WebAdmin, disable Forwarding on the Features page in the User or Parent object.

Message

The autoreply/vacation message sent in response to all incoming messages.

Mail Proxy

If Mail Proxy is enabled in the Features page, the user can define his or her own mail proxy preferences in WebAccess or Webmail.

Enabled

Retrieves new messages from the designated POP3 or IMAP4 e-mail accounts to the current user's NetMail mailbox.

Proxied messages are deleted from the target account's mailbox.

Enabled and Leave Mail on Server

Retrieves new messages from the designated POP3 or IMAP4 e-mail accounts to the current user's NetMail mailbox.

A copy of all proxied messages is left in the target account's mailbox.

Disabled

Does not retrieve messages from the designated POP3 or IMAP4 e-mail accounts.

IMPORTANT:  This option does not disable the Mail Proxy feature. To disable the mail proxy feature in WebAccess and WebAdmin, disable Mail Proxy on the Features page in the User or Parent object.

Entry

The currently displayed Proxy entry. A user can have up to three proxy entries.

Type

The target account's e-mail protocol. Select POP3 or IMAP4.

Host

The host name or IP address of the target account's POP or IMAP server.

You need to know the Host Name of the POP or IMAP server for your service provider, such as imap.myisp.com, mail.myisp.com, or pop.mail.myisp.com. If you do not know the host name, contact your service provider.For example, the host name format is imap.myisp.com, mail.myisp.com, or pop.mail.myisp.com. If you do not know the host name, contact your service provider.

User Name

The username for the target account.

Password

The password for the target account.

Clear

Clears the current proxy entry.

Time and Date Settings

 

Timezone

The default time zone for the current user.

If the Default Timezone is defined in both the User and Parent objects, precedence is determined by the Parent object's Default Inheritance setting. If the Default Timezone is defined in the User Options menu in WebAccess or Webmail, the User Options setting takes precedence over both the Parent and User object settings.

Modular Web Agent

 

Template

The default template for the current user.

NetMail 3.5 ships with two client templates: WebAccess (Webacc.ctp) and Webmail (WebMail.ctp).

The WebAccess interface provides standard mail client functionality including calendaring, scheduling, busy search, assigning tasks, writing notes, and advanced rules. Administrators can also give users access to self-administration features like changing passwords and configuring vacation messages. Furthermore, administrators can use the WebAccess interface to delegate NetMail administrative functions such as adding, modifying, and deleting user accounts. (For more information on delegating NetMail administration, see Task-Oriented Management.)

Webmail is patterned after the NIMS 2.5 mail client interface. It provides all the features of the WebAccess template with the exception of advanced rules and adding, modifying, or deleting user accounts.

For more information on templates, see Templates.

Task Oriented Management

 

Allows the administrator to give the current user rights to create, import, modify, or delete user accounts in the domains and contexts designated in the associated Parent object. For more information, see Task-Oriented Management.

All changes to Task Oriented Management properties are implemented immediately.

All task-oriented management functions are enabled by the Modular Web Agent Task Management Module. Although the module has no configurable options, it must be running on the messaging server to provide TOM functionality in WebAccess.

Parent Objects

The Parent objects with which the current TOM administrator is associated.

In the WebAccess interface, the TOM administrator is able to create, modify, delete, or import users in the Global or Hosting Domains associated with the selected Parent objects. User objects are created in the NMAP contexts designated in the Parent object. For more information, see the Managed Contexts properties in Parent Object.

Allow User Creation

The TOM administrator can create User objects in the NMAP contexts listed in the Parent object. If multiple contexts are listed in the Parent object, NetMail equally distributes new User objects between the contexts.

In creating the user account, the TOM administrator can select one of the domains listed in their Parent object's Managed domain names property. Use this domain to create the new user's Internet e-mail address (username@domain).

If the TOM administrator selects multiple domains when creating the user, the User object is created with the first domain name and Alias objects are created with the subsequent domain names. For example, if the TOM administrator selects domains abc.com and 123.com when creating a user account for jotero, the User object is created as jotero@abc.com. The Alias object, jotero@123.com, points to jotero@abc.com.

IMPORTANT:  Inform all TOM administrators that extended characters cannot be used in Internet e-mail addresses. If a TOM administrator creates an e-mail address with an extended character, the corresponding user cannot log in to the messaging system or receive messages.

Every User object created by a TOM administrator is automatically associated with the Parent object that corresponds to its assigned domain.

Allow User Import

The TOM administrator can import users using comma-delimited, ASCII files. The new User objects are created in the NMAP context listed in the Parent object. If multiple contexts are listed in the Parent object, NetMail equally distributes new User objects between the contexts.

TOM Administrators can associate new User objects with a Parent object en masse by importing lists of users in the TOM administration menu in WebAccess.

IMPORTANT:  Enable Domain Settings must be also enabled before the TOM administrator can import users.

The first line in the import file is a header row. It specifies the user attributes contained in the file and their associated order. Of these attributes, the first three are fixed.

  • For users belonging to Global Domains, attribute 1 is the username.

    For users belonging to Hosting Domains, attribute 1 is the full e-mail address (username@hosted_domain.com). The TOM module verifies each Hosting Domain before allowing the import. If the TOM administrator doesn't have rights to a given user's domain (that is, the Hosting Domain isn't listed in the Parent object's Managed domain names property), TOM errors out the current user and proceeds to the next user in the list.

  • Attribute 2 is the surname.
  • Attribute 3 is the password.

Aside from these fixed attributes, the import file can include any data---not just the attributes specifically defined in WebAccess. For example, the first line or header row of the import file might appear as follows:

Username, Surname, Password, First name, Middle Initial

Following the header row are the user records. Each line represents a different user record. The data in each record is delimited by commas and must appear in the order designated in the header row. Using the header row from the previous example, a user record might appear as follows:

simon@test.com, Roberts, ih8beets, Simon, T

Allow User Deletion

The TOM administrator can delete users from the NMAP contexts selected in the Parent object. When a TOM administrator deletes a user account, he or she is given the option of removing the user's mailbox and all associated directories.

Enable Domain Settings

The TOM administrator can define default user attributes. These attributes are applied to all users created or imported in any of the domains designated in the Parent object.

IMPORTANT:  This option must be enabled before the TOM administrator can import users.

Features

 

 

All changes to User object properties are implemented immediately.

IMPORTANT:  The implementation of these options depends on the Default Inheritance setting in the Parent object.

Parent Object

The Parent object associated with the current user. The user "inherits" all options configured in the Parent object unless the Parent object's default inheritance is User First. This option gives User object settings precedence over the Parent object.

IMAP

Enables or disables IMAP connections for the current user.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the agent is enabled.

POP

Enables or disables POP connections for the current user.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the agent is enabled.

Forwarding

Enables or disables message forwarding for the current user. If Enabled is selected, the User object's Forwarding settings are activated.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the agent is enabled.

If Forwarding properties are defined in both the User and Parent objects, precedence is determined by the Parent object's Default Inheritance setting.

AutoReply

Enables or disables AutoReply messages for the current user. If Enabled is selected, the User object's AutoReply/Vacation settings are activated.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the agent is enabled.

If AutoReply/Vacation properties are defined in both the User and Parent objects, precedence is determined by the Parent object's Default Inheritance setting.

Messaging Rules

Enables or disables the Rules feature for the current user.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the agent is enabled.

Webmail

Enables or disables the Webmail template for the current user.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the Webmail template is enabled.

You must create the Webmail object in the tree before it can be enabled.

Modular Web Agent

Enables or disables the ModWeb client for the current user. If Enabled is selected, the User object's Default Timezone setting is activated.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the agent is enabled.

Mail Proxy

Enables or disables the Mail Proxy feature for the current user.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the Mail Proxy feature is enabled.

Calendar/Scheduling

Enables or disables the user's Calendars and scheduling functions.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the calendar and scheduling options are enabled.

Calendar Agent

Enables or disables iCal functionality, including automatic event status tracking, for the current user.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the agent is enabled.

AntiVirus

Allows the administrator to enable or disable virus scanning for the current user.

Selecting Deferred defers the setting to the Parent object. If Deferred is selected in both the Parent and User objects, the agent is enabled.

Rules

 

 

Displays the active rules for the current user. Both user-defined and administrator-defined rules are listed.

To define a rule for the current user, click New. For more information, see Defining Rules in User Objects