Retry Timing
Sets how many times this server will retry sending failed messages, and the interval in minutes between these retries. Unless explicitly set, the default retry times are "30,720," meaning the first retry will occur 30 minutes after the first attempt, the second retry after 12 hours, and that a total of 2 retries will be attempted. Retry intervals should be separated by commas:
30,60,90
Each interval measures the time, in minutes, between the previous try and the next try. The smallest acceptable retry interval is five minutes and the largest acceptable retry interval is 1440 minutes (24 hours). Retry intervals which are not within the acceptable range will be ignored. For example, if you have one retry of three minutes, no retries will be attempted.
For example, if you want to establish a retry schedule of 30 minutes, two hours, eight hours, and 24 hours, you would enter the following values:
30,120,480,1440
Please note that the retry interval is measured in relation to the time of the last retry, not the time the message was originally sent.
For most lists, two retries are more than enough. If you are running ListManager for the first time with lists that have many bad email addresses, you may want to have only one retry to make delivery quicker. Once members with bad email addresses have been put on hold and purged (based on your settings in Utilities: List Settings: Automatic Maintenance: Error Mail), your mailing speeds will increase and you may reset the retry timing to less aggressive settings.
This field is limited to one hundred characters for every database except Oracle.
Fallback HELO text
Specifies the string ListManager uses in the HELO portion of the SMTP transaction if ListManager is unable to construct a HELO text from site or DNS information. Normally, ListManager uses the Internet host name for a site to determine the HELO text. If it is unable to do so, ListManager performs a reverse lookup on the first TCP/IP address of the machine it is running on to determine the HELO string. To have ListManager use a different HELO string, specify it here.
Example:
lists.example.com
Changing the HELO text is extremely useful if you are behind a firewall and machines on the Internet cannot resolve the hostname your machine uses.
Configure Relay Hosts
Relay all outbound mail through this mail host rather than doing regular direct delivery.
Lyris strongly recommends that you not use a relay host, because ListManager has been optimized to send mail directly to the Internet. Using a relay host may delay mail delivery, and result in inaccurate delivery reports. Some bounced mail may also be returned to the relay host instead of ListManager, preventing ListManager from handling error mail correctly.
However, some environments need outbound mail to be relayed through a specific host. For instance, your organization might employ a TCP/IP firewall that prevents ListManager from directly delivering mail. In such a case, each application behind the firewall must use a relay host to communicate with the outside.
If the specified relay host(s) listed are unavailable, ListManager will consider the failed delivery attempts as transient failures and will attempt retries according to the retry timing specified above.
NOTE If one or more relay hosts are defined, domain connection limits have no effect