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

 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

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

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

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




       postmap /etc/postfix/canonical

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

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


       The  optional canonical table specifies an address mapping
       for local and non-local addresses. The mapping is used  by
       the  cleanup(8) daemon.  The address mapping is recursive.

       Normally, the canonical 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/canonical in  order  to  rebuild  the
       indexed file after changing the text file.

       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 below.

       The  canonical  mapping  affects   both   message   header
       addresses (i.e. addresses that appear inside messages) and
       message envelope addresses  (for  example,  the  addresses
       that  are  used in SMTP protocol commands). Think Sendmail
       rule set S3, if you like.

       Typically, one would use the canonical  table  to  replace
       login   names   by  Firstname.Lastname,  or  to  clean  up
       addresses produced by legacy mail systems.

       The canonical mapping is not to be confused  with  virtual
       domain support. Use the virtual(5) map for that purpose.

       The  canonical  mapping  is  not to be confused with local
       aliasing.  Use the aliases(5) map for that purpose.


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

       pattern result
              When  pattern matches a mail address, replace it by
              the corresponding result.

       blank lines and comments
              user@domain is replaced by address. This  form  has
              the highest precedence.

              This  is  useful  to clean up addresses produced by
              legacy mail systems.  It can also be used  to  pro­
              duce  Firstname.Lastname  style  addresses, but see
              below for a simpler solution.

       user address
              user@site is replaced by address when site is equal
              to  $myorigin,  when  site is listed in $mydestina­
              tion, or when it is listed in $inet_interfaces.

              This form is useful for replacing  login  names  by

       @domain address
              Every  address  in  domain  is replaced by address.
              This form has the lowest precedence.

       In all the above forms, when address has the form  @other­
       domain, the result is the same user in otherdomain.


       When a mail address localpart contains the optional recip­
       ient delimiter (e.g., user+foo@domain), the  lookup  order
       becomes: user+foo@domain, user@domain, user+foo, user, and
       @domain.  An unmatched address extension (+foo) is  propa­
       gated to the result of table lookup.


       This  section  describes how the table lookups change when
       the table is given in the form of regular expressions. For
       a  description  of regular expression lookup table syntax,
       see regexp_table(5) or pcre_table(5).

       Each pattern is a regular expression that  is  applied  to
       the entire address being looked up. Thus, user@domain mail
       addresses are not broken up into their  user  and  @domain
       constituent parts, nor is user+foo broken up into user and

       Patterns are applied in the  order  as  specified  in  the
       table,  until  a  pattern is found that matches the search

       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.


       The table format does not understand quoting  conventions.
              Address  mapping  lookup  table  for  envelope  and
              header sender addresses.

       Other parameters of interest:

              The network interface addresses  that  this  system
              receives mail on.  You need to stop and start Post­
              fix when this parameter changes.

              List of address classes  subject  to  masquerading:
              zero  or  more of envelope_sender, envelope_recipi­
              ent, header_sender, header_recipient.

              List of domains that hide  their  subdomain  struc­

              List  of user names that are not subject to address

              List of domains that  this  mail  system  considers

              The domain that is appended to locally-posted mail.

              Give special treatment to owner-xxx and xxx-request


       cleanup(8) canonicalize and enqueue mail
       postmap(1) create mapping table
       virtual(5) virtual domain mapping
       pcre_table(5) format of PCRE tables
       regexp_table(5) format of POSIX regular expression tables


       The  Secure  Mailer  license must be distributed with this


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




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.


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.11 Seconds