Manually on the Command Line

To start a new NetWare MTA on the command line:

1. Go to the console of the NetWare server where the NetWare MTA is installed.

   or

   Use Remote Console to access the server:

   1. Press Al+F1 to display the options.

   2. Choose Select a Screen to View.

   3. Choose System Console.

2. Enter the command to load the MTA NLM.

   Syntax: load gwmta.nlm /home [svr\][vol:]\domain_dir

   Example:
   load gwmta.nlm /home-server2\mail:\provo2

   The /home startup switch is required to start the NetWare MTA.

   If the domain or post offices are located on different servers from where the NetWare MTA is running, the /dn switch or the /user and /password switches are also required so the NetWare MTA can log in to those servers. For an alternative to direct access for post offices, see Using TCP/IP Links between a Domain and its Post Offices.

   If the domain is located on a different server from where the NetWare MTA is running, use the /work switch to specify a local directory for the MTA holding queues. The default location is the domain directory, which is not appropriate when the domain is located on a different server from where the NetWare MTA is running.

The NetWare MTA agent console will appear and display normal startup status messages. See Monitoring the MTA.

If the NetWare MTA agent console does not appear, see "Message Transfer Agent Problems" in GroupWise 6.5 Troubleshooting 2: Solutions to Common Problems.

When you start the NetWare MTA as described above, it is configured according to the MTA settings specified in ConsoleOne^®. You can go to ConsoleOne and modify MTA functioning as needed. See Configuring the MTA in ConsoleOne.

With a Startup File

Another way to start the NetWare MTA is to use a startup file. You could use a startup file with the NetWare MTA for the following reasons:

• Overriding MTA settings defined in ConsoleOne
• Controlling the MTA locally without using ConsoleOne
• Adjusting specialized MTA functions that are not controllable from ConsoleOne

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. This initial startup file includes the /home startup switch set to the location of the domain directory.

If the domain or any or its post offices are located on a different server from where the NetWare MTA is running, you must edit the startup file and provide settings for the /user and /password switches so the NetWare MTA can log in to those servers. For an alternative to direct access for post offices, see Using TCP/IP Links between a Domain and its Post Offices. For an alternative to direct access for other domains, see Using TCP/IP Links between Domains.

If the domain serviced by the NetWare MTA is located on a different server from where the NetWare MTA is running, use the /work switch to specify a local directory for the MTA holding queues. The default location is the domain directory, which is not appropriate when the domain is located on a different server from where the NetWare MTA is running.

The MTA startup file can be modified to use other startup switches as needed. Startup switches specified on the command line override those in the startup file. Startup switches in the startup file override corresponding settings in ConsoleOne. See Using MTA Startup Switches.

When you use a startup file, you must include it on the command line when you load the NetWare MTA. For example:

Syntax: load gwmta.nlm @MTA_startup_file

Example: load gwmta.nlm @provo2.mta

In addition to the initial MTA startup file, the Agent Installation program also provides a grpwise.ncf file to load the agents. If you will run only the NetWare MTA, you should edit the grpwise.ncf file to remove the command to load the POA.

Automatically in the autoexec.ncf File

After the NetWare MTA is running smoothly, you should modify the NetWare startup file, autoexec.ncf, to load the NetWare MTA and required NLM programs automatically whenever you restart the server

IMPORTANT:  If you are running the MTA in a Novell cluster, see "Configuring the GroupWise Volume Resource to Load and Unload the Agents" in "Novell Cluster Services" in the GroupWise 6.5 Interoperability Guide for alternative instructions.

1. Edit the autoexec.ncf file in the NetWare sys:\system directory.

2. Add the following command to load the agents:

   grpwise.ncf

   or

   To start the agents in protected mode, add the following command:

   protect grpwise.ncf

3. Save the autoexec.ncf file.

4. If possible, restart the server to verify that the NLM programs and the NetWare MTA are loading properly.

Manually with a User Interface

1. Make sure you are logged in as root.

2. Change to the GroupWise agent bin directory.

   cd /opt/novell/groupwise/agents/bin

3. Enter the following command to start the MTA:

   Syntax:
   ./gwmta --show --home domain_directory &

   Example:
   ./gwmta --show --home /gwsystem/domlnx &

The MTA startup file is created by the Installation Advisor in the /opt/novell/groupwise/agents/share directory and is named after the domain that the MTA services. Because the Installation Advisor prompted you for the domain name and directory, it can set the --home startup switch in the MTA startup file. In the bin directory where the MTA executable is located, you could start the MTA with a command similar to the following example:

./gwmta --show @../share/lnxdom.poa

Manually As a Daemon

1. Make sure you are logged in as root.

2. Change to the /etc/init.d directory.

3. To start the Linux MTA (and perhaps the POA as well, depending on the configuration of the server), enter the following command:

   ./grpwise start

4. To confirm that the agents have started, enter the following command:

   ps -eaf | grep gw

   This lists all GroupWise agent process IDs.

Automatically at System Startup

If you selected Launch GroupWise Agents on System Startup in the Agent Installation program, the Agent Installation program configured your system so that the agents would start automatically each time you restart your server. The Agent Installation program always creates a grpwise startup script in /etc/init.d for starting the agents. To enable automatic startup, the Agent Installation program also creates symbolic links named S99grpwise in the rc3.d and rc5.d directories so that the agents load on restart into level 3 or 5, depending on the configuration of your Linux system.

When the grpwise script runs and starts the agents, it reads the agent startup files in /opt/novell/groupwise/agents/share to check for configuration information provided by startup switches. Because the --show switch cannot be used in the startup files, the agents never run with agent console interfaces when started automatically when the server restarts.

During agent installation, if you specified only a domain and no post offices, only an MTA startup file was created and the grpwise startup script starts only the MTA.

Manually from the Windows Desktop

In Windows, click Start > Programs > GroupWise Agents, then start the Windows MTA.

The Windows MTA agent console should appear and display normal startup status messages. See Monitoring the MTA.

If the Windows MTA agent console does not appear, see "Message Transfer Agent Problems" in GroupWise 6.5 Troubleshooting 2: Solutions to Common Problems.

When you start the Windows MTA as described above, it is configured according to the MTA settings specified in ConsoleOne. You can go to ConsoleOne and modify MTA functioning as needed. See Configuring the MTA in ConsoleOne.

With a Startup File

Another way to start the Windows MTA is to use a startup file. You could use a startup file to configure the MTA for the following reasons:

• Overriding MTA settings defined in ConsoleOne
• Controlling the MTA locally without using ConsoleOne
• Adjusting specialized MTA functions that are not controllable from ConsoleOne

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. This initial startup file includes the /home startup switch set to the location of the domain directory.

The MTA startup file can be modified to use other startup switches as needed. Startup switches in the startup file override corresponding settings in ConsoleOne. See Using MTA Startup Switches.

Automatically in the Windows Startup Group

After the Windows MTA is running smoothly, you should add it to the Windows Startup group to start the Windows MTA automatically whenever you restart your Windows server.

1. In Windows NT, click Start > Settings > Taskbar > Start Menu Programs > Add.

   or

   In Windows 2000, click Start > Settings > Taskbar & Start Menu > Advanced > Add.

2. Browse to the directory where you installed the Windows MTA.

3. Double-click GWMTA.EXE, then add the startup file to the command line.

   Example: gwmta.exe @provo2.mta

4. Click Next.

5. Select the Startup folder, provide a name for the shortcut, then click Finish.

6. If possible, restart the server to verify that the Windows MTA starts when you log in.

Automatically as a Windows Service

To start the GroupWise Windows MTA as a service for the first time after installation:

1. From the Windows desktop, click Start > Settings > Control Panel.

2. Double-click Services, select the MTA service (named after the domain), then click Start.

To make sure the MTA starts automatically each time you restart the server:

1. Click Start > Settings > Control Panel.

2. Double-click Services, select the MTA service (named after the domain), then click Startup.

3. Select Automatic, then click OK.

   Thereafter, you will be able to manage the Windows agents just as you would any other services.