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

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, 180 guest(s) and 0 member(s) that are online.

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

  

pcre_table



SYNOPSIS

       pcre:/etc/postfix/filename

       postmap -q "string" pcre:/etc/postfix/filename

       postmap -q - pcre:/etc/postfix/filename <inputfile


DESCRIPTION

       The  Postfix  mail system uses optional tables for address
       rewriting or mail routing. These tables are usually in dbm
       or  db  format. Alternatively, lookup tables can be speci­
       fied in Perl Compatible Regular Expression form.

       To find out what types of lookup tables your Postfix  sys­
       tem supports use the postconf -m command.

       To   test  lookup  tables,  use  the  postmap  command  as
       described in the SYNOPSIS above.

       The general form of a PCRE table is:

       /pattern/flags result
              When pattern matches a search string, use the  cor­
              responding result value.

       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.

       if /pattern/flags

       if !/pattern/flags

       endif  Match   the  search  string  against  the  patterns
              between if and endif, if and  only  if  the  search
              string   matches  (does  not  match)  pattern.  The
              if..endif can nest.

              Note: do not prepend whitespace to patterns  inside
              if..endif.

       Each  pattern  is  a  perl-like  regular  expression.  The
       expression delimiter can be any character, except  whites­
       pace  or  characters that have special meaning (tradition­
       ally the forward slash is used).  The  regular  expression
       can contain whitespace.
              respectively, in addition to matching at the  start
              and end of the subject string.

       s (default: on)
              Toggles the PCRE_DOTALL flag. When this flag is on,
              the .  metacharacter matches the newline character.
              With  Postfix  versions prior to 20020528, The flag
              is off by default, which is inconvenient for multi-
              line message header matching.

       x (default: off)
              Toggles  the  pcre extended flag. When this flag is
              on, whitespace in the  pattern  (other  than  in  a
              character class) and characters between a # outside
              a character class and the  next  newline  character
              are  ignored.  An escaping backslash can be used to
              include a whitespace or # character as part of  the
              pattern.

       A (default: off)
              Toggles  the PCRE_ANCHORED flag.  When this flag is
              on, the pattern is forced to  be  "anchored",  that
              is, it is constrained to match only at the start of
              the string which is being  searched  (the  "subject
              string").  This  effect  can  also  be  achieved by
              appropriate constructs in the pattern itself.

       E (default: off)
              Toggles the  PCRE_DOLLAR_ENDONLY  flag.  When  this
              flag  is  on,  a  $  metacharacter  in  the pattern
              matches only at the  end  of  the  subject  string.
              Without  this  flag,  a dollar also matches immedi­
              ately before the final character if it is a newline
              character (but not before any other newline charac­
              ters). This flag is ignored if PCRE_MULTILINE  flag
              is set.

       U (default: off)
              Toggles the ungreedy matching flag.  When this flag
              is on, the  pattern  matching  engine  inverts  the
              "greediness"  of  the  quantifiers so that they are
              not greedy by default, but become  greedy  if  fol­
              lowed  by  "?".   This  flag can also set by a (?U)
              modifier within the pattern.

       X (default: off)
              Toggles the PCRE_EXTRA flag.  When this flag is on,
              any  backslash  in  a pattern that is followed by a
              letter that has no special meaning causes an error,
              thus reserving these combinations for future expan­
              sion.

       perl syntax ($1, $2, etc.).   The  macros  in  the  result
       string  may  need  to  be  written as ${n} or $(n) if they
       aren't followed by whitespace.


EXAMPLE SMTPD ACCESS MAP

       # Protect your outgoing majordomo exploders
       /^(?!owner-)(.*)-outgoing@(.*)/ 550 Use ${1}@${2} instead

       # Bounce friend@whatever, except when whatever is our domain (you would
       # be better just bouncing all friend@ mail - this is just an example).
       /^friend@(?!my\.domain)/        550 Stick this in your pipe $0

       # A multi-line entry. The text is sent as one line.
       #
       /^noddy@my\.domain$/
        550 This user is a funny one. You really don't want to send mail to
        them as it only makes their head spin.


EXAMPLE HEADER FILTER MAP

       /^Subject: make money fast/     REJECT
       /^To: friend@public\.com/       REJECT


EXAMPLE BODY FILTER MAP

       # First skip over base 64 encoded text to save CPU cycles.
       # Requires PCRE version 3.
       ~^[[:alnum:]+/]{60,}$~          OK

       # Put your own body patterns here.


SEE ALSO

       regexp_table(5) format of POSIX regular expression tables


AUTHOR(S)

       The PCRE table lookup code was originally written by:
       Andrew McNamara
       andrewm@connect.com.au
       connect.com.au Pty. Ltd.
       Level 3, 213 Miller St
       North Sydney, NSW, Australia

       Adopted and adapted by:
       Wietse Venema
       IBM T.J. Watson Research
       P.O. Box 704
       Yorktown Heights, NY 10598, USA

                                                    PCRE_TABLE(5)
  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


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 help in many different ways.


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