Defining your local domains

To fully configure the Virtual SMTP server you must first define your local domains and specify the IP address where messages will be delivered. Then you need to test for successful mail deliverability using these settings. This section describes how do perform these tasks.

Defining your local domains 1. Run the Internet Information Services (IIS) manager (from Control Panel's Administrator Tools folder) to

display the Default SMTP Virtual Server in the left pane and select the Domains container. Right mouse click to select New -> Domain as shown below.

2. This will open a window for you to select the type, which should be the default Remote button.

PDF created with pdfFactory Pro trial version www.pdffactory.com

http://www.pdffactory.com


3.

Press to enter the remote SMTP domain name.

4.

Press and you will be returned to the list of domain in the right pane.




5. Next, select your newly created remote domain and right-mouse click to view its properties.

As shown above, select the checkbox to Allow incoming mail to be relayed to this domain and button Forward all mail to smart host . In the field below, enter the IP address for your receiving mail server




surrounded by square brackets.

Press to finish this configuration for the newly created remote domain.

If you have more domains, repeat the above steps for each remote domain. Note that it is fine if the IP addresses for all your remote domains are to the same mail server.

Note:

Some mail servers are unable to accept messages sent by the IIS SMTP Server using the Extended SMTP (ESMTP) standard, indicated by the EHLO command. Known mail servers adhering to the older SMTP standard instead of ESMTP include:

• Microsoft Exchange v5.5 and earlier • Symantec Mail Security™ for SMTP, all versions as of 2004

Thus to avoid any failures when the IIS SMTP Server is attempting to deliver the filtered messages to your downstream mail server, you will need to check the box Send HELO instead of EHLO above.

In most cases, the problem stems from IIS SMTP Server trying to relay messages it receives in binary form because it advertises the ability to support 8BITMIME. You can turn this off by following the steps in this Microsoft KnowledgeBase article Q262168.

All the remote domains you created are under the single (default) SMTP virtual server, and thus the message limits set for this server will apply to all these domains. Among the global settings are limits with the following default values:

• Per-message size limit of 4096 KB

• Per-session (delivery) of 10240 KB • Per-session number of messages to 10

• Per-message number of recipients to 100

If you want to change these values, view the properties of the SMTP virtual server and look on the Messages tab.




Press to finish configuring these limits on message delivery.

Finally, stop (if running) and restart the IIS SMTP Server to make these changes take effect.




Testing mail deliverability to local domains Once your local domains has been defined, you need to test the SMTP virtual server for deliverability to a real address at each local domain. One method to do this is to use the Microsoft Outlook Express email client to send this test message directly to this SMTP virtual server. Other email clients may also be used but this section will describe how to use Outlook Express 6 to perform this testing.

Warning:

If you are trying to test mail delivery to non-local (remote) domains on the Internet, you will need to add the IP address of the Outlook Express machine onto the IIS SMTP Server's Relay list. This is because the IIS SMTP Server is set to prevent relaying by default, and your Outlook Express testing to remote domains would appear as a relay attempt. Click here to find out how to set this up.

1. Create a mail account in Outlook Express by selecting Tools -> Accounts.




2.

When the Internet Accounts window appears, select the Mail tab and pressing .

3. This will invoke the Internet Connection Wizard to prompt you for various pieces of information.

• Your display name




• Your email address

• The incoming and outgoing mail server which is this Praetor machine's IP address. Use a fictitious IP address for the incoming mail since we are simply testing outbound SMTP directly to the Praetor machine




• Account login and password for inbound mail retrieval

Note:




The important information to enter in the above is the IP address of the outgoing mail server. This is because the SMTP server being configured has no POP3 or IMAP server operational for retrieval of incoming mail.

As a result you will get errors when your email client attempts to retrieve incoming messages stored on the SMTP server. It cannot authenticate successfully.

This is just fine since all we are trying to do is configure the email client software to directly send test messages to the SMTP server.

4.

When completed, click .

5. Compose the test message to a valid address in your domain.

Press to send the message.

6. Use your normal email client to verify that the message was properly relayed by the SMTP virtual server and

sent to your specified mail server (in step 5 of setting up the new domain properties for the SMTP virtual server.)




If mail deliverability is unsuccessful, you will need to get it to work before proceeding with Praetor installation.

Testing mail deliverability to non-local domains Before you can successfully test deliverability to non-local (remote) domains on the Internet, you will need to configure the IIS SMTP Server so that it does not see your test message from Outlook Express as a relay attempt.

To avoid this problem you will need to add the IP address of the Outlook Express machine so that it is permitted to use IIS as a mail relay. This is done via the IIS Manager by selecting the SMTP Server properties, specifically those shown on the Access tab.




Press on the button and enter the IP address of the Outlook Express test machine in the field shown below.




Install process overview

Warning:

You should not attempt to perform the installation remotely via technologies such as Windows Remote Desktop (formerly Terminal Services) or similar remote control products. Doing so may cause the wrong security settings to be used and Praetor may function incorrectly or erratically.

Even Microsoft's own Service Pack 4 for MSDE cannot be installed using a Remote Desktop client!

Also, recording a CDR with the downloaded Praetor files will not allow you to perform the installation directly from the read-only CDR. You must copy the files onto your local drive and run the SETUP from that location.

This chapter describes the installation process for the different scenarios possible, all of which will be performed automatically by the Praetor installer. However, before the main Praetor filter can be installed, the installer will check to verify that other components are present and performs the following:

1. Install the blank Praetor SQL databases 2. Update the Bayesian database with the default word list 3. Install PLGV, the Personal Log Viewer web application

This can be seen in the following initial screen.

After pressing the installer then begins to check if you have the requisite Microsoft components also installed and that you are logged in with administrator privileges. Should the Praetor installer determine that you




are missing either the .NET Framework v1.1 or a local SQL Server (e.g. the free Microsoft SQL Desktop Engine or MSDE), then it will download those components from the Microsoft website and install them. This can be seen in this sample screen with SQL Server missing.

To avoid this long download from within the Praetor installer, CMS strongly recommends that you have these Microsoft components already installed before attempting to install Praetor. You can find the download links here.

Note:

When upgrading from Praetor v1.5, CMS recommends that you get a new machine with Windows machine. In this way you can introduce it into your existing email stream transparently.

If you insist on installing Praetor G2 on your existing Windows 2000/XP-based Praetor v1.5 machine, you would need to:

1. Shut down Praetor v1.5 to take it off-line so it is no longer listening for incoming email on port 25.

2. Make sure the SMTP Virtual Server is installed and operationally receiving mail on port 25.

3. Use MODLIST to export your lists by invoking it as follows: MODLIST /EXPLISTS:MyList.TXT

4. Copy of the Praetor.DAT, PraetorScript.TXT, and MyList.TXT files to a backup location thereby preserving your rules and lists.

5. De-install the Praetor v1.5 to prevent conflicts in Praetor's subcomponents.

6. Install this new Praetor version in the standalone manner outlined below.

Please click on the pictured links below for your selected process.

1. Installing Praetor on a standalone Windows machine (recommended) This is also applicable for Exchange v5.5 and any non-Windows 2000 based mail systems including Lotus Domino, Novell GroupWise, Sendmail, or other SMTP mail server. In this configuration Praetor can filter both inbound and outbound email. For a discussion why CMS recommends this, click here.




2. Installing Praetor directly on the Exchange 2000 or 2003 server In this configuration Praetor can filter only inbound email.

3. Installing Praetor directly on a Windows 2000-based Domino server In this configuration Praetor can filter only inbound email.







Defining your local domains

Documents