Previous | Next | Contents | Index |
The first step is to add the conversion
channel to the
PMDF configuration file. The entry should have the form:
conversion CONVERSION-DAEMON |
Rewrite rules can be added if desired to make it possible to queue mail
explicitly to the conversion
channel. Something like
conversion $U%conversion.localhostname@CONVERSION-DAEMON conversion.localhostname $U%conversion.localhostname@CONVERSION-DAEMON |
localhostname
is the name of the local PMDF
system, provides the necessary functionality. Once this is done,
addresses of the form
user%host@conversion.localhostname |
conversion
channel regardless of
what the CONVERSIONS
mapping says.
Additional conversion_*
channels may be defined. For
example:
conversion_2 CONVERSION2-DAEMON |
These alternate conversion channels are generally selected using the
CONVERSIONS
mapping table Channel
keyword
(see Table 24-1). If desired, you may also create separate rewrite
rules for each of these alternate conversion channels, similar to the
ones shown above.
A channel named conversion must be
defined to enable conversion channel processing. This channel is used
as the default conversion channel.
|
Note that the conversion
channel and all
conversion_*
channels use a single conversions file (see
Section 24.1.3).
Previous | Next | Contents | Index |