Gateway Public Host Name: In most installations, this host name should be the DNS entry that you have designated as your highest priority MX, such as "mail.mydomain.com".
Banner Greeting Identifier: Normally the greeting that Alligate sends remote servers is the word "Alligate". Some users may wish to change this greeting to indicate something proprietary to their installation. You can change the greeting that Alligate issues by changing the banner greeting identifier. In the example below the banner greeting identifier is displayed in red.
Generate random banner greeting for maximum security: This option will cause Alligate to generate a random greeting whenever a remote server connects to your Alligate server. This will help to ensure that spammers are unable to tell what Gateway software you are running in case they are able to learn techniques for getting spam through certain products.
Display product version number in banner: Normally as part of Alligate's banner reading it displays the version number of the SMTP Gateway executable. If you do not want the banner to display the version number, check this option. Any example below, the version number is displayed in green.
Display running statistics and banner: By default Alligate will also display running statistics. In the example below, running statistics are displayed in blue. In this example, the running statistics portion of the banner greeting would indicate that Alligate has received 93,000 messages and has been up for 5.3 days.
Validate Recipients: When this option is enabled, when Alligate receives a message from a remote server it will interrogate the local destination server to make sure that your mail server will accept mail for the address in the RCPT TO: portion of the message envelope. Recipient validation uses high speed, reusable verifier threads. Threads are created as necessary to ensure that recipients are verified very quickly. The connection with your mail server remains open and reused if there are any more recipients to verify, so there is very little additional load on the mail server. Recent responses are cached internally so that subsequent recipient validations are handled without connecting to the mail server at all.
Cache Server Responses for x hours: If you are using recipient validation, Alligate can cache validation responses from the local destination server which will increase throughput times and reduce server load. This lets you tell Alligate how long to cache responses.
Limit cached responses to: This option lets you specify the number of validation responses you wish to be cached.
Cache 2xx responses from local servers: This option specifies whether you wish to cache 2xx validation responses from local servers.
Cache 4xx responses from local servers: This option specifies whether you wish to cache 4xx validation responses from local servers. We recommend that you leave this option unchecked. Because 4xx errors are usually temporary, a cached response may take some time to expire in Alligate's internal cache and while the error condition may clear on the mail server, the cached response will be returned.
Cache 5xx responses from local servers: This option specifies whether you wish to cache 5xx validation responses from local servers.
Save recipient cache on shutdown: This option allows you to specify whether the recipient cache should be saved when Alligate's SMTP server is stopped. If you save the recipient cache, it will be reloaded when the server starts again. This will prevent the cache from being lost and a new one started.