mxClaim

mxClaim can be deployed on a separate IIS SMTP mail relay system or on an Exchange Bridgehead Server. Deployment on an Exchange Mailbox server is possible, but is not supported.

IIS SMTP Relay Deployment

This is the recommended method for deploying mxClaim. Advantages of this deployment method are:

• you can use mxClaim with a wider range of mail servers including Exchange 4.0, 5.0 and 5.5, Lotus Notes, sendmail, etc.
• you can separate your mail disclaimer processing from your mail storage servers, the server where mxClaim is deployed does not have to be dedicated purely to mxClaim, and can also be used to perform virus filtering with a 3rd party mail scanner or to filter spam using mxORB

The system requirements for this method of deployment are as follows:

• Windows 2000 Professional, Server or Advanced Server with the IIS 5.0 SMTP Service
• or Windows Server 2003 (all editions) with the IIS 6.0 SMTP Service
• or Windows XP Professional with the IIS 5.1 SMTP Service

This method of deployment is illustrated below. For more information on this deployment method, read the IIS SMTP relay deployment guide in the documentation.

^ back to top

Exchange Bridgehead Server Deployment

To install mxClaim on a bridgehead server follow the IIS SMTP relay deployment guide in the documentation, but ignore steps one to four.

The system requirements for this method of deployment are as follows:

• Windows 2000 Professional, Server or Advanced Server
• or Windows Server 2003 (all editions)
• Exchange Server 2000 Standard or Enterprise Edition
• or Exchange Server 2003 Standard or Enterprise Edition

^ back to top

Exchange Mailbox Server Deployment

Deploying on your Exchange Mailbox Server system requires configuration of dual SMTP virtual servers (as shown below).

This method of deployment is not recommended. If you choose to deploy mxClaim on your mailbox server then you may experience problems such as outgoing messages stuck in the SMTP queue or disclaimers not being added to messages.

For more information on this method of deployment see the knowledge base.

^ back to top