SmarterMail 4.x Help
This documentation is for a product that is no longer supported by SmarterTools.

General Settings

The General Settings page is where you control many of the global settings for the SmarterMail server. This page is tabbed for easy editing. No settings will be saved until you click on the Save button.

NOTE: For first time users, we recommend the first change to be the System Admin Username and the System Admin Password on the Administrator tab to avoid anyone getting into your system using the default login.


Administrator

Username - This is the login name associated with the System Administrator account for the SmarterMail Server. You will use this name instead of a full email address when logging in as the System Administrator.

Old Password - In order to change the System Administrator password you must the current password associated with the System Administrator account. Passwords are case-sensitive.

New Password - Enter the desired password for the System Administrator account. Passwords are case-sensitive.

Confirm New Password - Verify the desired password for the System Administrator account. Passwords are case-sensitive.


Server Info

Host Name - Enter the host name of this server. It is sent to connecting servers to identify the server. Host names should be in the format computername.domain.com.

Postmaster Mailbox - Every mail server requires a main email for the postmaster. This is usually the owner or Administrator of SmarterMail.

IP of Primary / Secondary DNS - Enter the IP address of the DNS servers. If left blank, the DNS server information will be pulled from the the Windows Networking settings (Recommended).


Security

Allow Relay - If you are concerned about spam mailers using the relay function to send mail through your server or do not want any other mail server to use your SMTP server as a gateway, you can set the type of relays you will allow, or completely disallow mail relay completely:

  • Nobody - This option will restrict mail sent to only work via SMTP authentication, and with accounts on the local SmarterMail Server except for IPs on the White List.
  • Only Local Users (Recommended) - Limits relay access to users (email accounts) for a valid domain on your SmarterMail Server.
  • Only Local Domains - Limits relay access only to mail hosts (domains) on your SmarterMail Server.
  • Anyone - Allows any other mail server to pass messages through your mail server, increasing the chances of your mail server being used for sending large volumes of messages with domains not associated with your local mail server. Selecting this option turns off statistics for all domains, due to the high amount of messages that are passed through the mail server with an open relay.

Auto Responsers - Allows you to restrict what types of auto-responses are permitted for the system. Certain anti-spam organizations are starting to block those servers that auto-respond to spam traps. To reduce the possibility of this occurring, set the auto-response option to be as restrictive as your clients will permit.

Content Filter Bouncing - As with auto-responses, certain anti-spam organizations also blacklist those servers that send bounce messages back to spam trap accounts. SmarterTools recommends setting this option to be as restrictive as your clients will allow.

Catch-Alls - Check the "Enable bounces and auto-responders for email messages sent to catch-all accounts" if you rely on auto-responders being sent when a message comes in through a catch-all. In general, this is a bad idea, so it should be left unchecked unless your situation specifically requires it.

Password Strength Requirements - The System Administrator is able to set the requirements for passwords and, as a result, all users must adhere to those standards. The password options available to the System Administrator are: minimum length, upper and lower case letters, numbers, and symbols.

Redirect Log Outs - This feature allows System Administrators to redirect users who log out to a certain URL. The redirect options available are:

  • Redirect to Server URL on log out.
  • Allow Domain Administrators to override the redirect URL

Spool

Spool Path - This is the full path in which messages are stored prior to delivery. If you are using a real-time virus scanner, this is the path that must be scanned in order to properly handle viruses.

SubSpools - Subspools allows SmarterMail to work around the NTFS limitation of 30,000 objects in an individual folder. SmarterMail will utilize subspools by allocating up to 10,000 messages per subspool.

Delivery Delay - This option will hold mail in its spool for this amount of time prior to sending the mail. The benefit of a delivery delay is so that if you have a secondary service, like a virus checker, that needs access to the mail prior to its delivery, you give the secondary service ample time to interact with the message prior to it leaving the mail server.

Time Between Retries - When the mail server is unable to contact the receiving server, the email attempting to be sent is held for a period of time before attempting to be resent. This is the time between retries. Users can specify multiple retry times to resend emails before it is bounced. By default, this is set to 4 times - 15min, 30min, 60 min and 90 min.

Command-line file to run on new mail - Enter the full path to an executable you wish to process incoming messages with. Use %filepath as an argument to pass the path to the email file to the executable. It is important to set a reasonable delivery delay to prevent SmarterMail from attempting to deliver the message while the executable is still accessing it. It is safe for the executable to delete the message to prevent delivery. Example: If you set this field to "c:\program files\myexe.exe %filepath", the program myexe.exe will be launched with the full path to the spool file as its first argument. The command will not be executed if the Enabled box is not checked.

Command-line timeout - The amount of time, in seconds, that the server will wait while waiting for information from the remote server. In general, a timeout between 45 to 75 seconds should suffice.