Toolvox® x3, Administrator guide – Code Blue TOOLVOX X3 User Manual
Page 116
![background image](https://www.manualsdir.com/files/778590/content/doc116.png)
Code Blue
•
259 Hedcor Street
•
Holland, MI 49423 USA
•
800.205.7186
•
www.codeblue.com
GU-154-F
page 116 of 132
ToolVox® X3
Administrator Guide
Transport Mapping
The term transport refers to the mechanism used to deliver a piece of email. Specifically, SMTP and
UUCP are mail transports supported by Postfix. Transport mapping can be used for a number of
purposes, including SMTP to UUCP gatewaying, operating Postfix on a firewall with forwarding to an
internal mail server, etc.
Transport mapping lookup tables
This option configures the path to a file containing one or more transport mappings. These tables
are like mapping tables, and are converted to a database and used by Postfix in the same way. This
option correlates to the transport_maps directive. This feature is disabled by default. A common
value for this option is /etc/postfix/transport.
To create a new mapping, first define the mapping file. Then click
Add a mapping. If your goal is
to redirect mail to a protected internal host from Postfix running on a firewall, you could enter the
outside domain name into the
Name field, swelltech.com, and then enter into the Maps to... field
the address of the internal machine, smtp:privatehost.swelltech.com. To improve upon this, local
delivery on this machine could be disabled, and increased controls over where and to whom mail
should be accepted. There are more examples in the tutorial section of this chapter.
Relocated Mapping
Using this option, it is possible to notify senders if a local user has moved to another address.
For example, if a user leaves an organization but still receives occasional mail at her local
address, it may be convenient to notify anyone sending mail to the user of the move and new
contact information for that user. Usage is just like the previous types of mappings and won’t be
documented specifically here, although an example of a relocated mapping will be given to display
the types of information that can be provided by this feature.
Let’s say I move from my current company to the far more relaxed atmosphere of the Oval Office.
To make sure all of my friends and clients can keep in touch with me, I could provide a relocated
mapping with a
Name of [email protected] with a Maps to... of [email protected]. While
this won’t redirect mail to me at my new home, it will notify the people trying to contact me that I’ve
changed email addresses. Hopefully they will update their address books and resend their mail to
the new address.
Local delivery
Local delivery is what Postfix does when it reaches the end of its list of mappings and access
controls and still finds that the message is allowed and destined for a user on the local machine
(i.e., a mapping could potentially send the message elsewhere for final delivery, so all mappings, as
well as various access checks, are performed before reaching this stage). This page configures a
number of options relating to how Postfix handles the delivery of mail for local users.
Name of the transport for local deliveries
This configures the name of the transport that will be used for delivery to a destination that will
match the $mydestination or $inet_interfaces variables. This can be a simple mailbox drop handled
by the Postfix local delivery agent, or any appropriate delivery command. This option correlates to
the local_transport directive and defaults to the defined transport type named local.