1. Manuals
  2. Brands
  3. Novell Manuals
  4. Software
  5. GROUPWISE 7 - MESSAGE TRANSFERT AGENT
  6. Manual

Novell GROUPWISE 7 - MESSAGE TRANSFERT AGENT Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Message Transfer Agent
X
Chapter 40, "Understanding Message Transfer between Domains and Post Offices," on
page 605
Chapter 41, "Configuring the MTA," on page 613
Chapter 42, "Monitoring the MTA," on page 645
Chapter 43, "Optimizing the MTA," on page 675
Chapter 44, "Using MTA Startup Switches," on page 683
X
Message Transfer Agent
603

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the GROUPWISE 7 - MESSAGE TRANSFERT AGENT and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Novell GROUPWISE 7 - MESSAGE TRANSFERT AGENT

Summary of Contents for Novell GROUPWISE 7 - MESSAGE TRANSFERT AGENT

  • Page 1 Message Transfer Agent Chapter 40, “Understanding Message Transfer between Domains and Post Offices,” on page 605 Chapter 41, “Configuring the MTA,” on page 613 Chapter 42, “Monitoring the MTA,” on page 645 Chapter 43, “Optimizing the MTA,” on page 675 Chapter 44, “Using MTA Startup Switches,”...
  • Page 2 604 GroupWise 7 Administration Guide...
  • Page 3 Understanding Message Transfer between Domains and Post Offices A domain organizes post offices into a logical grouping for addressing, routing, and administration ® purposes in your GroupWise system. Messages are transferred between post offices and domains by the Message Transfer Agent (MTA). The following topics help you understand domains and the functions of the MTA: Section 40.1, “Domain Representation in ConsoleOne,”...

  • Page 4: Domain Directory Structure

    GroupWise View Showing Post Offices in Relationship to Domains Figure 40-2 40.2 Domain Directory Structure Physically, a domain consists of a set of directories that house all the information stored in the domain. See “Domain Directory” in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure.

  • Page 5: Agent Input/Output Queues In The Domain

    40.3.3 Gateways Gateways are installed and configured at the domain level of your GroupWise system. For a list of gateways, see the GroupWise Gateways Documentation Web site (http://www.novell.com/ documentation/gwgateways). Understanding Message Transfer between Domains and Post Offices 607...
  • Page 6 Replicates updates to all domains and post offices throughout your GroupWise system. This keeps the Address Book up to date for all GroupWise users. ® Synchronizes GroupWise user information with Novell eDirectory user information. This handles updates made in ConsoleOne without the GroupWise Administrator snap-in running.

  • Page 7: Message Flow Between Post Offices In The Same Domain

    GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure. 40.7 Cross-Platform Issues between Domains and Post Offices Domains can be located on the following platforms: ® Novell NetWare Windows Server Linux The GroupWise agents can run on the following platforms: Novell NetWare Windows Server...

  • Page 8: Mta/Post Office Platform Independence Through Tcp/Ip Links

    Section 40.7.4, “MTA/Domain Platform Independence through TCP/IP Links,” on page 611 Section 40.7.5, “MTA/Domain Platform Independence through the Transfer Pull Configuration,” on page 611 40.7.1 MTA Platform Dependencies Because of Direct Access Requirements to Post Offices The MTA must always have direct access to the domain directory. In addition, if using mapped or UNC links to post offices, the MTA must have direct access to each post office directory as well.

  • Page 9: Mta/Domain Platform Independence Through Tcp/Ip Links

    The table below summarizes the various combinations of the platform of MTA for the source domain and the platform where the destination domain is located, and indicates which combinations work for direct access and which ones do not: MTA Platforms and Domain Platforms Table 40-2 NetWare MTA for Linux MTA for Source...
  • Page 10 612 GroupWise 7 Administration Guide...

  • Page 11: Configuring The Mta

    Configuring the MTA For detailed instructions about installing and starting the MTA for the first time, see “Installing GroupWise Agents” in the GroupWise 7 Installation Guide. ® As your GroupWise system grows and evolves, you will probably need to modify MTA configuration to meet changing system needs.

  • Page 12: Creating An Mta Object In Edirectory

    Do not attempt to create more than one MTA object for a domain. ® To create a new MTA object in Novell eDirectory: 1 In ConsoleOne, browse to and right-click the Domain object for which you need to create an MTA object, then click New.

  • Page 13: Configuring The Mta In Consoleone

    7 In the Description field, type one or more lines of text describing the MTA. This description displays on the MTA server console as the MTA runs. If multiple administrators work at the server where the MTA will run, the description includes a note about who to contact before stopping the MTA.
  • Page 14 The table below summarizes the MTA configuration settings in the MTA object properties pages and how they correspond to MTA startup switches (as described in Chapter 44, “Using MTA Startup Switches,” on page 683): MTA Configuration Settings Table 41-1 ConsoleOne Properties Pages and Corresponding Tasks and Startup Switches Settings Information Page...
  • Page 15 ConsoleOne Properties Pages and Corresponding Tasks and Startup Switches Settings HTTP User Name Section 42.2.1, “Setting Up the MTA Web Console,” on page 657. HTTP Password See also /httpuser and /httppassword. Network Address Page TCP/IP Address Section , “Using TCP/IP Links between Domains,” on page 618 Section , “Using TCP/IP Links between a Domain IPX/SPX Address...

  • Page 16: Changing The Link Protocol Between Domains

    ConsoleOne Properties Pages and Corresponding Tasks and Startup Switches Settings Certificate File Section 41.2.3, “Securing the Domain with SSL Connections to the MTA,” on page 629. SSL Key File See also /certfile, /keyfile and /keypassword. Password After you install the MTA software, you can further configure the MTA using a startup file. To survey the many ways the MTA can be configured, see Chapter 44, “Using MTA Startup Switches,”...
  • Page 17 4 On the Network Address page, click the pencil icon for the TCP/IP Address field to display the Edit Network Address dialog box. 5 Select IP Address, then provide the IP address, in dotted decimal format, of the server where the MTA is running.
  • Page 18 Corresponding Startup Switches You can also use the /tcpport switches in the MTA startup file to provide the IP address and the message transfer port number. MTA Web Console You can view the MTA TCP/IP information on the Configuration page under the TCP/IP Settings heading.
  • Page 19 7 Click OK. 8 Repeat Step 4 through Step 7 for each domain in the Outbound Links list where you want the MTA to use a TCP/IP link. Selecting multiple domains is also allowed. 9 Double-click a domain in the Inbound Links list. 10 Set Link Type to Direct.

  • Page 20: Changing The Link Protocol Between A Domain And Its Post Offices

    Async Gateway documentation at the GroupWise Gateway Documentation Web site (http://www.novell.com/documentation/gwgateways). Using the Internet Agent to Link Domains You can use the Internet Agent to link a domain into your GroupWise system across the Internet. When you use the Internet Agent as the transport mechanism between domains, it encapsulates GroupWise messages (both e-mail messages and administrative messages) within SMTP messages in order to transport them across the Internet.
  • Page 21 Using TCP/IP Links between a Domain and its Post Offices To change from mapped or UNC links to TCP/IP links between a domain and its post offices, you must perform the following two tasks: “Configuring the Agents for TCP/IP” on page 623 “Changing the Link Protocol between a Domain and its Post Offices to TCP/IP”...
  • Page 22 7 In the Message Transfer Port field, specify a unique TCP port on which the POA will listen for incoming messages from the MTA. The default is 7101. 8 For optimum security, select Enabled in the SSL drop-down list for the message transfer port. For more information, see Section 41.2.3, “Securing the Domain with SSL Connections to the MTA,”...

  • Page 23: Binding The Mta To A Specific Ip Address

    6 Make sure the information displayed in the Edit Post Office Link dialog box matches the information provided in the Edit Network Address dialog box in “Configuring the Agents for TCP/IP” on page 623. 7 Click OK. 8 Repeat Step 4 through Step 7 for each post office in the domain where you want to use TCP/IP...
  • Page 24 41.1.6 Moving the MTA to a Different Server As your GroupWise system grows and evolves, you might need to move an MTA from one server to another. For example, you might decide to run the MTA on a different platform, or perhaps you want to move it to a server that has more disk space for the mslocal directory.

  • Page 25: Adjusting The Mta Logging Level And Other Log Settings

    The full domain name is used in the filename. However, all letters are lowercase and any spaces in the domain name are removed. The startup file is located in the / opt/novell/groupwise/agents/share directory. 3 Adjust the setting of the /home switch to point to the new location of the domain directory.

  • Page 26: Configuring User Access Through The Domain

    41.2 Configuring User Access through the Domain Although users do not access the domain as they use the GroupWise client, their messages often pass through domains while traveling from one post office to another. Section 41.2.1, “Restricting Message Size between Domains,” on page 628 Section 41.2.2, “Enabling Live Remote,”...

  • Page 27: Enabling Live Remote

    messages. This arrangement allows typical messages to be processed promptly, while delaying large messages that exceed the specified size. The result is that large messages do not slow down processing of typical messages. 5 Click OK. 6 To exit the Link Configuration Tool and save your changes, click File > Exit > Yes. ConsoleOne then notifies the MTA to restart using the new message size limits.
  • Page 28 3 To use SSL connections between the MTA and the POAs for its post offices, which provides optimum security, select Enabled in the Message Transfer SSL drop-down list. The MTA must use a TCP/IP connection to each POA in order to enable SSL for the connection.

  • Page 29: Configuring Specialized Routing

    For background information about certificate files and SSL key files, see Chapter 71, “Encryption and Certificates,” on page 1117. 7 In the Certificate File field, browse to and select the public certificate file provided to you by your CA. 8 In the SSL Key File field: 8a Browse to and select your private key file.
  • Page 30 All messages from a domain can be automatically routed through another domain, regardless of the final destination of the messages. This provides additional control of message flow through your GroupWise system. You can set up routing domains on two levels: “Selecting a System Default Routing Domain”...

  • Page 31: Scheduling Direct Domain Links

    Selecting a Specific Routing Domain for an Individual Domain As long as you are not forcing all messages to the system default routing domain, you can override the system default routing information for an individual domain. 1 In ConsoleOne, browse to and right-click the MTA object, then click Properties. 2 Click GroupWise >...
  • Page 32 3 Click View > Domain Links to display domain links. 4 Double-click the domain you want to create a link schedule for. Only direct links can be scheduled. 5 Click Scheduling. The link schedule grid displays the current schedule for the selected direct link. The grid consists of half-hour time slots showing the link profile assigned to each time slot.
  • Page 33 Each link profile defines the following values to set the conditions under which the link opens: Which message queues to monitor Maximum wait time for any message in any monitored queue Maximum number of waiting messages allowed in all monitored queues Maximum total size of waiting messages allowed in all monitored queues The default profile shows as white in the link schedule grid.

  • Page 34: Using A Transfer Pull Configuration

    Queue Purpose Low priority status messages The contents of deselected queues are not monitored but are processed when the link opens. 10 For each selected queue, specify the maximum number of minutes a message must wait in each queue before the link opens. If you want the link to open immediately when a message arrives in the queue, specify 0 (zero).
  • Page 35 The transfer directory must contain a wpcsin subdirectory, with standard priority 0 through 7 subdirectories beneath. The transfer directory must be placed where both the sending and receiving MTAs have rights. 2 In ConsoleOne, modify the outgoing link from the sending domain so the MTA for the sending domain writes message files to the transfer directory, rather than directly to the receiving domain.

  • Page 36: Configuring Domain Maintenance

    Administrator snap-in running. The user information was changed using Novell iManager. The user information was changed using Novell eGuide and the GroupWise Identity Manager driver is not in use In these situations, user information in eDirectory no longer matches corresponding user information in GroupWise.
  • Page 37 Enabling eDirectory User Synchronization By default, eDirectory user synchronization is disabled. The MTA still performs all its other functions, but any changes made to user information in eDirectory without the GroupWise Administrator snap-in running will not appear in GroupWise until eDirectory user synchronization has been performed.
  • Page 38 2b Browse to and right-click a misconfigured MTA, then click Properties. 2c In the Platform field, select the platform where the MTA is running. 2d Click OK to save the correct platform information. 2e Return to Tools > GroupWise System Operations > eDirectory User Configuration > Configure Agents.
  • Page 39 9 If all domains are now enabled, click OK to return to main ConsoleOne window, then continue with “Scheduling eDirectory User Synchronization” on page 642. If some domains are still disabled, continue with “Assigning an eDirectory-Enabled MTA to Synchronize Other Domains” on page 641.
  • Page 40 3 Select the MTA you want to perform eDirectory user synchronization for the selected domain, then click OK. The domain should now display Enabled in the Status column of the eDirectory User Synchronization Configuration dialog box. 4 Repeat Step 1 through Step 3 until all domains in your GroupWise system are enabled for...

  • Page 41: Enabling Mta Message Logging

    3 Select an existing eDirectory user synchronization event, then click Edit. Click Create, then type a name for the event. 4 Set Type to eDirectory User Synchronization. 5 In the Trigger box, specify when you want the eDirectory user synchronization event to take place.
  • Page 42 5 In the Delete Reports After field, specify the number of days to retain reports on disk. Reports are automatically deleted after the specified time has passed. NOTE: Other fields appearing on the Message Log Settings property page of the MTA object in ConsoleOne were valid in earlier versions of GroupWise, but are not supported by the GroupWise 7 MTA.

  • Page 43: Monitoring The Mta

    Section 42.3, “Using MTA Log Files,” on page 665 Section 42.4, “Using GroupWise Monitor,” on page 666 Section 42.5, “Using Novell Remote Manager,” on page 667 Section 42.6, “Using an SNMP Management Console,” on page 667 Section 42.7, “Notifying the Domain Administrator,” on page 671 Section 42.8, “Using the MTA Error Message Documentation,”...
  • Page 44 NetWare: The MTA server console always displays on the NetWare server console. Linux: You must use the --show startup switch in order to display the Linux MTA server console. “Starting the Linux Agents with a User Interface” in “Installing GroupWise Agents”...
  • Page 45 Domains: Displays the total number of domains the MTA links to and the number that are currently closed. Post Offices: Displays the total number of post offices in the domain and the number that are currently closed. Gateways: Displays the total number of gateways in the domain and the number that are currently closed.
  • Page 46 MTA Admin Thread Status Box The MTA admin thread updates the domain database (wpdomain.db) when domains, post offices, users, and other types of object information are added, modified, or removed, and repairs it when damage is detected. To display the MTA Admin Thread Status box from the MTA server console, click Configuration >...
  • Page 47 “Displaying Live Remote Status” on page 653 “Displaying MTA Admin Thread Status” on page 653 “Recovering the Domain Database Automatically or Immediately” on page 654 “Performing eDirectory User Synchronization” on page 655 “Browsing the Current MTA Log File” on page 655 “Viewing a Selected MTA Log File”...
  • Page 48 4 Use the following command to verify that the MTA has stopped. ./grpwise status To stop the Linux MTA when it is running in the background as a daemon and you started it manually (not using the grpwise script): 1 Make sure you are logged in as root. 2 Determine the process IDs (PIDs) of the MTA: ps -eaf | grep gwmta The PIDs for all gwmta processes are listed.
  • Page 49 NetWare Note: Use Options (F10) > Configuration Status. Select the location, then click Suspend. Routing of all messages to and from the location remains suspended until you resume processing. To resume the MTA for a location: 1 At the server where the MTA is running, display the MTA server console. 2 Click Configuration >...
  • Page 50 MTA Web Console You also check the MTA software date on the Environment page. Displaying the Current MTA Settings You can list the current configuration settings of the MTA at the MTA server console. To display the current MTA settings: 1 At the server where the MTA is running, display the MTA server console.
  • Page 51 3 Select a location, then click Details to display the above information plus the following additional details: Hold: Displays the full path to the location of the directory structure used by the mslocal MTA to hold messages for closed locations. Pull: Displays the transfer pull directory, if any.
  • Page 52 Completed: Number of administrative message successfully processed. Errors: Number of administrative messages not processed because of errors. In Queue: Number of administrative messages waiting in the queue to be processed. Send Admin Mail: Select this option to send a message to the administrator whenever a critical error occurs.
  • Page 53 Admin Task Processing. Select Automatic Recovery or Perform DB Recovery as needed. Performing eDirectory User Synchronization ® You can configure the MTA to perform Novell eDirectory user synchronization at regular intervals. See Section 41.4.1, “Using eDirectory User Synchronization,” on page 638.
  • Page 54 MTA Web Console You can browse and search MTA log files on the Log Files page. Viewing a Selected MTA Log File Reviewing log files is an important way to monitor the functioning of the MTA. 1 At the server where the MTA is running, display the MTA server console. 2 Click Log >...

  • Page 55: Using The Mta Web Console

    4 Stop and restart the MTA. Accessing Online Help for the MTA Click Help on the menu bar for information about the MTA server console. Click the Help button in any dialog box for additional information. NetWare Note: Press F1 for information in any dialog box or menu. 42.2 Using the MTA Web Console The MTA Web console enables you to monitor the MTA from any location where you have access to a Web browser and the Internet.
  • Page 56 3 Make a note of the IP address or DNS hostname in the TCP/IP Address field. You need this information to access the MTA Web console. The HTTP Port field displays the default port number of 7180. 4 If the default HTTP port number is already in use on the MTA server, specify a unique port number.

  • Page 57: Accessing The Mta Web Console

    ConsoleOne then notifies the MTA to restart so the new settings can be put into effect. Corresponding Startup Switches You can also use the /httpport, /httpuser, and /httppassword startup switches in the MTA startup file to enable the MTA Web console. In addition, you can use the /httprefresh switch to control how often the MTA refreshes the information provided to your Web browser.
  • Page 58 Monitoring MTA Status When you first access the MTA Web console, the Status page is displayed. Online help throughout the MTA Web console helps you interpret the information being displayed and use the links provided. MTA Web Console with the Status Page Displayed Figure 42-4 Click the Router link to display details about the MTA routing queue (gwinprog).
  • Page 59 MTA Web Console with the Environment Page Displayed for a Linux Server Figure 42-6 On a Windows server, the following information is displayed: MTA Web Console with the Environment Page Displayed for a Windows Server Figure 42-7 Viewing and Searching MTA Log Files On the MTA Web console menu, click Log Files to display and search MTA log files.
  • Page 60 Event Logging (LOG): The event logging thread writes information into the event log files that you can search on this page. See Section 42.3, “Using MTA Log Files,” on page 665. Dispatcher (DIS): The dispatcher thread starts other MTA threads as needed to meet the demands being put on the MTA at any given time.
  • Page 61 MTA Web Console with the Links Page Displayed Figure 42-10 Click a location to view its holding queue. Click View Link Configuration to determine the address of each location and access the agent Web consoles of other domains and of post offices that belong to the local domain.

  • Page 62: Controlling The Mta From The Mta Web Console

    42.2.4 Controlling the MTA from the MTA Web Console At the MTA Web console, you can change some MTA log settings for the current MTA session. You can also stop and start some specific MTA threads. “Changing MTA Configuration Settings” on page 664 “Controlling the MTA Admin Thread”...

  • Page 63: Using Mta Log Files

    MTA Web Console with the Admin Task Status Page Displayed Figure 42-13 Modify the functioning of the MTA admin thread as needed, then click Submit. The changes remain in effect for the current MTA session. Controlling Links to Other Locations On the MTA Web console menu, click Links.

  • Page 64: Using Groupwise Monitor

    42.3.1 Configuring MTA Log Settings and Switches The following aspects of logging are configurable: Log File Path (/log) Disk Logging (/logdiskoff) Logging Level (/loglevel) Maximum Log File Age (/logdays) Maximum Log File Size (/logmax) You can configure the log settings in the following ways: Using ConsoleOne to establish defaults (see Section 41.1.8, “Adjusting the MTA Logging Level and Other Log Settings,”...

  • Page 65: Using Novell Remote Manager

    963. 42.5 Using Novell Remote Manager If the MTA is running on NetWare 6.5 or on Novell Open Enterprise Server (OES), you can use the IP Address Management feature in Novell Remote Manager (Manage Server > IP Address Management) to view the IP address and port configuration for the MTA. This is also true for other GroupWise agents (POA, Internet Agent, and WebAccess Agent) running on NetWare 6.5/OES...

  • Page 66: Setting Up Snmp Services For The Mta

    Section 42.6.2, “Copying and Compiling the MTA MIB File,” on page 670 Section 42.6.3, “Configuring the MTA for SNMP Monitoring,” on page 671 42.6.1 Setting Up SNMP Services for the MTA Select the instructions for the platform where the MTA runs: “Setting Up SNMP Services for the NetWare MTA”...
  • Page 67 3 Locate the snmpd.conf file on your Linux server. 4 In a text editor, open the snmpd.conf file and add the following line: dlmod Gwsnmp /opt/novell/groupwise/agents/lib/libgwsnmp.so 5 Save the snmpd.conf file and exit the text editor. 6 Restart the SNMP daemon (snmpd) to put the changes into effect.

  • Page 68: Copying And Compiling The Mta Mib File

    option was not available. Now that you have set up SNMP, you can install GroupWise agent SNMP support. At the Windows server where you want to install the GroupWise agent SNMP support: 1 Run setup.exe at the root of the GroupWise 7 Administrator for NetWare/Windows CD, then click Install Products >...

  • Page 69: Configuring The Mta For Snmp Monitoring

    2d Click Compile. 2e Make sure that the server where the MTA is running is configured to send SNMP traps to the ZENworks Server Management Site Server. NetWare: Add the IP address or hostname of the ZENworks Server Management Site Server to the traptarg.cfg file in the sys:\etc directory.

  • Page 70: Using The Mta Error Message Documentation

    2 In the Administrator field, browse to and select your GroupWise user ID. A domain can have a single administrator, or you can create a group to function as administrators. 3 Click OK to save the administrator information. The selected user or group then begins receiving e-mail messages whenever the MTA for the domain encounters a critical error.

  • Page 71: Using Platform-Specific Mta Monitoring Tools

    You can also use GroupWise Monitor to troubleshoot message transfer problems. See Part XIII, “Monitor,” on page 963. 42.10 Using Platform-Specific MTA Monitoring Tools Each operating system where the MTA runs provides tools for monitoring programs. NetWare: You can use the NetWare Monitor NLM to monitor the effects of the MTA on the NetWare server.
  • Page 72 674 GroupWise 7 Administration Guide...

  • Page 73: Optimizing The Mta

    Optimizing the MTA You can adjust how the MTA functions to optimize its performance. Before attempting optimization, you should run the MTA long enough to observe its efficiency and its impact on other network applications running on the same server. See Chapter 42, “Monitoring the MTA,”...

  • Page 74: Optimizing Mapped/Unc Links

    By default, the MTA waits 5 seconds for a response when trying to contact another MTA or a POA across a TCP/IP link. If no response is received from the other MTA or the POA, the sending MTA tries again three more times. If all four attempts fail, the MTA reports an error, then waits 10 minutes before it tries again.
  • Page 75 By default, when using mapped or UNC links, the MTA scans its high priority queues every 5 seconds and its regular and low priority queues every 15 seconds. You can adjust the scan cycle ® settings to meet the needs of your GroupWise system.

  • Page 76: Adjusting The Number Of Mta Scanner Threads For The Domain And Post Offices

    43.2.3 Adjusting the Number of MTA Scanner Threads for the Domain and Post Offices When using mapped or UNC links, the MTA automatically starts one high priority scanner thread for the priority 0 and 1 subdirectories of its input queues. It also starts a second scanner thread for the priority 2-7 subdirectories.

  • Page 77: Optimizing The Routing Queue

    4 Select Use 2nd Mail Priority Scanner to provide separate MTA scanner threads for administrative messages and high priority user messages vs. regular and low priority messages. These settings can be used separately (creating three MTA scanner threads) or together (creating four MTA scanner threads).

  • Page 78: Adjusting The Maximum Number Of Active Router Threads

    (gwinprog). As messages arrive in the routing queue, it starts additional routers as needed, within parameters you can set. Section 43.3.1, “Adjusting the Maximum Number of Active Router Threads,” on page 680 Section 43.3.2, “Adjusting the Maximum Number of Idle Router Threads,” on page 680 MTA Web Console You can view the current contents of the routing queue from the Status...
  • Page 79 3 Decrease the number of seconds in the Attach Retry field if you want the MTA to try to contact closed locations more often. Increase the number of seconds in Attach Retry field if you want the MTA to try to contact closed locations less often.
  • Page 80 682 GroupWise 7 Administration Guide...

  • Page 81: Using Mta Startup Switches

    Using MTA Startup Switches ® You can override settings provided in ConsoleOne by using startup switches in the MTA startup file. When you run the Agent Installation program, an initial MTA startup file is created in the agent installation directory. It is named using the first 8 characters of the domain name with a .mta extension.
  • Page 82 NetWare MTA Linux MTA Windows MTA ConsoleOne Settings /language --language /language /liveremote --liveremote /liveremote /log --log /log Log File Path /logdays --logdays /logdays Max Log File Age /logdiskoff --logdiskoff /logdiskoff Logging Level /loglevel --loglevel /loglevel Logging Level /logmax --logmax /logmax Max Log Disk Space /lrconn --lrconn...

  • Page 83: File Name

    MTA program. On Linux, the startup file always resides in the /opt/novell/groupwise/agents/share directory. The startup file must reside on the same server where the MTA is installed.
  • Page 84 /defaultroutingdomain- --defaultroutingdomain /defaultroutingdomain-inethub inethub inethub 44.7 /dn ® Specifies the Novell eDirectory distinguished name of the NetWare MTA object to facilitate logging into remote servers and authenticating to eDirectory. It can be used instead of the /user password switches. NetWare MTA...
  • Page 85 See also /fast4. 44.9 /fast4 Causes the MTA to monitor and process the priority 2 and 3 subdirectories with a separate scanner thread from the priority 4 through 7 subdirectories. See Section 43.2.3, “Adjusting the Number of MTA Scanner Threads for the Domain and Post Offices,” on page 678.

  • Page 86: Http Port

    NetWare MTA Linux MTA Windows MTA Syntax: /httppassword- --httppassword /httppassword- unique_password unique_password unique_password Exampl /httppassword-AgentWatch --httppassword AgentWatch /httppassword-AgentWatch See also /httpuser, /httpport, /httprefresh, and /httpssl. 44.13 /httpport Sets the HTTP port number used for the MTA to communicate with your Web browser. The default is 7180;...
  • Page 87 Example /ip-172.16.5.18 --ip 172.16.5.18 /ip-172.16.5.18 /ip-”mtasvr.provo.novell.com” --ip “mtasvr.provo.novell.com” /ip-”mtasvr.provo.novell.com” 44.18 /keyfile Specifies the full path to the private file used to provide secure SSL communication between the MTA and other programs. See Section 41.2.3, “Securing the Domain with SSL Connections to the MTA,”...
  • Page 88 Linux MTA Windows MTA Syntax: /language-code --language code /language-code Example: /language-es --language de /language-fr The table below lists the valid language codes. Contact your local Novell sales office for information about language availability. Language Language Language Language Code Code Arabic Hungarian...
  • Page 89 Specifies the directory where the MTA will store its log files. The default location varies by platform. NetWare: mslocal subdirectory in the directory specified by the /work switch Linux: /var/log/novell/groupwise/domain_name.mta Windows: mslocal subdirectory in the directory specified by the /work switch For more information, see Section 42.3, “Using MTA Log Files,” on page 665.
  • Page 90 NetWare MTA Linux MTA Windows MTA Example: /logdays-5 --logdays 10 /logdays-14 See also /log, /loglevel, /logdiskoff, and /logmax. 44.24 /logdiskoff Turns off disk logging for the MTA so no information about the functioning of the MTA is stored on disk. The default is for logging to be turned on. See Section 42.3, “Using MTA Log Files,”...
  • Page 91 44.27 /lrconn Specifies the maximum number of simultaneously connected Remote client users the MTA can accept. The default is 25. See Section 41.2.2, “Enabling Live Remote,” on page 629. NetWare MTA Linux MTA Windows MTA Syntax: /lrconn-number --lrconn number /lrconn-number Example: /lrconn-50 --lrconn 75...
  • Page 92 See also /maxidlerouters. 44.31 /messagelogdays Sets the number of days you want MTA message log files to remain on disk before being automatically deleted. The default is 7 days. See Section 41.4.2, “Enabling MTA Message Logging,” on page 643. NetWare MTA Linux MTA Windows MTA Syntax:...
  • Page 93 44.34 /messagelogsettings Enables MTA message logging. See Section 41.4.2, “Enabling MTA Message Logging,” on page 643. NetWare MTA Linux MTA Windows MTA Syntax: /messagelogsettings-codes --messagelogsettings codes /messagelogsettings-codes Example: /messagelogsettings-e --messagelogsettings e /messagelogsettings-e See also /messagelogpath, /messagelogdays, and /messagelogmaxsize. 44.35 /msgtranssl Enables secure SSL communication between the MTA and the POAs in its domain.
  • Page 94 NetWare MTA Linux MTA Windows MTA Syntax: /noerrormail --noerrormail /noerrormail 44.39 /nondssync Disables eDirectory user synchronization. See Section 41.4.1, “Using eDirectory User Synchronization,” on page 638. NetWare MTA Linux MTA Windows MTA Syntax: /nondssync --nondssync 44.40 /norecover Disables automatic database recovery. The default is for automatic database recovery to be turned on.
  • Page 95 44.43 --show Starts the Linux MTA with a server console interface similar to that provided for the NetWare and Windows MTAs. This user interface requires that the X Window System and Open Motif be running on the Linux server. The --show switch cannot be used in the MTA startup file. Therefore, the MTA never runs with a user interface if it is started automatically whenever the server restarts.
  • Page 96 44.47 /tcpwaitdata Sets the maximum number of seconds the MTA attempts to send data over a TCP/IP connection to another MTA. The default is 20. See Section 43.1.2, “Adjusting the MTA Wait Intervals for Slow TCP/IP Connections,” on page 676. NetWare MTA Linux MTA Windows MTA...
  • Page 97 deleting users, etc.), skipping the virus scanning of administrative messages can speed up processing of users’ e-mail messages. NetWare MTA Linux MTA Windows MTA Syntax: /vsnoadm --vsnoadm /vsnoadm 44.51 /work Specifies the directory where the MTA creates its local working directory (mslocal). The default is the domain directory.

This manual is also suitable for:

Groupwise 7 message transfer agent

Table of Contents