Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
HP & 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, 70 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/access

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

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


       The  optional access table directs the Postfix SMTP server
       to selectively  reject  or  accept  mail.  Access  can  be
       allowed  or  denied for specific host names, domain names,
       networks, host network addresses or mail addresses.

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


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

       pattern action
              When pattern matches a mail address, domain or host
              address, perform the corresponding action.

       blank lines and comments
              Empty lines and whitespace-only lines are  ignored,
              as  are  lines whose first non-whitespace character
              is a `#'.

       multi-line text
              A logical line starts with non-whitespace  text.  A
              line  that starts with whitespace continues a logi­
              cal line.


       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:


       Note:  lookup  of  the null sender address is not possible
       with some types of lookup table. By default, Postfix  uses
       <>  as  the  lookup  key  for such addresses. The value is
       specified with the smtpd_null_access_lookup_key  parameter
       in the Postfix main.cf file.


       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, domain, user+foo@,
       and user@.


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

              Matches domain.tld.

              The pattern domain.tld also matches subdomains, but
              only when the string smtpd_access_maps is listed in
              the Postfix  parent_domain_matches_subdomains  con­
              figuration setting.  Otherwise, specify .domain.tld
              (note the initial dot) in  order  to  match  subdo­




       net    Matches  any host address in the specified network.
              A network address is a  sequence  of  one  or  more
              octets separated by ".".

              Note:  CIDR  notation (network/netmask) is not sup­
              ported with lookups from indexed files such  as  DB
              or  DBM, or from networked tables such as NIS, LDAP
              or SQL.


       [45]NN text
              Reject the address etc. that matches  the  pattern,
              and respond with the numerical code and text.


       REJECT optional text...
              of the lookup key (such as a subdomain name,  or  a
              network address subnetwork).


       HOLD optional text...
              Place  the message on the hold queue, where it will
              sit until someone either deletes it or releases  it
              for  delivery.  Log the optional text if specified,
              otherwise log a generic message.

              Mail that is placed on hold can  be  examined  with
              the  postcat(1)  command,  and  can be destroyed or
              released with the postsuper(1) command.

              Note: this action currently affects all  recipients
              of the message.


       DISCARD optional text...
              Claim  successful delivery and silently discard the
              message.  Log the optional text if specified,  oth­
              erwise log a generic message.

              Note:  this action currently affects all recipients
              of the message.

       FILTER transport:destination
              After the message is queued, send the  entire  mes­
              sage  through  a  content filter.  More information
              about  content  filters  is  in  the  Postfix  FIL­
              TER_README file.

              Note:   this  action  overrides  the  main.cf  con­
              tent_filter  setting,  and  currently  affects  all
              recipients of the message.

              Apply the named UCE restriction(s) (permit, reject,
              reject_unauth_destination, and so on).


       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 string being looked up. Depending on the appli­
       cation,  that  string  is  an  entire  client hostname, an
       entire client IP address, or an entire mail address. Thus,
       The table format does not understand quoting  conventions.


       postmap(1) create mapping table
       smtpd(8) smtp server
       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


Looking for a "printer friendly" version?



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?
The Linux Tutorial can use your help.


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