{TemplateInclude "Default" "HelpNav"}

SMTP Agent - Identification

IMPORTANT: You do not need to restart the smtpd executable to effect changes to these properties. Instead, changes are effective within 5 minutes.

 

Domains

You must add all the domain and host names that your NetMail® system is planning to accept messages from 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.)

 

Global Domains

A listing of the messaging system’s native domains.

When the SMTP Agent receives a message, it looks at the domain portion of the recipient’s e-mail address (everything after the @ symbol). If the addressed domain matches a domain in the Global Domains list, the SMTP Agent removes the domain portion of the address and drops the message in the message queue.

Because the SMTP Agent removes Global Domains from the recipient’s e-mail address, ensure that the user portion of the e-mail address (everything before the @ symbol) is unique.

You can address unique usernames at any global domain. For example, messages addressed to Bob@Novell.com and Bob@Novell.edu are delivered to the same mailbox if Novell.com and Novell.edu are listed as Global Domains and an NDS object named Bob exists in an NMAP Agent context. For more information on NMAP Agent contexts, see the NMAP Agent's Context property.

 

Hosting Domains

A listing of foreign domains hosted on the current system. This option is most applicable to ISP environments. For more information, see the Novell® NetMail Administration Guide at http://www.novell.com/documentation.

When the SMTP Agent receives a message addressed to a domain in the Hosting Domains list, it drops the message in the message queue without removing the domain portion of the recipient’s e-mail address.

Because the entire e-mail address remains intact, it is not necessary that the user portion of the e-mail address (everything before the @ symbol) is unique. Combining the user’s name with a Hosting Domain name enables identical users to exist within the same messaging system. Although, you might have multiple users named “jling” in your overall messaging system, each one has a unique NDS® username.

NOTE: Because the user’s e-mail address is also the user’s NDS username, the user must type his or her full e-mail address (username@domain) to log in to the system.

Users created with domains in their NDS object names can only be addressed at that domain. For example, messages addressed to Bob@Novell.com and Bob@Novell.edu are delivered to different mailboxes if Novell.com and Novell.edu are listed as Hosting Domains and NDS objects named Bob@Novell.com and Bob@Novell.edu exist in an NMAP Agent context. For more information on NMAP Agent contexts, see the NMAP Agent's Context property.

In POP mode, Netscape* Messenger* 4.x strips @ symbols and trailing characters from usernames. Users in Hosting Domains can use either Netscape Messenger 4.x in IMAP mode or they can manually configure a POP client to accept usernames with the @ symbol.

To enable the Netscape Messenger 4.x POP client to accept usernames with the @ symbol, edit the PREFS.JS file in the c:\program files\netwscape\users\username directory. Add the following line above the other mail lines:

user_pref(“mail.allow_at_sign_in_user_name”, true)

You can then restart the Netscape Messenger 4.x POP client. It is possible to make this change before distributing the Netscape client to all the users.

 

Other

Message Size Limit

The maximum message size the SMTP Agent can accept. Because the SMTP Agent handles all Internet traffic, this property limits both incoming and outgoing Internet messages.

You can enter any amount between None (no limit) and 40 MB.

NOTE: This does not apply to messages sent using WebAccess or Webmail. While POP and IMAP clients must use the SMTP Agent to put their outbound messages in the NMAP Agent’s message queue, the Modular Web Agent can directly communicate with the NMAP Agent. Therefore, it drops its own messages in the message queue, circumventing the SMTP Agent’s message limit.

 

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 the Novell NetMail Administration Guide for more information.

 

A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark. For more information, see Legal Notices.