The Mercury/32 Mail Transport System is an excellent e-mail server designed to work with networks of all sizes. In the years since Mercury/32 first came on the scene, it has evolved to act independently of server machines and platforms, thus allowing you, the administrator or user, to integrate other e-mail clients such as Outlook 2000 and Eudora 5.0 .In previous articles, I’ve covered how to install and configure Mercury/32 on your NT4 Workstation to work as a LAN mail server. In this article, I’ll show you how to integrate Eudora and Outlook 2000 e-mail clients with Mercury/32 mail server.
For more information on setting up the Mercury Mail Transport System e-mail server, read Paul Garceau’s other articles in this series:
- ”An Exchange alternative: Mercury Mail Transport System can be installed on your client”
- ”Configuring Windows NT 4.0 Workstation to run Mercury Mail Transport System”
- ”Configuring Mercury Mail Transport System to run a LAN-based e-mail server”
Configuring your POP3 Server services for Eudora e-mail clients
To access your POP3 configuration options, start Mercury/32, then from the main console menu, choose Configuration | MercuryP POP3 Server. MercuryP is the POP3 Server module. Note that this dialog box contains an enabled option called Manufacture UNIX-Style Status Headers. For the Eudora 5.0 e-mail client to run, this option must remain enabled. If you do not enable this option, Eudora won’t be able to receive POP3 e-mail from your LAN mail server. Enabling this switch does not affect the functionality of the POP3 server other than to create headers for any e-mail waiting to be picked up by your POP3 client. It is also recommended that you select the Offer Only Unread Mail To Connected Clients option. Selecting this option avoids repeatedly delivering POP3 e-mail.
Modifying Eudora e-mail clients
If you haven’t installed Eudora 5.0, proceed with the installation as normal. When you are asked for the name of your Mail Server (Incoming), provide the fully qualified domain name you added to the Hosts file for your local POP3 Server. When you are asked which SMTP Server (Outgoing) you would like to use, provide the fully qualified domain name you assigned to your local SMTP Server.
If you’ve already installed Eudora and you wish to replace your ISP server with the Mercury/32 Mail Transport System, start Eudora 5.0 and select Tools | Options to see the Options dialog box (Figure A).
|Direct Eudora to the Mercury/32 server by changing settings in the Options dialog box.|
In the Options dialog box, you will notice that the Incoming Mail Server (POP3) and the SMTP Server (Outgoing) are fully qualified domain names. These names are only used locally to determine where Eudora should place the ingoing and outgoing mail from the client. They will not conflict with existing and fully qualified Internet domain names since we are only working on your LAN.
The address I used in Figure A, mail.taliesin.org, is the same name I entered in my Hosts file and is the same domain that the Eudora client will look at when it checks for POP3 mail or sends out SMTP mail. If you need more information about setting addresses, read the previous articles in this series mentioned above. When you’re finished configuring your Eudora 5.0 client, click OK. Eudora is now set up to use your Mercury/32 Mail Transport System.
Configuring the Outlook 2000 e-mail client
Outlook 2000 requires a somewhat different approach when you want to use LAN e-mail services. Normally, Outlook 2000 assumes you will be using the Microsoft Exchange Server as your mail transport service. Therefore, Outlook 2000 defaults to the Corporate And Workgroup setup option. This configuration will not work with the Mercury/32 Mail Transport System.
To avoid the Microsoft Outlook 2000 feature, you must change the setup options at setup time to Internet Only. When you are asked which mail server(s) to use for your e-mail, provide the IP address you assigned to your e-mail server for your Incoming Mail Server (POP3) and your Outgoing Mail Server (SMTP)(Figure B).
|Direct Outlook to your Mercury/32 server’s POP3 and SMTP IP addresses.|
Next, click the Connection tab and click Connect Using My Local Area Network (LAN)(Figure C).
|Allow Outlook to connect using your LAN by clicking Connect Using My Local Area Network (LAN).|
Next, click the General tab. In the E-Mail Address and Reply Address, type the short form of your domain name (Figure D). For example, although you may have set your server to a name such as mail.taliesin.org, if you use an address such as email@example.com, Outlook 2000 will report an error. Instead, the second half of your e-mail should be the shortened form (e.g., taliesin.org). This should be the same value you entered under Internet Name when you were configuring the Mercury Core Module.
|Use the short version of your domain when you enter your e-mail address in Outlook.|
What if Outlook 2000 is already set up to use Exchange Server?
If you’ve already installed Outlook 2000 and want to replace Exchange Server Mail Services with the Mercury/32 Mail Transport System, you need to reconfigure your Outlook 2000 from a Corporate Or Workgroup installation to an Internet Only installation. To do so, follow these steps:
- Open Outlook 2000.
- From the Outlook 2000 console, select Tools | Options. The Options dialog box displays six tabs: Preferences, Mail Services, Mail Format, Spelling, Security, and Other.
- Click the Mail Services tab.
- Click Reconfigure Mail Support.
- Click Internet Only (Figure E).
- Insert the Office 2000 CD in your CD-ROM drive and click Next.
- Follow the prompts and set the mail server IP addresses as outlined in the above section, “Configuring the Outlook 2000 e-mail client.”
|Reconfigure Outlook 2000 from Corporate Or Workgroup to Internet Only.|
Mercury/32 will get your business e-mail up and running for free, and with only a workstation, a bit of time, and a little know-how. This series on the Mercury Mail Transport System has provided you with that know-how. Now that you’ve configured your e-mail clients, you’re ready to begin using the Mercury/32 Mail Transport System as your centralized LAN mail server and enjoying the benefits of this alternative to Microsoft Exchange Server.
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.