Use two TCP/IP addresses
In this scenario, your machine uses two TCP/IP addresses, and has two machine names. Sendmail will run on one TCP/IP address, and receive mail there. Lyris will run on the other TCP/IP
address, and receive mail there. Each TCP/IP address should resolve to a different DNS host name, so that people can send email to either address by using the appropriate host name.
The advantage of this approach is that it is very straightforward to set up, and does not cause any dependency between sendmail and Lyris. Thus, it is also very reliable.
For example, if your machine is named "apollo.mycorp.com" and has the TCP/IP address "22.214.171.124", you might also assign your machine the TCP/IP address "126.96.36.199" which resolves to
"juno.mycorp.com". Sendmail would be told to use the "apollo" address, and Lyris could use the "juno" address. To the outside world, it will appear that your network has two machines, "apollo" and
"juno", when actually they are one machine, with two TCP/IP addresses.
The first step in implementing this method is to obtain, from your network administrator, a second TCP/IP address, and to make sure that a separate host name is assigned in the DNS for it.
Adding a TCP/IP address on Solaris
Once this is done, you can add this TCP/IP address to your Solaris system with a command such as this:
ifconfig le0:1 188.8.131.52 upin this example, the Ethernet adapter "le0" has been assigned a second address (with the ":1") of "184.108.40.206", and is now up. You might want to add this command to a startup
file, such as /etc/rc2.d/S72inetsvc so that this command executes automatically at system startup.
Adding a TCP/IP address on Irix
As of Irix 6.2, you can add a TCP/IP address using the "alias" option of the "ifconfig" command. The "man ifconfig" documentation page explains it this way:
ifconfig interface alias addr Adding a TCP/IP address on Digital Unix
Establish an additional network address for this interface. This can be useful in permitting a single physical interface to accept packets addressed to several different addresses such as when you
are changing network numbers and you wish to accept packets addressed to the old interface. Another case is when you'd like to have multiple addresses assigned to a single network interface. The
broadcast and netmask options can also be used in conjunction with the alias option. When using aliases you may have to change the configuration of routed, especially if aliases are on different
networks than the primary address. Aliases are added as host entries in the routing tables for routed. See routed(1M) for more information on this.
Digital Unix supports multiple TCP/IP addresses using the "alias" option of the "ifconfig" command. Consult the documentation page for "man ifconfig" for more information.
After you have added a TCP/IP address
The next step is to configure sendmail to use only one TCP/IP address. If you do not do this, sendmail will automatically use all the TCP/IP addresses on your machine, and none will be available
To restrict sendmail to one TCP/IP address, add the following line to your /etc/mail/sendmail.cf file:
substituting your 1st TCP/IP address for 220.127.116.11. This sendmail option is explained in the "Options" chapter of the O'Reilly sendmail book.
You will now need to restart sendmail. Be sure to telnet to port 25 on each TCP/IP address to ensure that sendmail is using the correct TCP/IP address.
apollo# telnet 18.104.22.168 25 You should now go ahead and install Lyris. Once Lyris is installed, you will need to tell Lyris to use the 2nd TCP/IP address. The installation program will give this option, or
you can do this with the "tcpip" command line parameter. For example:
Connected to 22.214.171.124.
Escape character is '^]'.
ESMTP Sendmail 8.8.5/8.8.5; Mon, 16 Jun 1997
apollo# telnet 126.96.36.199 25
telnet: Unable to connect to remote host:
lyris tcpip 188.8.131.52 127.0.0.1The "127.0.0.1" is added so that you can connect to Lyris from your own machine. By default, the Lyris Web Interface uses 127.0.0.1 to connect to the Lyris server. If you do not
specify 127.0.0.1 as a TCP/IP address you will need to edit your "lyris.plc" config file to point to the address.
You are now ready to use Lyris! You can start Lyris in the foreground with the command "lyris start" or in the background with "lyris -bd". The first time, we recommend that you run Lyris in the
foreground, so that any error messages are immediately displayed. If you would like complete debugging information, add the "debug" parameter when you run Lyris, as in: "lyris start debug"