Advanced Recipient Validation

Top  Previous  Next

Normally, recipient validation is performed by checking the envelope recipient name with your normal destination mail server to see if your server will accept messages for that address. This is normally adequate for most installations. However there are situations where this is not possible or practical.

 

When creating a routing definition you can specify an alternate recipient validation server. This can be used in one of two ways.

 

Going around a secondary gateway or relay

 

Let's say you have Alligate installed and all of your connections from the Internet coming directly to the Alligate server. Some installations may have an antivirus Gateway or other relay type device that Alligate would forward messages to which in turn would forward messages to your real destination mail server. This may be an intermediate server or an appliance of some kind. Many of these types of intermediate gateways or relays do not support recipient validation.

 

The alternate recipient validation server can allow you to specify a different server to use for validating recipient addresses. For example, if you have an intermediate Gateway or relay installed, your destination server as defined in the routing table will most likely be the IP address of that box. If it does not support recipient validation you can specify your real mail server as the alternate recipient validation server and Alligate will use that instead of your normal destination server for validating recipient addresses.

 

Using the Alligate recipient validation service

 

We also provide our own recipient validation service. This runs on the Alligate machine and acts as a limited SMTP server for the sole purpose of validating recipient addresses. To use the recipient validation service you must create a text file that contains all the e-mail addresses that you will accept e-mail for. You can create a text file that contains all of your valid e-mail addresses, or you can create numerous text files with various subsets of your valid e-mail addresses and each one.

 

The Alligate recipient validation service will check a directory called ..\Alligate\rvInput and will load and merge all text files it finds in that directory. These files can be changed on the fly and Alligate will detect any changes and reload the files automatically.

 

The Alligate recipient validation service must be started on the Services page of the control panel.

 

information

By default the recipient validation service listens on port 10125. If this needs to be changed for some reason, you can change it by editing the following registry entry:

 

HKEY_LOCAL_MACHINE\SOFTWARE\SolidOak\Alligate\Settings\Verification\RecipValidationServer

 

This is a string value (REG_SZ) and defaults to 10125.

 

 

Related topics: Routing