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

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

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

  

regexp_table



SYNOPSIS

       regexp:/etc/postfix/filename

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

       postmap -q - regexp:/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 POSIX 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 Postfix regular expression table is:

       /pattern/flags result

       !/pattern/flags result
              When pattern matches  (does  not  match)  a  search
              string, use the corresponding 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 regular expression enclosed by a pair of
       delimiters.  The regular expression syntax is described in
       re_format(7).  The expression delimiter can be any charac­
       search is done, and user@domain  mail  addresses  are  not
       broken  up  into  their user and domain constituent parts,
       nor is user+foo broken up into user and foo.

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

       Substitution of substrings  from  the  matched  expression
       into the result string is possible using $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

       # Disallow sender-specified routing. This is a must if you relay mail
       # for other domains.
       /[%!@].*[%!@]/       550 Sender-specified routing rejected

       # Postmaster is OK, that way they can talk to us about how to fix
       # their problem.
       /^postmaster@/       OK

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


EXAMPLE HEADER FILTER MAP

       # These were once common in junk mail.
       /^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.
       ~^[[:alnum:]+/]{60,}$~          OK

       # Put your own body patterns here.


SEE ALSO

       pcre_table(5) format of PCRE tables


AUTHOR(S)

       The regexp table lookup code was originally written by:
       LaMont Jones
       lamont@hp.com

       That code was based on the PCRE dictionary contributed by:
       Andrew McNamara
       andrewm@connect.com.au
       connect.com.au Pty. Ltd.
       Level 3, 213 Miller St
       North Sydney, NSW, Australia
  




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