To set up routing-based authorization for hosts that are not in your domain (your_company.com in this example):
MTBL "world-auth", file="authinfo/world"This declares a table called world-auth that is maintained in the file authinfo/world. This table will contain the authorization information for the world channel.
MCHN your_companywork, auth=free, show="MYNET Network Delivery", ap=822, mod=imm
MCHN world, auth=inblock, auth=dho, indest="world-auth", show="WORLD Delivery", ap=822, mod=immThe ``auth=indest'' parameter specifies that when world is the input channel, MMDF checks the authinfo/world file to verify that the inbound host is authorized to send mail to the destination. See ``Specifying channel authorization levels''.
When you specify the ``auth=dho'' parameter on a channel, MMDF replaces the ``host'' (in host-based authorization) used to check authorization with a route. The route is either from the source or to the destination, depending on which ``auth'' level that you specify. MMDF replaces the local section of the route (the user's name) with the string ``username''. Then, MMDF compares this route to the entries in the table, to determine if the message is authorized or not.
world: username@your_company.com: firstname.lastname@example.org_company.com: email@example.com_company.com: firstname.lastname@example.org_company.com:This table authorizes MMDF to deliver any mail addressed to people in the your_company.com domain arriving or leaving on the world channel. This does not allow mail to pass through the your_companywork channel to a destination outside the your_company.com domain.