Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Fatherhood.Org

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 175 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

transport



SYNOPSIS

       postmap /etc/postfix/transport

       postmap -q "string" /etc/postfix/transport

       postmap -q - /etc/postfix/transport <inputfile


DESCRIPTION

       The  optional  transport  table  specifies  a mapping from
       email addresses  to  message  delivery  transports  and/or
       relay hosts. The mapping is used by the trivial-rewrite(8)
       daemon.

       This mapping overrides the default routing that  is  built
       into Postfix:

       mydestination
              A  list of domains that is by default delivered via
              $local_transport.

       virtual_mailbox_domains
              A list of domains that is by default delivered  via
              $virtual_transport.

       relay_domains
              A  list of domains that is by default delivered via
              $relay_transport.

       any other destination
              Mail for any other destination is by default deliv­
              ered via $default_transport.

       Normally,  the transport table is specified as a text file
       that serves as  input  to  the  postmap(1)  command.   The
       result,  an  indexed file in dbm or db format, is used for
       fast searching by the mail  system.  Execute  the  command
       postmap  /etc/postfix/transport  in  order  to rebuild the
       indexed file after changing the transport table.

       When the table is provided via other means  such  as  NIS,
       LDAP  or  SQL,  the  same lookups are done as for ordinary
       indexed files.

       Alternatively, the table can be  provided  as  a  regular-
       expression map where patterns are given as regular expres­
       sions. In that case, the lookups are done  in  a  slightly
       different  way as described in section "REGULAR EXPRESSION
       TABLES".


TABLE FORMAT

       The input format for the postmap(1) command is as follows:

       The pattern specifies an email address, a domain name,  or
       a  domain  name  hierarchy, as described in section "TABLE
       LOOKUP".

       The result is of the form transport:nexthop.   The  trans­
       port  field  specifies  a  mail delivery transport such as
       smtp or local. The nexthop field specifies where  and  how
       to deliver mail. More details are given in section "RESULT
       FORMAT".


TABLE LOOKUP

       With lookups from indexed files such as DB or DBM, or from
       networked  tables  such  as NIS, LDAP or SQL, patterns are
       tried in the order as listed below:

       user+extension@domain transport:nexthop
              Mail for user+extension@domain is delivered through
              transport to nexthop.

       user@domain transport:nexthop
              Mail for user@domain is delivered through transport
              to nexthop.

       domain transport:nexthop
              Mail for domain is delivered through  transport  to
              nexthop.

       .domain transport:nexthop
              Mail  for  any  subdomain  of  domain  is delivered
              through transport to  nexthop.  This  applies  only
              when the string transport_maps is not listed in the
              parent_domain_matches_subdomains configuration set­
              ting.   Otherwise, a domain name matches itself and
              its subdomains.

       Note 1: the special pattern * represents any address (i.e.
       it functions as the wild-card pattern).

       Note  2:  the  null  recipient  address  is  looked  up as
       $empty_address_recipient@$myhostname (default: mailer-dae­
       mon@hostname).


RESULT FORMAT

       The  transport field specifies the name of a mail delivery
       transport (the first name of a mail delivery service entry
       in the Postfix master.cf file).

       The  interpretation  of  the  nexthop  field  is transport
       dependent. In the case of SMTP, specify host:service for a
       non-default  server port, and use [host] or [host]:port in
       order to disable MX (mail exchanger) DNS lookups.  The  []
       form is required when you specify an IP address instead of
       In  order to deliver internal mail directly, while using a
       mail relay for all other mail, specify a  null  entry  for
       internal  destinations  (do not change the delivery trans­
       port or the nexthop information) and  specify  a  wildcard
       for all other destinations.

            my.domain    :
            .my.domain   :
            *            smtp:outbound-relay.my.domain

       In  order  to send mail for foo.org and its subdomains via
       the uucp transport to the UUCP host named foo:

            foo.org      uucp:foo
            .foo.org     uucp:foo

       When no nexthop host name is  specified,  the  destination
       domain  name  is  used instead. For example, the following
       directs mail for user@foo.org via the slow transport to  a
       mail  exchanger  for foo.org.  The slow transport could be
       something that runs at most  one  delivery  process  at  a
       time:

            foo.org      slow:

       When no transport is specified, Postfix uses the transport
       that matches the address domain class (see TRANSPORT FIELD
       discussion  above).   The  following  sends  all  mail for
       foo.org and its subdomains to host gateway.foo.org:

            foo.org      :[gateway.foo.org]
            .foo.org     :[gateway.foo.org]

       In the above example, the  []  are  used  to  suppress  MX
       lookups.   The  result  would  likely  point to your local
       machine.

       In the case of delivery via SMTP, one  may  specify  host­
       name:service instead of just a host:

            foo.org      smtp:bar.org:2025

       This  directs  mail  for user@foo.org to host bar.org port
       2025. Instead of a numerical port a symbolic name  may  be
       used.  Specify  [] around the hostname in order to disable
       MX lookups.

       The error mailer can be used to bounce mail:

            .foo.org      error:mail for *.foo.org is not  deliv­
       erable

       table, until a pattern is found that  matches  the  search
       string.

       Results  are  the  same as with indexed file lookups, with
       the additional feature that parenthesized substrings  from
       the pattern can be interpolated as $1, $2 and so on.


CONFIGURATION PARAMETERS

       The  following  main.cf parameters are especially relevant
       to this topic. See the Postfix  main.cf  file  for  syntax
       details  and  for  default  values. Use the postfix reload
       command after a configuration change.

       empty_address_recipient
              The address that is looked up instead of  the  null
              sender address.

       parent_domain_matches_subdomains
              List  of  Postfix features that use domain.tld pat­
              terns  to  match  sub.domain.tld  (as  opposed   to
              requiring .domain.tld patterns).

       transport_maps
              List of transport lookup tables.


SEE ALSO

       postmap(1) create mapping table
       trivial-rewrite(8) rewrite and resolve addresses
       pcre_table(5) format of PCRE tables
       regexp_table(5) format of POSIX regular expression tables


LICENSE

       The  Secure  Mailer  license must be distributed with this
       software.


AUTHOR(S)

       Wietse Venema
       IBM T.J. Watson Research
       P.O. Box 704
       Yorktown Heights, NY 10598, USA

                                                     TRANSPORT(5)
  
Help us cut cost by not downloading the whole site!
Use of automated download sofware ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and therefore is expressedly prohibited. For more details on this, take a look here

Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.04 Seconds