Партнёры:
Хостинг:
pcre_table - format of Postfix PCRE tables
postmap -fq "string" pcre:/etc/postfix/filename postmap -fq - pcre:/etc/postfix/filename <inputfile
Alternatively, lookup tables can be specified in Perl Compatible Regular Expression form. In this case, each input is compared against a list of patterns, and when a match is found the corresponding result is returned.
To find out what types of lookup tables your Postfix system supports use the "postconf -m" command.
To test lookup tables, use the "postmap -fq" command as described in the SYNOPSIS above.
The general form of a PCRE table is:
Note: do not prepend whitespace to patterns inside if..endif.
This feature is available in Postfix 2.1 and later.
Note: do not prepend whitespace to patterns inside if..endif.
This feature is available in Postfix 2.1 and later.
Each pattern is a perl-like regular expression. The expression delimiter can be any character, except whitespace or characters that have special meaning (traditionally the forward slash is used). The regular expression can contain whitespace.
By default, matching is case-insensitive, and newlines are not treated as special characters. The behavior is controlled by flags, which are toggled by appending one or more of the following characters after the pattern:
Patterns are applied in the order as specified in the table, until a pattern is found that matches the input string.
Each pattern is applied to the entire input string. Depending on the application, that string is an entire client hostname, an entire client IP address, or an entire mail address. Thus, no parent domain or parent network 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.
Substitution of substrings from the matched expression into the result string is possible using the conventional perl syntax ($1, $2, etc.); specify $$ to produce a $ character as output. The macros in the result string may need to be written as ${n} or $(n) if they aren't followed by whitespace.
Note: since negated patterns (those preceded by !) return a result when the expression does not match, substitutions are not available for negated patterns.
# 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 $1
# 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.
/^Subject: make money fast/ REJECT /^To: friend@public\.com/ REJECT
# First skip over base 64 encoded text to save CPU cycles.
# Requires PCRE version 3.
~^[[:alnum:]+/]{60,}$~ OK
# Put your own body patterns here.
postmap(1), Postfix lookup table manager postconf(5), configuration parameters regexp_table(5), format of POSIX regular expression tables
Use "postconf readme_directory" or "postconf html_directory" to locate this information.
DATABASE_README, Postfix lookup table overview
The PCRE table lookup code was originally written by:
Andrew McNamara
[email protected]
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
|
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |