Recipient verification enables SpamTitan Cloud servers to check whether a recipient email address exists before an email is sent. If the address does not exist, the email is blocked prior to reaching the mail server (note that recipient verification is disabled by default).
This feature enhances the spam block rate by using resources more efficiently and helps maintain accurate daily license usage counts.
Dynamic Recipient Verification (DRV) is the simplest method for implementing recipient verification and is recommended as part of your SpamTitan Cloud setup.
For dynamic recipient verification to function properly, your mail server must be configured to reject invalid addresses. Below are links to external guides that can assist you in enabling recipient filtering on common mail server software:
- Microsoft Exchange Server 2007
- Microsoft Exchange Server 2010: Note that if you are using a default standalone installation of Microsoft Exchange Server 2010 without an Edge Transport server, anti-spam functionality is not included. To enable it, refer to the guide on enabling anti-spam functionality on a Hub Transport Server.
- Microsoft Office 365: To use DRV with SpamTitan Gateway, Directory Based Edge Blocking (DBEB) must be activated in Office 365, allowing RCPT TO probes for invalid email addresses to be rejected. You can then enable DRV in SpamTitan Gateway, using your Office 365 Fully Qualified Domain Name (FQDN) as the verification server.
For details on enabling DBEB, see the guide on using Directory Based Edge Blocking to reject messages sent to invalid recipients.
- Lotus Domino
- Postfix