Utilities: Administration: Server: Server Settings: Network Settings: Deliver Email

Max Megabits

The average maximum megabits per second (Mbps) ListManager should use. In some circumstances, ListManager may use all of your bandwidth, limiting other web applications. If you have bandwidth limitations and would like to prevent ListManager from using all of your bandwidth, enter the amount of bandwidth (in Mbps) it should be allowed to used on average.

Note that this feature regulates the average bandwidth used by the server. If you are sending out very large messages, ListManager will send each one as quickly as possible, but then will be idle for a period so that its average bandwidth is what is set here. If you must eliminate large bandwidth spikes as well as regulate your average bandwidth usage, you should consider a hardware solution (a managed switch with rate-limiting).
 

Messages Per Hour

The number of messages your license permits you to send per hour. Contact your account representative at 800-768-2929 or at sales@lyris.com for more information about increasing your mailing speeds.

Max Simultaneous Sends

Controls the number of simultaneous mail sends that can be sent at once. In general, the maximum allowed by your license will be sufficient.

However, if you are finding that your bandwidth is being overtaxed by ListManager, you may want to set Max Simultaneous Sends lower.

If you are running a site that has a very large number of one-off messages, such as autoresponders, or many subscriptions, you may want to increase the number. Contact your account representative at 800-768-2929 or at sales@lyris.com for more information about increasing your max simultaneous sends.

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 six 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, three to five retries are more than enough. It is a good idea to schedule one retry a full 24 hours after the message originally went out, to guard against temporary network outages. 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.

Default Delivery Domain

Whenever ListManager receives a subscription request from a simple name, such as "Bob", rather than rejecting it outright or adding an obviously bad email address to the database, ListManager can append a domain name to it. One example of when this is useful is when you are using ListManager on your internal network, where everybody is on the same domain. If you submitted an add command to the ListManager server, you would only need to include the email account name, as shown below:

login xxxxx
add jazztalk <<
bob
shirley
farnsworth
>>
end

Thus, with a default domain of "company.com", ListManager would append "company.com" to each of bob, shirley, and farnsworth before subscribing them to jazztalk.

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.

A mail server must be listening on the port of the TCP/IP address that you specify. For this setting, you specify an IP address/port combination (not a host name).

You can specify as many relay hosts as you like. Each entry must be separated by a carriage return. If you specify multiple relay hosts ListManager will automatically distribute the mail relay load between them. If you need to send a great deal of mail through a relay host setup, we recommend that you specify several relay hosts.

Example:

207.105.6.2 25

If the relay host is defined but unresponsive when ListManager is started or after changing this setting, you will see a warning on the console and ListManager will be unable to deliver mail.

TCP/IP Address for Outgoing SMTP

This setting determines which IP address will be used for outgoing SMTP connections. If "Any IP Address" is selected, it will use any available IP address for outgoing SMTP connections. Choosing this option sets it to 0.0.0.0, and the operating system then chooses which address to bind to. If specified, the first TCP/IP address specified in the Multiple TCP/IP Addresses setting (in Utilities: Administration: Server Settings: Network Settings: Receive Email) will be used for outgoing SMTP connections.

The text in the HELO command will be based on this setting. If "Any IP Address" is specified then the first TCP/IP address as described above will be used to determine the HELO text. To set the HELO text manually, see Setting Server Options.

This setting is useful when you want to have ListManager send mail out on a different IP address than the ones it listens to. This is required in some configurations where multiple network cards are used.

HELO Text

Specify the string ListManager uses in the HELO portion of the SMTP transaction. Normally, ListManager performs a reverse lookup on the first TCP/IP address of the machine it is running on to determine the HELO string. To 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.

More

1.   Utilities: Administration: Server: Server Settings

1.   Utilities: Administration: Server: Server Settings: Network Settings: Receive Email

2.   Utilities: Administration: Server: Server Settings: Network Settings: Deliver Email

3.   Utilities: Administration: Server: Server Settings: Network Settings: Ports