DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Managing mail with MMDF

Setting up MMDF using a mail gateway

This section describes setting up MMDF on a network of machines over a TCP/IP Ethernet, using one machine as the mail gateway. In this case, all machines on the Ethernet will forward all mail to one machine, which will then distribute the mail to the appropriate destination.

The purpose of a mail gateway machine is to provide ease of configuration. Establishing a gateway does not in any way prevent the other machines from communicating directly over the Ethernet with rlogin, telnet, or other communication programs.

The machine names in this example are seine, yangtze, and mekong. The IP addresses and fully qualified domain names of the example computers are:

10.0.118.4 seine.your_company.COM
10.0.118.5 yangtze.your_company.COM
10.0.118.6 mekong.your_company.COM

The gateway machine is mekong.your_company.COM.

This section assumes that all configuration files are in the default, newly installed state--not the state in which they were left after following the steps in ``Setting up MMDF on a TCP/IP network''.

  1. Log in as mmdf on seine.

  2. Check that the domain your_company.COM exists. Because this is the top-level domain used by seine, it will have been added at installation time, but you can use the Domain Administration Manager to check.

  3. In the MMDF Configuration Manager check that the domain name is not hidden by choosing the addressing option:

    ``From: user@seine.your_company.COM''

  4. In the MMDF Configuration Manager, specify that you want to forward mail addressed to unknown hosts over the badhosts channel to the smart host (the gateway) mekong.your_company.COM.

    Host entries for the other machines in the local domain, yangtze.your_company.COM and mekong.your_company.COM, are added by the MMDF Configuration Manager.

    As a result of these steps, these entries will exist in /usr/mmdf/mmdftailor:

       MLDOMAIN	"your_company.COM"
       MLNAME		"seine"
       

    MDMN name="root", dmn="", show="Root Domain", table=rootdom MDMN name="localdom", dmn="your_company.COM", show="your_company.COM Domain", table=localdom

    MCHN show="Local delivery", name=local, que=local, tbl=local, pgm=local, ap=822, mod=imm MCHN show="SMTP Delivery", name=smtp, que=smtp, tbl=smtpchn, pgm=smtp, ap=822, mod=host, confstr="charset=7bit" MCHN show="Smart-host Routing for hosts", name=badhosts, que=badhosts, tbl=smtpchn, pgm=smtp, ap=822, mod=host, confstr="hostname=seine.your_company.COM", host="mekong.your_company.COM"

    This entry will exist in /usr/mmdf/table/root.dom:

       seine.your_company.COM:	seine.your_company.COM
    

    These entries will exist in /usr/mmdf/table/local.dom:

       seine:		seine.your_company.COM
       yangtze:	yangtze.your_company.COM
       mekong:		mekong.your_company.COM
    
    These entries will exist in /usr/mmdf/table/smtp.chn:
       yangtze.your_company.COM	10.0.118.5
       mekong.your_company.COM	10.0.118.6
       seine.your_company.COM		10.0.118.4
    
    As a result of the initial mail configuration, these entries will exist in /usr/mmdf/table/local.chn:
       seine:			seine
       seine.UUCP:		seine
       seine.your_company.COM		seine
    
    Also, the directory /usr/spool/mmdf/lock/home/q.badhosts is created with owner and group mmdf.

  5. Repeat steps 1-4 on yangtze. When you are finished, these entries will exist in /usr/mmdf/mmdftailor:
       MLDOMAIN	"your_company.COM"
       MLNAME		"yangtze"
       

    MDMN name="root", dmn="", show="Root Domain", table=rootdom MDMN name="localdom", dmn="your_company.COM", show="your_company.COM Domain", table=localdom

    MCHN show="Local delivery", name=local, que=local, tbl=local, pgm=local, ap=822, mod=imm MCHN show="SMTP Delivery", name=smtp, que=smtp, tbl=smtpchn, pgm=smtp, ap=822, mod=host, confstr="charset=7bit" MCHN show="Smart-host Routing for hosts", name=badhosts, que=badhosts, tbl=smtpchn, pgm=smtp, ap=822, mod=host, confstr="hostname=yangtze.your_company.COM", host="mekong.your_company.COM"

    The directory /usr/spool/mmdf/lock/home/q.badhosts exists with owner and group mmdf.

    These entries will exist in /usr/mmdf/table/local.dom:

       yangtze:	yangtze.your_company.COM
       seine:		seine.your_company.COM
       mekong:		mekong.your_company.COM
    
    These entries will exist in /usr/mmdf/table/smtp.chn
       seine.your_company.COM		10.0.118.4
       mekong.your_company.COM	10.0.118.6
       yangtze.your_company.COM	10.0.118.5
    
    As a result of the initial mail configuration, these entries will exist in /usr/mmdf/table/local.chn:
       yangtze:		yangtze
       yangtze.UUCP:		yangtze
       yangtze.your_company.COM	yangtze
    

  6. Repeat steps 1-3 on mekong. When you are finished, these entries will exist in /usr/mmdf/mmdftailor:
       MLDOMAIN	"your_company.COM"
       MLNAME		"mekong"
       

    MDMN name="root", dmn="", show="Root Domain", table=rootdom MDMN name="localdom", dmn="your_company.COM", show="your_company.COM Domain", table=localdom

    MCHN show="Local delivery", name=local, que=local, tbl=local, pgm=local, ap=822, mod=imm MCHN show="SMTP Delivery", name=smtp, que=smtp, tbl=smtpchn, pgm=smtp, ap=822, mod=host, confstr="charset=7bit"

    The directory /usr/spool/mmdf/lock/home/q.badhosts exists with owner and group mmdf.

    These entries will exist in /usr/mmdf/table/local.dom:

       yangtze:	yangtze.your_company.COM
       seine:		seine.your_company.COM
       mekong:		mekong.your_company.COM
    
    This entry will exist in /usr/mmdf/table/smtp.chn
       seine.your_company.COM		10.0.118.4
       yangtze.your_company.COM	10.0.118.5
       mekong.your_company.COM	10.0.118.6
    
    As a result of the initial mail configuration, these entries will exist in /usr/mmdf/table/local.chn:
       mekong:			mekong
       mekong.UUCP:		mekong
       mekong.your_company.COM	mekong
    
When you have finished, MMDF is configured on all three machines so that seine and yangtze will forward all unrecognized local mail to mekong, which knows about both machines.

An advantage to this configuration is that if you were to add another machine (for example, columbia) to the network, you would only have to configure columbia and change the setup on mekong. This is simpler than the configuration shown in ``Setting up MMDF on a TCP/IP network'', in which you would have to reconfigure every system on the network. Mail should be addressed using Internet style addresses, such as root@seine.your_company.COM.


Next topic: Setting up MMDF over TCP/IP with a UUCP Internet gateway
Previous topic: Setting up MMDF on a TCP/IP network

© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 26 May 2005