Recipient verification allows SpamTitan to verify if a recipient's email address exists before sending them an email. If it does not exist, SpamTitan blocks the email before reaching the mail server (default: recipient verification is disabled).
Recipient verification helps improve the spam block rate by using resources more efficiently and will also help keep your daily license usage count accurate.
Dynamic Recipient Verification (DRV) is the easiest form of recipient verification to use and manage and is recommended to enable this as part of your SpamTitan setup. Follow the steps below to enable DRV on a domain.
For dynamic recipient verification to work, your mail server must initially be configured to reject invalid addresses. These are links to external guides that to you enable recipient filtering on common mail servers:
Microsoft Exchange Server 2010 . If you use a default standalone installation of Microsoft Exchange Server 2010 without an Edge Transport server, anti-spam functionality is not installed. To enable, see Enable Anti-Spam Functionality on a Hub Transport Server .
Microsoft Office365: To use DRV in SpamTitan Gateway, Directory Based Edge Blocking (DBEB) must be enabled in Office365 so that RCPT TO probes to invalid email addresses are rejected. You can then enable DRV in SpamTitan Gateway and the verification server will simply be your Office365 FQDN, just like the destination server.
To enable DBEB, see Use Directory Based Edge Blocking to reject messages sent to invalid recipients .
Once recipient verification has been enabled on your mail server, select your domain from the All Domains table and select the Domain Configuration tab.
From Recipient Verification, select Dynamic.
Select Save Changes.