What types of account-verification can SecurityGateway use?
• SMTP ‘call-forward’ verification This method is compatible with all servers, since it uses standard SMTP commands to contact the email server associated with the domain, using the RCPT TO command. Note that your server needs to allow null senders, or ”, for this process to work, as required by the RFC. By default, this type of verification uses SMTP port 25. • Exchange / ActiveDirectory If you are using an Exchange server, or have an ActiveDirectory domain setup, you may use it to verify users exist on the domain. Note, however, that SecurityGateway does not have support for custom search-filter, like in MDaemon. By default, this type of verification uses port 389. • Minger If you are using MDaemon 9.63 or later, you can use the Minger protocol to verify users are valid. More information regarding how to setup Minger can be found at the related article below. By default, this type of verification uses port 4069. • LDAP Server If you have LDaemon, or a third-party LDAP server setup,
