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

 

Multiple TCP/IP Addresses

By default, ListManager will listen for connections on all TCP/IP addresses on the machine it is running on.

 

If you would like to limit ListManager to only some of your TCP/IP addresses, you can enter them here. If you enter several TCP/IP addresses, separate each address with a carriage return.

 

You will need to restart the server after saving your changes in order for them to take effect.

 

When ListManager starts up, it will check your configured Tcl port (default is 2021) for each of the TCP/IP addresses it listens to, to determine if another program is currently using that port and TCP/IP address combination. Two programs cannot both listen to the same TCP/IP address and port. If there is a conflict, ListManager will inform you of the problem.

 

One reason to use the Multiple TCP/IP addresses feature is if you want to have ListManager coexist with a mail server also running on your machine. If your mail server can be made to only listen to a specific TCP/IP address , then you can have ListManager listen to the other address(es), and the two programs can coexist on your machine.

 

Note: By default, the web interface uses the loopback address (127.0.0.1) to talk to the server on the same machine. If you specify IP addresses to use, you want to list 127.0.0.1 as one of the IP addresses, so that the web interface can continue to function.
 

Forward Mail

Optionally forward non-Lyris mail to another SMTP server.

This setting allows ListManager to coexist with another SMTP server on the same machine.

 

For instance, if the machine you want to run ListManager on has a mail server running on it (i.e. Sendmail or Post.Office) and you want this machine to continue running a mail server, this setting will allow ListManager to coexist with your mail server.

 

Before ListManager can be installed, you will need to configure your mail server to listen to a different port than port 25 for receiving mail. Once this is done, you can install ListManager and instruct it with this "Forward Mail" feature to pass non-Lyris mail onto your regular mail server. Mail sending and receiving from both ListManager and your regular mail server is unaffected. In this way, both ListManager and your mail server can coexist peacefully on the same machine.

 

For this "Forward Mail" setting, specify the TCP/IP address and port number.

 

For example: "127.0.0.1 2025" forwards non-Lyris mail to an SMTP server running on the same machine on port 2025. This is a common setting when ListManager is coexisting with a mail server on the same machine.

 

Another example: "207.105.7.62 25" forwards non-Lyris mail to an SMTP server running on a different machine. Thus, mail that isn't for ListManager is forwarded to another mail server for regular processing.

 

See Mail Server Coexistence for more information.

 

Forwarding Orders

Forwarding orders allow ListManager to receive email for a given email address, and forward that email to another email address.

 

For example, you might want to define an "administrator" (or "admin") email address on your server and have it forwarded to your personal email address.

You can define as many forwarding orders as you like, each one separated by a carriage return. Each forwarding order has two parts: the first part is the email address you want ListManager to match on (the address on the ListManager) and the second part (separated by a space) is the email address to forward email to.

 

Here is an example of two forwarding orders that forward mail from "admin" and "administrator" on a server named "server5.lyris.net":

 

admin@server5.lyris.net bob@yourcompany.com
administrator@server5.lyris.net bob@yourcompany.com

 

You can specify multiple people to forward to, by separating each destination email address with a comma. One use of this feature might be to make a "cross-posting" address for multiple lists. Mail sent to this address could automatically be forwarded to several mailing lists. Another use of this feature is if there are several administrators who should receive the same email.

 

Here is an example:

 

admins@lyris.net bob@yourcompany.com,jane@yourcompany.com

 

When forwarding to multiple recipients, be sure to separate each recipient address with a single comma, with no spaces between each email address; otherwise your forwarding order will not work.

 

Incoming From: Mail Rewrites

Optionally rewrite incoming From: mail addresses using these rules.

 

This feature is useful when your users have slightly varying email addresses. For instance, people's email addresses might sometimes say "bob@example.com" and other times say "bob@mail.example.com". This feature lets you rewrite an email address so that it becomes something else.

 

On each line, specify the string to search for, a space, and then the replacement string. The process is a simple search and replace. If the first string is found, then it is replaced with the second string.

 

You can specify as many rewrites as you like, each on a separate line.

 

For example: "@mail.acme.com @acme.com" would cause the email address jane@mail.acme.com to be rewritten to jane@acme.com.

 

The incoming mail rewrites only apply mail coming into (being delivered to) ListManager. Outgoing mail addresses are not affected.

 

Incoming To: Mail Rewrites

Optionally rewrite incoming To: mail addresses using these rules.

 

This feature is useful for creating aliases. For instance, you may want people to be able to send mail to "listservices@…" and have it delivered to ListManager as "lyris@…"

 

On each line, specify the string to search for, a space, and then the replacement string. The process is a simple search and replace. If the first string is found, then it is replaced with the second string.

 

You can specify as many rewrites as you like, each on a separate line.

 

For example: "listservices@ lyris@" would cause the email address listservices@mail.acme.com to be rewritten to lyris@mail.acme.com.

 

The incoming mail To: rewrites only apply mail coming into (being delivered to) ListManager. Outgoing mail addresses are not affected.

 

Remove ListManager Email Addresses

This option allows you to have ListManager not listen for mail on the addresses you specify.

 

By default, ListManager accepts mail on all sorts of email addresses, such as "subscribe-listname@…" "help@…" "info@…" and many others. If you want ListManager not to respond to messages at these addresses, you can list the addresses that it should not respond to.

 

You can specify as many user names as you like, putting each on a separate line.

 

Note: You do not include the domain name, but just give the user name.

 

Examples:

subscribe-jazztalk
help
info

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

 



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