IMPORTANT:  You must restart the msgldap executable to effect any changes in the Address Agent configuration. See Loading and Unloading NetMail Agents for more information.

Port

Specifies the LDAP port assignment. LDAP applications (such as the Modular Web Client Address Book) use this port to access the Address Book Agent for address book lookups.

The Address Book Agent's default LDAP port assignment is 389.

Allow Personal Addressbook Search

Enables an LDAP client to perform a search on the user's personal address book if the LDAP connection is authenticated.

To authenticate the LDAP connection in a client such as Outlook Express, the user must configure My LDAP Server Requires Authentication, then provide his or her eDirectory username and password.

Supported Users

The messaging system contexts the Address Book Agent references to generate its user index. Users belonging to supported contexts are available for LDAP queries. Conversely, User objects not included in a supported context are not included in the agent's index and, therefore, are not available for LDAP queries.

Users with an Unlisted Privacy status are not included in the system address book, regardless of whether they are in a supported NMAP context. For more information on defining the user's privacy status, see the Privacy property in the User Objects.

Because NMAP Agents define the messaging system's supported contexts, the Supported Users property corresponds to NMAP Agents. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server that has users in its assigned contexts.

To verify that the Address Book Agent is servicing a particular NMAP Agent's user contexts:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the msgldap executable to effect any changes in the Supported Users configuration. See Loading and Unloading NetMail Agents for more information.

By default, the Address Book Agent is enabled. To disable the Address Book Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the Address Book Agent at startup. However, to immediately disable the agent, you must manually unload the msgldap executable or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Starting and Stopping NetMail.

After the Address Book Agent is disabled, the messaging server does not launch the msgldap executable again until you select Enabled and restart the messaging server.

2

This option is associated with the Enable Automatic LDIF File Export feature in the administrative interface.

8

This is the optional feature, Require Authentication.

It requires a username and password when users connect to the Address Book Agent.

32

This option is associated with the Allow Personal addressbook search feature in the administrative interface.

IMPORTANT:  You must restart the msgalias executable to effect any changes in the Alias Agent's configuration. See Loading and Unloading NetMail Agents for more information.

Every _____ Day(s)

How often (in days) the Alias Agent regenerates the alias database. The default is 1 day. The maximum setting is 99 days.

The alias database contains alias tables that store the aliases and their associated usernames.

If any errors are generated in the alias database (such as duplicate aliases), the Alias Agent notes the conflict in the log file and sends an SNMP trap, if SNMP is configured.

Automatically populate "Internet E-mail Address" attribute

Automatically populates the Internet E-mail Address attribute in the User object with one of the following values:

• Default e-mail address

  For information on how the default e-mail address is derived, see User E-Mail Addresses.

• Firstname_Lastname@Domain (Steve_Johnston@novell.com)
• First Letter+Lastnam@Domain (Sjohnsto@novell.com)

  This alias option is limited to eight characters.

Global Aliases

Aliases that are recognized by every Alias Agent running on a distributed messaging server. Global aliases are stored in a shared alias table in the Internet Services container. The shared alias table includes entries from every Alias Agent running on a distributed messaging server.

Other than the fact that global aliases are recognized throughout the messaging system, there is no difference between local and global aliases. Global aliases are defined in exactly the same manner as local aliases and the same rules apply.

The preferred way to manage Global Aliases is to define eDirectory Alias objects. This is because eDirectory Alias objects provide all the functionality of Global Aliases, but they do not require an Alias Agent.

You cannot create Alias objects in WebAdmin; therefore, you must use another administrative tool, such as iManager, to create Alias objects.

For more information, see Creating Aliases.

Queue Server

By default, the Alias Agent's monitored queues and supported user contexts are defined by the Monitored Queues property. The Queue Server property overrides the Monitored Queues property and allows you to selectively define which message queues you want the Alias Agent to monitor.

IMPORTANT:  You should only define this property if you want to restrict which message queues the Alias Agent monitors. Otherwise, you do not need to configure this property.

The Queue Server property defines the message queues monitored by the Alias Agent. Messages passing through the specified NMAP Agents' message queues are scanned by the Alias Agent. If a message recipient matches any of the Alias Agent's defined aliases, it replaces the alias with the corresponding e-mail address.

A single Alias Agent can monitor multiple message queues; however, you should not configure multiple Alias Agents to monitor the same queue. Doing so produces inconsistent results such as duplicate messages. Only one Alias Agent should monitor each message queue.

Because NMAP Agents manage the message queues, the Queue Server property corresponds to NMAP Agents.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must ensure that the Alias Agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that an Alias Agent is registered to a particular message queue:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the msgalias executable to effect any changes in the Monitored Queues configuration. See Loading and Unloading NetMail Agents for more information.

Monitored Queues

By default, this property defines the Alias Agent's monitored queues and its supported user contexts.

Monitored Queues are the message queues monitored by the Alias Agent. Messages passing through the specified NMAP Agents' message queues are scanned by the Alias Agent. If a message recipient matches any of the Alias Agent's defined aliases, it replaces the alias with the corresponding e-mail address.

The supported user contexts represent the users serviced by the Alias Agent. The Alias Agent can automatically generate aliases for supported users. It can also populate the Internet E-mail Address attribute in the users' associated User objects.

Because NMAP Agents manage both the message queue and the messaging system's user contexts, the Monitored Servers property corresponds to NMAP Agents.On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server that has users in its assigned contexts.

A single Alias Agent can service multiple NMAP Agents; however, you should not configure multiple Alias Agents to service the same NMAP Agent. Doing so produces inconsistent results such as duplicate messages. Only one Alias Agent should service each NMAP Agent.

To verify that the Alias Agent is servicing a particular NMAP Agent:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the msgalias executable to effect any changes in the Supported Users configuration. See Loading and Unloading NetMail Agents for more information.

By default, the Alias Agent is enabled. To disable the Alias Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the Alias Agent at startup. However, to immediately disable the agent, you must manually unload the msgalias executable or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Loading and Unloading NetMail Agents on Linux.

After the Alias Agent is disabled, the messaging server does not launch the msgalias executable again until you select Enabled and restart the messaging server.

IMPORTANT:  You must restart the antispam executable to effect any changes in the AntiSpam Agent's configuration. See Loading and Unloading NetMail Agents for more information.

CC Postmaster

Copies the postmaster on blocked messages that are returned to their senders. This option works in conjunction with Send Back.

IMPORTANT:  You must restart the avirus executable to effect any changes in the AntiVirus Agent configuration. See Loading and Unloading NetMail Agents for more information.

CA InoculateIT

The AntiVirus Agent supports any Computer Associates InoculateIT-compliant virus engine.

If properly configured, the NetMail AntiVirus Agent accesses the bare engine and performs all required scanning. Consequently, unless you also use the server for file and print services, we recommend that you do not run the full scanning engine. Allowing the AntiVirus Agent to perform all required scanning improves system performance because the agent does not scan the temporary and permanent files written by NetMail.

If you need to run the full scanning product, you must load InoculateIT in the autoexec.ncf file or startup script before loading NetMail; InoculateIT cannot start if its engine (avengine) is already loaded. In this configuration, you must also ensure that you never unload InoculateIT without first unloading the NetMail AntiVirus Agent.

Command Software

The AntiVirus Agent supports any Command AntiVirus* compliant virus engine.

Pattern-file path:

The path to the virus engine's pattern files.

IMPORTANT:  Do not include the filenames.

Pattern files are virus definition files that you download periodically from the Computer Associates, McAfee, or Command Software Web sites to keep your virus protection up to date.

This field is specific to the CA InoculateIT, McAfee, and Command Software virus engines.

Port

The port at which the AntiVirus Agent can connect to the Symantec AntiVirus Scan Engine.

This field is specific to the Symantec AntiVirus Scan Engine.

Scan

The scanning options determine which messages are scanned for viruses.

Messages for Local Recipients

Only scans messages addressed to users for whom virus scanning is enabled. You can enable virus scanning at the Parent or User objects.

Notify intended recipient if infected

Sends a virus alert to the message recipients. The alert indicates who tried to send the message and which virus the message contained.

Monitored Queue

The message queue monitored by the AntiVirus Agent. Messages passing through the specified message queue are scanned by the AntiVirus Agent. If a message contains a virus, the AntiVirus Agent deletes the message from the queue. The AntiVirus Agent can also be configured to return the message to the sender with a notice indicating which virus the message contained. It can also send a virus alert to the message recipients indicating who tried to send the message and which virus the message contained.

A single AntiVirus Agent can monitor multiple message queues; however, you should not configure multiple AntiVirus Agents to monitor the same queue. Doing so produces inconsistent results such as duplicate messages. Only one AntiVirus Agent should monitor each message queue.

Because NMAP Agents manage the message queues, the Monitored Queues property corresponds to NMAP Agents. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must ensure that the AntiVirus Agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that an AntiVirus Agent is registered to a particular message queue:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the avirus executable to effect any changes in the Monitored Queues configuration. See Loading and Unloading NetMail Agents for more information.

By default, the AntiVirus Agent is enabled. To disable the AntiVirus Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the AntiVirus Agent at startup. However, to immediately disable the agent, you must manually unload the avirus executable or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Starting and Stopping NetMail.

After the AntiVirus Agent is disabled, the messaging server does not launch the avirus executable again until you select Enabled and restart the messaging server.

NOTE:  When you initially unload the avirus executable, the messaging system is not left unprotected. Because of the design of the message queue, NMAP temporarily pauses message processing while it tries to connect to the AntiVirus Agent. It attempts a connection several times before it continues message processing without the agent. This timeout period (approximately 30 seconds) provides enough time to reload the AntiVirus Agent after updating pattern files or engine code.

If you are using the InoculateIT engine without running the full scanning product, you only need to update the pattern file and/or the engine NLM.^TM NetMail automatically detects any such update, pauses the queue, reloads the engine and the new pattern files, and then resumes message processing.

Monitored Queues

The message queue monitored by the AutoReply Agent. Messages passing through the specified message queue are scanned by the AutoReply Agent. If a message is addressed to a user with an enabled autoreply message, the AutoReply Agent generates the autoreply message and drops it in the current message queue.

A single AutoReply Agent can monitor multiple message queues; however, you should not configure multiple AutoReply Agents to monitor the same queue. Doing so produces inconsistent results such as duplicate messages. Only one AutoReply Agent should monitor each message queue.

Because NMAP Agents manage the message queues, the Monitored Queues property corresponds to NMAP Agents. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must ensure that the AutoReply Agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that an AutoReply Agent is registered to a particular message queue:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the forward executable to effect any changes in the Monitored Queues configuration. See Loading and Unloading NetMail Agents for more information.

By default, the AutoReply Agent is enabled. To disable the AutoReply Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the AutoReply Agent at startup. However, to immediately disable the agent, you must manually unload the forward executable or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Starting and Stopping NetMail.

After the AutoReply Agent is disabled, the messaging server does not launch the forward executable again until you select Enabled and restart the messaging server.

Monitored Queues

The message queue monitored by the Calendar Agent. The Calendar Agent scans the specified message queues for iCal status messages. The Calendar Agent processes all Accept, Delegate, and Decline responses and automatically updates the event's status information in the event organizer's calendar.

Only the user who schedules the event can view who has accepted, delegated, or declined a calendar event. Attendees see only their own status; every other attendee is viewed as pending.

A single Calendar Agent can monitor multiple message queues; however, you should not configure multiple Calendar Agents to monitor the same queue. Doing so produces inconsistent results such as duplicate messages. Only one Calendar Agent should monitor each message queue.

Because NMAP Agents manage the message queues, the Monitored Queues property corresponds to NMAP Agents. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must ensure that the Calendar Agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that an Calendar Agent is registered to a particular message queue:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the calagent executable to effect any changes in the Monitored Queues configuration. See Loading and Unloading NetMail Agents for more information.

By default, the Calendar Agent is enabled. To disable the Calendar Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the Calendar Agent at startup. However, to immediately disable the agent, you must manually unload the calagent executable or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Starting and Stopping NetMail.

After the Calendar Agent is disabled, the messaging server does not launch the calagent executable again until you select Enabled and restart the messaging server.

Agent Status

By default, the CAP Agent is enabled. To disable the CAP Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the CAP Agent at startup. However, to immediately disable the agent, you must manually unload the capd executable or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Loading and Unloading NetMail Agents.

After the CAP Agent is disabled, the messaging server does not launch the capd executable again until you select Enabled and restart the messaging server.

Expiration Timeout

The amount of time (in minutes) that an IP address is stored by the Connection Manager Agent. You can designate any value between 5 and 1440 minutes.

IMPORTANT:  You must restart the gkeeper executable to effect any changes in this property. See Loading and Unloading NetMail Agents for more information.

By default, the Connection Manager Agent is enabled. To disable the Connection Manager Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the Connection Manager Agent at startup. However, to immediately disable the agent, you must manually unload the gkeeper executable or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Loading and Unloading NetMail Agents.

After the Connection Manager Agent is disabled, the messaging server does not launch the gkeeper executable again until you select Enabled and restart the messaging server.

IMPORTANT:  You must restart the imslist executable to effect any changes in the List Agent configuration. See Loading and Unloading NetMail Agents for more information.

IMPORTANT:  You must restart the modwebd executable to effect any changes in the Modular Web Agent's configuration. See Starting and Stopping NetMail for more information.

Default Language

The default language for the Modular Web Agent and its submodules. The language defined in the Parent object or the User Options menu overrides this default setting.

SSL Port

The port the Modular Web Agent uses for secure HTTP (HTTPS) connections. The default HTTPS port assignment is port 443.

Use the default port number unless that port number is already in use by another program on the server.

Default Template

The template NetMail uses if no template is defined in the User and Parent objects.

Select the default template from the Available Templates list.

Queue Server

The message queue to which the ModWeb Calendar Module delivers appointments, notes, and tasks that need to be processed. Because NMAP Agents manage the message queue, the Queue Server property corresponds to an NMAP Agent.

Each ModWeb Calendar Module can only have one queue server. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must design your system so that each queue agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that the ModWeb Calendar Module is registered to a particular queue server:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the modwebd executable to effect any changes in the ModWeb Calendar Module's configuration. See Loading and Unloading NetMail Agents for more information.

IMPORTANT:  You must restart the modwebd executable to effect any changes in the ModWeb Mail Module's configuration. See Loading and Unloading NetMail Agents for more information.

Maximum number of recipients per e-mail

Limits the number of recipients for messages sent by users in the current messaging system.

The ModWeb Mail Module does not restrict the number of recipients for inbound messages that the Modular Web Agent downloads from the user's mailbox.

The Addressbook options allow you to control which address books users can access in WebAccess and Webmail.

To sort the ModWeb address books, see Configuring the Mail Module.

System-Wide

If enabled, this option gives users access to a system-wide address book in WebAccess and Webmail.

ldap://user:password@hostname:port/?basedn

• The user:password variable is the user's name and password.
• Hostname identifies the LDAP server's host name or IP address. If you type the IP address of a server running the Address Book Agent, users can access address book information from eDirectory.

• Port specifies the LDAP port assignment. If the LDAP server uses the default LDAP port (port 389), you do not need to specify a port.
• Basedn identifies the address book context. This is required if the Require DN attribute is added to the Address Book Agent. It is ignored if the Derive DN from Authentication is added to the Address Book Agent. See Address Book Agent Optional Features for more information.

If you are using the Address Book Agent to provide a system-wide address book, the only required parameters are hostname:port.

Users with the Privacy attribute set to Limited or None in their eDirectory User object are visible to other NetMail users in the System-Wide Addressbook. Users with an listed privacy setting are not visible in the System-Wide Addressbook.

For information on providing domain-specific address books, see Managing Multiple Address Books.

IMPORTANT:  You must restart the modwebd executable to effect any changes in the Preference Module's configuration. See Loading and Unloading NetMail Agents for more information.

Allow Change

If Yes, this option enables users to change their login password from the Modular Web Agent templates.

Because NetMail is completely integrated with eDirectory, the user's ModWeb password is the same as the user's NetWare login password. Therefore, this option actually gives your users rights to their NetWare login password through Modular Web Agent, regardless of whether they have rights to the actual password property in their eDirectory User object.

Disables user configuration options in the WebAccess and Webmail templates. If Yes, these options do not appear in the User Options menu.

Colors

Template color definition options. This option is specific to the Webmail template.

Signature

Custom text automatically inserted at the end of each message.

IMPORTANT:  You must restart the nmapd executable to effect any changes in these properties. See Loading and Unloading NetMail Agents for more information.

Spool Directory

The drive or volume and, optionally, the directory where the message queue is located.

For detailed information about the Spool directory structure and how the message queue works, see Message Processing.

Minimum Space

The minimum amount of free space you want to maintain on the drive or volume hosting the message queue. The default is 2048 KB.

If the server reaches the Minimum Space quota, the messaging server bounces all incoming messages, stops system logging, and sends an SNMP trap.

On NetWare, if your mail directories are on the sys: volume, you can use this option to maintain the free space required by NetWare.

Retry Interval

The number of minutes the NMAP Agent waits before trying to resend any e-mail message. The default is 30 minutes.

NetMail never queues messages unless there is a problem. Under normal conditions, the NMAP Agent immediately tries to send messages after they are processed in the queue.

If, for some reason, the message is not sent, it remains in the queue for the number of minutes specified in the Retry Interval before NMAP tries to resend the message. For example, if you send a message to a company whose mail server is down, the messaging server keeps trying to send the message at the designated intervals.

Changes to this property are effective within 5 minutes.

CC Postmaster

Enable this option to send the postmaster a copy of bounced messages.

Forward Local Undeliverable Messages

The host name or IP address of a server designated to receive messages that are addressed to the messaging system's domain but are undeliverable within the local NetMail system. If you specify an IP address rather than a host name, you must enclose the IP address in square brackets [ ] to form a valid e-mail address.

Changes to this property are effective within 5 minutes.

When the NMAP Agent determines that a message recipient is within its Internet domain but cannot find the user in eDirectory, the NMAP Agent modifies the domain portion of the address with the value placed in this field and re-queues the message.

WAN environments commonly use this feature with standalone messaging servers in remote offices. For detailed information on this configuration, see Multiple Messaging Server WAN.

This option also enables NetMail to share a domain name with another e-mail system such as Novell GroupWise, Lotus Notes, or Microsoft Exchange. When this option is configured, the NMAP Agent forwards messages that belong to the domain but are not addressed to users within the NetMail messaging system. For more information on domain sharing, see Domain Sharing.

Weekdays

In the Weekdays field, specify a time span (using the 24-hour clock) when you do not want the NMAP Agent to process outgoing messages Monday through Friday.

Per User Quota

Enable this option to require individual user quotas. User quotas are set in the NetMail Configuration page of the User object. For further information on User object configuration, see User Objects.

Quota Return Message

An optional message that is returned to the sender when the recipient has exceeded his or her mailbox quota. The message notifies the sender that the recipient has exceeded the allotted mailbox quota and cannot receive additional messages.

NOTE:  When users are within 10% of their mailbox quota, they receive a system message notifying them that their mailbox is almost full. The message advises them to delete some of the messages and warns that when their mailbox is full, all inbound messages are returned to the sender.

The Single Copy Message Store (SCMS) feature allows NMAP to store e-mail messages sent to multiple recipients in a shared location on the messaging server. By default, messages sent to five or more users and exceeding 5 KB are stored in the shared message directory. To store a message in the SCMS directory, it must exceed both thresholds.

When a message exceeds the specified thresholds, NMAP places a single copy of the message and its attachments in the shared message directory. A pointer is placed in the recipients' mailboxes, directing NMAP to the complete message in the Single-Copy Message Store (SCMS) directory. When the last user downloads or deletes the message, it is deleted from the shared directory.

The SCMS feature conserves server disk space. Without SCMS, long messages and large attachments are sent to every recipient's mailbox, rapidly consuming large amounts of server disk space.

Changes to this property are effective within 5 minutes.

For more information on the SCMS directory, see Single Copy Message Store Directory Structure .

Message Size

The SCMS threshold for a message's minimum size, in kilobytes. If a message is larger than the designated message size and it exceeds the Minimum Number of Recipients threshold, it is stored in the SCMS directory.

Trusted Hosts

When NetMail agents need to access the message store or message queue, they create an IP connection to the associated NMAP Server and request the information they need. By default, the NMAP Agent requires all agents running on other servers (including other NMAP Agents) to authenticate with the server before it carries out their requests.

NetMail agent authentication does not use clear-text passwords.

By designating a messaging server as a trusted host, agents running on that server are not required to authenticate with the NMAP server. Rather, they are given open access to the NMAP Agent and its accompanying message queues and mail directories.

WARNING:  Because trusted hosts have complete access to all mailboxes and queued messages, you must secure the server consoles of all messaging servers with trusted host status. Do not grant trusted host status to Linux machines unless login access to the trusted host machines is restricted to the system administrator.

Because of the inherent security risks associated with this option, we recommend that you grant trusted host status only for testing purposes or to messaging servers running third party agents.

Changes to this property are effective within 5 minutes.

Text Signature

If enabled, appends the plain text signature to every outbound, remote message passing through the Pluspack Agent's monitored queues.

Copy to User

The user account to which the copies of remote messages are sent.

Allow Sending if Member of NDS Group

If this option is selected, only the members of the designated eDirectory Group are allowed to send messages outside the current messaging system.

You can select only one eDirectory Group.

Group

The eDirectory Group object used to include or exclude users for remote sending.

Return status to sender if refused

If a user's remote message is refused, this option returns a status message to the sender indicating that he or she is not allowed to send remote messages.

Monitored Queues

The message queue monitored by the Pluspack Agent. Messages passing through the specified message queue are scanned by the Pluspack Agent. All messages addressed to remote recipients are processed by the Pluspack Agent.

A single Pluspack Agent can monitor multiple message queues; however, you should not configure multiple Pluspack Agents to monitor the same queue. Doing so produces inconsistent results such as duplicate messages. Only one Pluspack Agent should monitor each message queue.

Because NMAP Agents manage the message queues, the Monitored Queues property corresponds to NMAP Agents. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must ensure that the Pluspack Agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that a Pluspack Agent is registered to a particular message queue:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the pluspackd executable to effect any changes in the Monitored Queues configuration. See Loading and Unloading NetMail Agents for more information.

Agent Status

By default, the POP Agent is enabled. To disable the POP Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the POP Agent at startup. However, to immediately disable the agent, you must manually unload pop3d or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Loading and Unloading NetMail Agents.

After the POP Agent is disabled, the messaging server does not launch pop3d again until you select Enabled and restart the messaging server.

IMPORTANT:  You must restart the mailprox executable to effect any changes in the Proxy Agent's configuration. See Loading and Unloading NetMail Agents for more information.

Simultaneous Threads

The number of threads you want to use to simultaneously retrieve messages. The more threads, the faster the message retrieval, but additional threads consume additional server memory.

Queue Server

The message queue to which the Proxy Agent delivers messages that need to be processed. Because NMAP Agents manage the message queue, the Queue Server property corresponds to an NMAP Agent.

Each Proxy Agent can only have one queue server. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must design your system so that each queue agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that a Proxy Agent is registered to a particular queue server:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the mailprox executable to effect any changes in the Queue Server configuration. See Loading and Unloading NetMail Agents for more information.

Supported Users

The users serviced by the Proxy Agent. Users belonging to supported contexts can proxy other mail accounts. (The Proxy Agent must be enabled on the users' associated User or Parent object.)

A single Proxy Agent can service multiple user contexts; however, you should not configure multiple Proxy Agents to service the same context. Doing so produces inconsistent results such as duplicate messages. Only one Proxy Agent should service each user context.

Because NMAP Agents manage the messaging system's user contexts, the Supported Users property corresponds to NMAP Agents.On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server that has users in its assigned contexts.

To verify that the Proxy Agent is servicing a particular NMAP Agent's user contexts:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the mailprox executable to effect any changes in the Supported Users configuration. See Loading and Unloading NetMail Agents for more information.

By default, the Proxy Agent is enabled. To disable the Proxy Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the Proxy Agent at startup. However, to immediately disable the agent, you must manually unload mailprox or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Loading and Unloading NetMail Agents.

After the Proxy Agent is disabled, the messaging server does not launch mailprox again until you select Enabled and restart the messaging server.

Monitored Queue

The message queue monitored by the Rule Agent. Messages passing through the specified message queue are scanned by the Rule Agent. If a message matches the conditions of a rule, the Rule Agent executes the rule action.

A single Rule Agent can monitor multiple message queues; however, you should not configure multiple Rule Agents to monitor the same queue. Doing so produces inconsistent results such as duplicate messages. Only one Rule Agent should monitor each message queue.

Because NMAP Agents manage the message queues, the Monitored Queues property corresponds to NMAP Agents. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must ensure that the Rule Agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that a Rule Agent is registered to a particular message queue:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the rulesrv executable to effect any changes in the Monitored Queues configuration. See Loading and Unloading NetMail Agents for more information.

By default, the Rule Agent is enabled. To disable the Rule Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the Rule Agent at startup. However, to immediately disable the agent, you must manually unload the rulesrv executable or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Starting and Stopping NetMail.

After the Rule Agent is disabled, the messaging server does not launch the rulesrv executable again until you select Enabled and restart the messaging server.

You must add all the domain and host names that your NetMail system is planning to accept messages in either the Global or Hosting Domains list.

In listing the domains that belong to your messaging system, consider the following important points:

• Do not list a domain as both a Global Domain and a Hosting Domain.
• Failure to add all domain and host names that resolve to the server's IP address creates message loops that quickly consume all your server resources. The problem is that messages addressed to domains not included in the SMTP Agent's domain lists still resolve to the SMTP server's IP address. However, because they aren't listed in the domain lists, the SMTP Agent cannot accept them. Therefore, the SMTP server ends up relaying these messages to itself in an endless loop. (NetMail only prevents such loops for domains that resolve to loopback or the server's default IP address.)

Parent Object

The Parent object associated with the SMTP Agent. The SMTP Agent recognizes all Global and Hosting Domains listed in its associated Parent objects. See Supporting Multiple Internet Domains for more information.

Changes to this property are implemented within 5 minutes.

A series of standard SMTP commands that you can enable on the current SMTP Agent. Select the commands you want the SMTP Agent to accept.

Changes to the STMP flags are implemented within 5 minutes.

Allow EXPN Command

The EXPN command expands a group name upon request and lists all the user names in that group. This command is also considered a security risk because it allows spammers to anonymously request group membership lists. For example, if a spammer makes a request to expand a system-wide group such as Everyone, the SMTP Agent returns the complete membership list, which is, essentially, every username in your organization.

Send ETRN

The SEND ETRN command requests a remote server to send any messages it has queued for your messaging system. This option is primarily for organizations with dial-up Internet connections.

For more information, see Servicing ETRN Domains.

A mail relay host is a relay point for remote messages. It is often used to transfer outbound messages through a firewall. ETRN Domains also use Mail Relay Hosts to transfer messages to their relay service. See Servicing ETRN Domains for more information.

IMPORTANT:  You must restart the smtpd executable to effect any changes in the Mail Relay Host configuration. See Loading and Unloading NetMail Agents for more information.

Deny Hosts Not in DNS

Provides reverse DNS lookups. When receiving messages from external systems, the SMTP Agent verifies that the host's IP address and domain correspond to its DNS record. If they don't match, the SMTP Agent drops the connection.

You must configure your DNS server to support reverse DNS lookups for this option to function.

Enables the SMTP Agent to do lookups on the Realtime Blackhole List (RBL). RBL maintains a list of confirmed spammers and open relays. If the mail host matches an entry on the RBL, the connection is refused.

Blocked Hosts

A list of blocked IP address ranges. If Block Hosts in "Blocked" List is selected, the SMTP Agent refuses connections from any host within the designated IP address range.

Listing ranges of registered IP addresses blocks specific external hosts from sending mail to or relaying mail through your messaging system. For example, you can choose to list the IP addresses registered to public mail systems such as Hotmail,* Yahoo!,* and Juno* because spammers frequently use these systems to relay spam.

Use this option to block internal hosts. By listing ranges of internal IP addresses, you can block specific workstations from sending any messages over the Internet.

To add a blocked host, type a range of disallowed IP addresses in the Blocked Hosts field, then click Save. Enter one blocked host per line.For example:

251.70.2.53-251.70.2.60

This page provides options that prevent spammers from using your messaging system to relay unsolicited bulk e-mail (UBE) or spam.

Changes to these properties are implemented within 5 minutes.

Do SMTP-after-POP

Prohibits users from sending remote messages through the SMTP Agent until they have first authenticated with the messaging system via their POP3 or IMAP4 client. This works for most Internet e-mail clients because these clients always check for e-mail (log in) just before sending messages.

This feature also includes the username of the person who authenticated with the messaging system in the message header. This helps track spammers who authenticate with a valid username but fake the message header to mask their identity.

SMTP-after-POP requires that you run the Connection Manager Agent and that you configure the Connection Manager options on the messaging server running the SMTP Agent.

See SMTP-after-POP for detailed instructions on configuring SMTP-after-POP authentication.

WARNING:  If you are using a Proxy Server, we recommend that you use ESMTP authentication rather than SMTP-after-POP because the same IP address might be assigned to multiple users. For more information on ESMTP authentication, see the Allow Remote Sending for Authenticated Users Only feature in the SMTP Agent.

Require Sender to Be in "Allowed" List

Restricts access to your NetMail system by selectively allowing access. If enabled, only mail hosts with an IP address designated in the Allowed Hosts list can relay remote messages through the current SMTP server.

If SMTP-after-POP, ESMTP authentication, and Require Sender to Be in "Allowed" List are all enabled, they function as an either/or option. If an e-mail client does not authenticate using of POP or IMAP when downloading mail, it must authenticate using ESMTP or the Allowed Hosts list must include it before it can send remote messages.

Relayed Domains (ETRN)

ETRN Domains are messaging systems that use a hosting service, such as an ISP or ASP, to send and receive messages over the Internet. These systems have their own messaging servers, agents, and mail directories; however, all their messaging services are local. Consequently, they must use a hosting service to send and receive remote messages. In most instances, ETRN Domains have non-persistent dial-up connections to their ISP or ASP.

For more information, see Servicing ETRN Domains.

To add an ETRN domain, enter the IP address or host name of the ETRN domain's SMTP server, then click Save. Enter one ETRN domain per line.

IMPORTANT:  To support these domains, you must click the Accept ETRN option in the Options page.

Domain Routing

Domain Routing allows messages addressed to a specified domain to be sent directly to a defined IP address without first going through the DNS server.

To add a domain to the Domain Routing list, type the domain name, a space, and then the IP address to which messages should be sent. Enter only one domain per line. For example:

testdomain1.com = 130.45.45.109
testdomain2,com = 140.42.42.111

To remove a domain from the Domain Routing list, select the domain and press Delete.

IMPORTANT:  You must restart the smtpd executable to effect any changes in the Domain Routing configuration. See Loading and Unloading NetMail Agents for more information.

The message queue to which the SMTP Agent delivers messages that need to be processed. Because NMAP Agents manage the message queue, the Queue Server property corresponds to an NMAP Agent.

Each SMTP Agent can only have one queue server. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must design your system so that each queue agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that an SMTP Agent is registered to a particular queue server:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

IMPORTANT:  You must restart the smtpd executable to effect any changes in the Queue Server configuration. See Loading and Unloading NetMail Agents for more information.

A monitored queue is the message queue from which the SMTP Agent picks up messages for remote delivery.

A single SMTP Agent can monitor multiple message queues; however, you should not configure multiple SMTP Agents to monitor the same queue. Doing so produces inconsistent results such as duplicate messages. Only one SMTP Agent should monitor each message queue.

Because NMAP Agents manage the message queues, the Monitored Queues property corresponds to NMAP Agents. On a standalone messaging server, WebAdmin automatically selects the NMAP Agent on the current server. In distributed messaging systems, you can select any NMAP Agent on a distributed messaging server.

IMPORTANT:  If you have a distributed messaging system with multiple NMAP Agents, you must design your system so that each queue agent only processes messages one time as they go from the queue server to the message store. For more information, see Agent Distribution in Distributed Environments.

To verify that an SMTP Agent is registered to a particular message queue:

1. Telnet to the queue server at port 689. (You must be a trusted host.)
2. Enter the config command to see a list of currently registered agents.

Changes to this property are implemented within 5 minutes.

By default, the SMTP Agent is enabled. To disable the SMTP Agent:

1. Select Disabled.
2. Click Save.

Disabling the agent prevents the messaging server from launching the SMTP Agent at startup. However, to immediately disable the agent, you must manually unload the smtpd executable or restart the messaging server. For more information on manually unloading NetMail agents or restarting the messaging server, see Starting and Stopping NetMail.

After the SMTP Agent is disabled, the messaging server does not launch the smtpd executable again until you select Enabled and restart the messaging server.