Originally designed as a way for universities and government agencies to transport information, the Internet has rapidly become a way of doing business practically everywhere in the world. In the early days of GroupWise, the Internet Mail gateway component of GroupWise was not a cheap option and required upwards of three separate DOS-based PCs to handle Internet mail. With the advent of GroupWise 5.5, you can run the Internet Mail component of GroupWise on either NetWare or Windows NT. For the purposes of this Daily Drill Down, we’ll install the Internet gateway on a NetWare server with a full-time connection to the Internet. I’ll assume you have GroupWise up and running.
If this is your first exposure to connecting to the Internet, you’ll need to complete a few tasks before starting the installation process for the GroupWise Internet Agent (GWIA). First, have TCP/IP installed and configured on the server you’ll install GWIA on. That way, you can ping your default gateway—the router that connects you to your Internet service provider (ISP)—and other hosts on the Internet by host name and IP address.
Next, you’ll need to register a domain name with NetworkSolutions.com or another domain name registrar. The registration should cost you about $70 for the first two years and $35 a year thereafter. Unless you plan to handle your own DNS servers, you’ll need to get the IP addresses and host and domain names of the DNS servers residing at your ISP’s network operations center. After you register your domain name, it can take anywhere from 24 hours to a week for the registered name to filter its way from the root DNS server to all of the attached DNS servers on the Internet. The amount of time will depend on the number of domain names that were registered at the same time as yours. You can perform a whois search on the domain registrar’s site to get a good idea of when the domain is available for use.
During the domain registration process, you can have your ISP set up the domain name on its DNS servers. Or you may choose to set up the domain information on your own DNS servers. You’ll need to create at least two DNS records:
- an A record specifying the host name of the mail server (i.e., MAIL)
- an MX (mail exchange) record listing the host name and preference number for the MX record (normally, this will be 0 when a single MX record is involved)
Installing the GroupWise Internet Agent
The Internet Agent ships on the same CD as the GroupWise client software and NLMs. You can run the installation program from any PC connected to your network. The program will do the following:
- Install the NLMs that make up the Internet Agent.
- Create the NDS object for GWIA.
- Create the startup files for GWIA.
- Test the server for the correct Internet configuration.
You can find the installation program for GWIA on the GroupWise client CD under \INTERNET\GWIA. Double-click on the INSTALL.EXE program to begin the installation process. When the GroupWise Internet Agent Installation Welcome window appears, click the Next button to continue. Review the information on the License Agreement window when it appears, then click the Accept button to proceed.
As I mentioned earlier, you have the option to have GWIA run on either NetWare or NT. For our example, select the NetWare option (it should be the default selection when the Software Platform window appears) and click the Next button.
When you see the NLM Installation Paths window, verify that the drive letter and paths to the directory for the NLMs for GroupWise and the NetWare load script (also known as the AUTOEXEC.NCF file) are correct. The default value is Z:\SYSTEM for both; you shouldn’t change the value unless you have a configuration that requires it to be otherwise. Unlike earlier versions of GroupWise, the installation program doesn’t do its own drive mappings, so you’ll need to make sure that the default drive letter listed—in our case, Z—is mapped to the volume that contains the directory name listed in the input boxes for both options. Once you’ve verified this, click Next to continue.
A window will briefly appear while the GroupWise installation program is trying to discover your current Internet configuration. This window lets you choose to:
- Send the outbound mail directly to the hosts listed in the DNS records for handling mail for a specific domain.
- Go through a relay host (that is, a mail proxy server such as Novell’s BorderManager).
In most cases, you should accept the default option of sending e-mail directly. However, if your company is concerned about your exposure to the Internet, you can use a relay host. This host acts as a mail forwarder between GroupWise and the outside world. Keep in mind that by choosing that option, you add a step or two to the debug process when you have e-mail problems. The time spent debugging this type of problem can get rather expensive. One of my clients recently lost the ability to send and receive mail with its European partner for nearly a week because of a problem that hadn’t been detected in the mail proxy used by the European partner.
With the Send Outbound Mail Directly option selected, click Next. Another window, titled GroupWise Domain, will appear while the GWIA installation program is attempting to learn more about your Internet configuration. Click the discovery button to the right of the Select GroupWise Domain Directory Data field to browse the directory structure until you locate the domain directory for your GroupWise installation. When you’ve located the correct directory for the GroupWise domain information, you should see a grayed-out filename in the Files window next to the name WPDOMAIN.DB. Click the OK button to return to the GroupWise Domain window.
The installation program creates a directory for each gateway that you install on your GroupWise system. The default for the GroupWise Internet Agent is GWIA. Unless you need to name it something else (don’t do this unless you plan on keeping very good notes about your installation and have an excellent understanding of the GroupWise messaging directory structure), click Next. If the directory for the GWIA files doesn’t already exist, the next window will ask you if you’d like to create the directory. Click Yes.
The next window will be titled GroupWise Internet Agent Name. Here you enter the name you want to use for the GWIA object in NDS. Accept the default of GWIA, then click Next.
By now, you should have registered your domain name. In the next window, called Internet Mail Domain Name, go to the User@ field and enter the domain name. Then, click Next to proceed. Another GroupWise discovery process will start to verify that your domain name is correct. You may see an Invalid Internet Host Name window. If you see this window, click the I Will Fix This Problem Later check box, then click Next.
Within a few seconds, you should see the Ready To Install window. Click the Install button to begin the process of copying files from the GroupWise CD to the server on which you’re installing GWIA. A gas-gauge-like display will appear on your screen as the files are being copied. When the process is complete, you will see the Post Installation Task List. During our installation, two tasks appeared: Specify A Post Master and An Invalid Or Unspecified Internet Host Name. Click the Save Task List To A File option and click the Finish button. The file will be saved by default to TASKLIST.TXT in the SYS:SYSTEM directory where you installed GWIA. Somewhere during the completion of this last task, you should hear a beep or a series of beeps from your server. A check of the server will now show that the GroupWise Internet Agent has been loaded; it should be up and running.
Configuring the GroupWise Internet Agent
After starting NWADMIN, locate the GroupWise Domain object and double-click it. When this NDS object expands, a GWIA object will appear. Double-click the GWIA object, and you’ll see all the settings you specified earlier.
To avoid having to set up Internet addressing rules, you can set up an External Foreign Domain. Setting up this domain will automatically tell GroupWise how to handle the e-mail going out to the Internet. To begin, click the Tools menu and select GroupWise System Operations. Double-click the System Connection icon when the GroupWise System Operations window appears. Since we’ve configured only one GroupWise domain, verify that the domain is highlighted and click the Connect button at the bottom of the window. The GroupWise System Connection window will close, and you’ll see the GroupWise System Operations window again. Now, click the Close button to dismiss that window.
At this point, click the Tools menu and select the GroupWise View option. When the GroupWise View window appears, click the upper pane and go to the top of the domain listings. The first item in the list is also known as the GroupWise System Entry. Right-click this entry, highlight the External Domain option, and click OK. When the Create External Domain window appears, enter INET in the External Domain Name field. Then, click the down arrow beside the Domain Type field and select External Foreign from the drop-down list. Next, click the drop-down arrow beside the Version field and select 5.x. Verify that the time zone for the location where the GWIA server is installed is correct. The Link To Domain field should contain the name of the GroupWise Domain NDS object that you can see in the GroupWise View window. Now, click the Create button to create the External Foreign GroupWise object.
In the main NWADMIN window, click the Tools menu and select the GroupWise System Operations option. Double-click the System Connection icon, verify that the GroupWise domain object is highlighted, and click Connect. When you see the GroupWise System Operations window again, click Close. At this point, click the Tools menu in NWADMIN and click the GroupWise Utilities option. In the resulting window, highlight and click on the Link Configuration option. The Link Configuration Tool window will appear. Set the INET External Foreign object in the Direct window under Outbound Links from the GWDomain (or whatever you have called your GroupWise domain). Right-click on INET and select the Edit option. When the Edit Domain Link window appears, change the Link Type from Direct to Gateway. In the Settings area, verify that the Gateway Link is set to GWIA. Finally, click OK.
You should now hear a series of beeps indicating that the Message Transfer Agent on the server on which you’ve installed GroupWise is restarting to effect the configuration changes. Close the Link Configuration and GroupWise View windows.
When you return to the main NWADMIN window, double-click on the GWIA object to open its properties sheet. As you’ll recall, one of the tasks from the Post Installation Task List was to create a postmaster. A postmaster is a special mail address that is supposed to be universally implemented on mail systems. Messages can be sent from the postmaster on one mail system to the postmaster on another mail system without the sender having to know the exact mailbox name on the other system. This mailbox is also used by GroupWise to send system-type messages, such as messages that can’t be delivered.
To create the postmaster, begin by clicking the Gateway Administrators tab. Click the Add button, then click on a user or users that you want to fulfill this role. Next, highlight each username and select the Postmaster check box in the Administrator Role box at the lower part of the window.
To ensure that you’re notified of any undeliverable messages, select the SMTP/MIME Settings tab and click the Undeliverables button. Then, select the Send To Postmaster option. Click OK to submit the changes to the GroupWise Message Transfer Agent.
You can change the format of your users’ e-mail addresses to make the addresses a little easier to work with. To do so, you’ll need to set up the Internet Addressing component in the GroupWise System Operations window. Click Tools, then select the GroupWise System Operations option. Double-click the Internet Addressing icon, then click the drop-down arrow beside the Internet Address Format field. You will see several choices for specifying how your users’ e-mail addresses will appear to the outside world. There is no one right or wrong way for them to appear. For our example, select the UserID@Internet domain name option. Verify that the Internet agent for your GroupWise system appears in the Internet Agent For Outbound SMTP/MIME Messages field. If it doesn’t, click the drop-down arrow beside this field and select the GWIA agent you’ve installed. Next, click the Create button and enter the Internet domain name you want to specify for the users on your GroupWise. Click OK, then click OK again to close the Internet Addressing window.
At this point, you need to decide how your users will send e-mail to others on the Internet. With the External Foreign Domain you set up earlier, users will have to type INET: followed by the Internet e-mail address of the recipient(s). While adding INET: may not be a problem for some users, others may be bothered by it. If you want to avoid complaints, just create a set of Internet addressing rules. You can specify that once a user types an Internet e-mail address, GroupWise will automatically tack on the INET: as the Message Transport Agent picks up the message and hands it off to GWIA. Novell has an excellent TID (Technical Information Document), number 10008444 , which goes into considerable detail on this subject. You may need to specify how you want to handle e-mail to some of the new Internet domains (for example, .cc) that are starting to pop up.
Ronald Nutter is a senior systems engineer in Lexington, KY. He's an MCSE, Novell Master CNE, and Compaq ASE. Ron has worked with networks ranging in size from single servers to multiserver/multi-OS setups, including NetWare, Windows NT, AS/400, 3090, and UNIX. He's also the help desk editor for Network World. If you’d like to contact Ron, send him an e-mail. (Because of the large volume of e-mail that he receives, it's impossible for him to respond to every message. However, he does read them all.)The authors and editors have taken care in preparation of the content contained herein, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for any damages. Always have a verified backup before making any changes.