--- /dev/null
+[client]
+password = mysqlfire
+port = 3306
+socket = /var/run/mysql/mysql.sock
+
+[mysqld]
+port = 3306
+socket = /var/run/mysql/mysql.sock
+datadir = /srv/mysql
+
+[mysql.server]
+user=mysql
+basedir=/var/lib
+
+[mysqld_safe]
+log-error=/var/log/mysqld.log
+#pid-file=/var/run/mysqld/mysqld.pid
+
+[mysql]
+no-auto-rehash
+# Remove the next comment character if you are not familiar with SQL
+#safe-updates
+++ /dev/null
-# ACCESS(5) ACCESS(5)
-#
-# NAME
-# access - Postfix access table format
-#
-# SYNOPSIS
-# postmap /etc/postfix/access
-#
-# postmap -q "string" /etc/postfix/access
-#
-# postmap -q - /etc/postfix/access <inputfile
-#
-# DESCRIPTION
-# The optional access(5) 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 addresses or mail addresses.
-#
-# For an example, see the EXAMPLE section at the end of this
-# manual page.
-#
-# Normally, the access(5) 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, or lookups can be directed to TCP-based server. In
-# that case, the lookups are done in a slightly different
-# way as described below under "REGULAR EXPRESSION TABLES"
-# and "TCP-BASED TABLES".
-#
-# TABLE FORMAT
-# 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.
-#
-# EMAIL ADDRESS PATTERNS
-# 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:
-#
-# user@domain
-# Matches the specified mail address.
-#
-# domain.tld
-# Matches domain.tld as the domain part of an email
-# address.
-#
-# 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 (note that this is the default
-# for some versions of Postfix). Otherwise, specify
-# .domain.tld (note the initial dot) in order to
-# match subdomains.
-#
-# user@ Matches all mail addresses with the specified user
-# part.
-#
-# 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.
-#
-# EMAIL ADDRESS EXTENSION
-# 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@.
-#
-# HOST NAME/ADDRESS PATTERNS
-# 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:
-#
-# domain.tld
-# 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-
-# mains.
-#
-# net.work.addr.ess
-#
-# net.work.addr
-#
-# net.work
-#
-# net Matches the specified IPv4 host address or subnet-
-# work. An IPv4 host address is a sequence of four
-# decimal octets separated by ".".
-#
-# Subnetworks are matched by repeatedly truncating
-# the last ".octet" from the remote IPv4 host address
-# string until a match is found in the access table,
-# or until further truncation is not possible.
-#
-# NOTE 1: The information in the access map should be
-# in canonical form, with unnecessary null characters
-# eliminated. Address information must not be
-# enclosed with "[]" characters.
-#
-# NOTE 2: use the cidr lookup table type to specify
-# network/netmask patterns. See cidr_table(5) for
-# details.
-#
-# net:work:addr:ess
-#
-# net:work:addr
-#
-# net:work
-#
-# net Matches the specified IPv6 host address or subnet-
-# work. An IPv6 host address is a sequence of three
-# to eight hexadecimal octet pairs separated by ":".
-#
-# Subnetworks are matched by repeatedly truncating
-# the last ":octetpair" from the remote IPv6 host
-# address string until a match is found in the access
-# table, or until further truncation is not possible.
-#
-# NOTE 1: the truncation and comparison are done with
-# the string representation of the IPv6 host address.
-# Thus, not all the ":" subnetworks will be tried.
-#
-# NOTE 2: The information in the access map should be
-# in canonical form, with unnecessary null characters
-# eliminated. Address information must not be
-# enclosed with "[]" characters.
-#
-# NOTE 3: use the cidr lookup table type to specify
-# network/netmask patterns. See cidr_table(5) for
-# details.
-#
-# IPv6 support is available in Postfix 2.2 and later.
-#
-# ACCEPT ACTIONS
-# OK Accept the address etc. that matches the pattern.
-#
-# all-numerical
-# An all-numerical result is treated as OK. This for-
-# mat is generated by address-based relay authoriza-
-# tion schemes.
-#
-# REJECT ACTIONS
-# 4NN text
-#
-# 5NN text
-# Reject the address etc. that matches the pattern,
-# and respond with the numerical three-digit code and
-# text. 4NN means "try again later", while 5NN means
-# "do not try again".
-#
-# REJECT optional text...
-# Reject the address etc. that matches the pattern.
-# Reply with $reject_code optional text... when the
-# optional text is specified, otherwise reply with a
-# generic error response message.
-#
-# DEFER_IF_REJECT optional text...
-# Defer the request if some later restriction would
-# result in a REJECT action. Reply with "450 optional
-# text... when the optional text is specified, other-
-# wise reply with a generic error response message.
-#
-# This feature is available in Postfix 2.1 and later.
-#
-# DEFER_IF_PERMIT optional text...
-# Defer the request if some later restriction would
-# result in a an explicit or implicit PERMIT action.
-# Reply with "450 optional text... when the optional
-# text is specified, otherwise reply with a generic
-# error response message.
-#
-# This feature is available in Postfix 2.1 and later.
-#
-# OTHER ACTIONS
-# restriction...
-# Apply the named UCE restriction(s) (permit, reject,
-# reject_unauth_destination, and so on).
-#
-# 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.
-#
-# This feature is available in Postfix 2.0 and later.
-#
-# DUNNO Pretend that the lookup key was not found. This
-# prevents Postfix from trying substrings of the
-# lookup key (such as a subdomain name, or a network
-# address subnetwork).
-#
-# This feature is available in Postfix 2.0 and later.
-#
-# FILTER transport:destination
-# After the message is queued, send the entire mes-
-# sage through the specified external content filter.
-# The transport:destination syntax is described in
-# the transport(5) manual page. More information
-# about external content filters is in the Postfix
-# FILTER_README file.
-#
-# Note: this action overrides the main.cf con-
-# tent_filter setting, and currently affects all
-# recipients of the message.
-#
-# This feature is available in Postfix 2.0 and later.
-#
-# 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: use "postsuper -r" to release mail that was
-# kept on hold for a significant fraction of $maxi-
-# mal_queue_lifetime or $bounce_queue_lifetime, or
-# longer.
-#
-# Note: this action currently affects all recipients
-# of the message.
-#
-# This feature is available in Postfix 2.0 and later.
-#
-# PREPEND headername: headervalue
-# Prepend the specified message header to the mes-
-# sage. When this action is used multiple times, the
-# first prepended header appears before the second
-# etc. prepended header.
-#
-# Note: this action does not support multi-line mes-
-# sage headers.
-#
-# Note: this action must be used before the message
-# content is received; it cannot be used in
-# smtpd_end_of_data_restrictions.
-#
-# This feature is available in Postfix 2.1 and later.
-#
-# REDIRECT user@domain
-# After the message is queued, send the message to
-# the specified address instead of the intended
-# recipient(s).
-#
-# Note: this action overrides the FILTER action, and
-# currently affects all recipients of the message.
-#
-# This feature is available in Postfix 2.1 and later.
-#
-# WARN optional text...
-# Log a warning with the optional text, together with
-# client information and if available, with helo,
-# sender, recipient and protocol information.
-#
-# This feature is available in Postfix 2.1 and later.
-#
-# REGULAR EXPRESSION TABLES
-# 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,
-# no parent domain or parent network search is done,
-# 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 ta-
-# ble, until a pattern is found that matches the search
-# string.
-#
-# Actions 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.
-#
-# TCP-BASED TABLES
-# This section describes how the table lookups change when
-# lookups are directed to a TCP-based server. For a descrip-
-# tion of the TCP client/server lookup protocol, see tcp_ta-
-# ble(5). This feature is not available up to and including
-# Postfix version 2.2.
-#
-# Each lookup operation uses the entire query string once.
-# 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, 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.
-#
-# Actions are the same as with indexed file lookups.
-#
-# EXAMPLE
-# The following example uses an indexed file, so that the
-# order of table entries does not matter. The example per-
-# mits access by the client at address 1.2.3.4 but rejects
-# all other clients in 1.2.3.0/24. Instead of hash lookup
-# tables, some systems use dbm. Use the command "postconf
-# -m" to find out what lookup tables Postfix supports on
-# your system.
-#
-# /etc/postfix/main.cf:
-# smtpd_client_restrictions =
-# check_client_access hash:/etc/postfix/access
-#
-# /etc/postfix/access:
-# 1.2.3 REJECT
-# 1.2.3.4 OK
-#
-# Execute the command "postmap /etc/postfix/access" after
-# editing the file.
-#
-# BUGS
-# The table format does not understand quoting conventions.
-#
-# SEE ALSO
-# postmap(1), Postfix lookup table manager
-# smtpd(8), SMTP server
-# postconf(5), configuration parameters
-# transport(5), transport:nexthop syntax
-#
-# README FILES
-# Use "postconf readme_directory" or "postconf html_direc-
-# tory" to locate this information.
-# SMTPD_ACCESS_README, built-in SMTP server access control
-# DATABASE_README, Postfix lookup table overview
-#
-# LICENSE
-# The Secure Mailer license must be distributed with this
-# software.
-#
-# AUTHOR(S)
-# Wietse Venema
-# IBM T.J. Watson Research
-# P.O. Box 704
-# Yorktown Heights, NY 10598, USA
-#
-# ACCESS(5)
# Begin /etc/aliases
-MAILER-DAEMON postmaster
-postmaster root
+MAILER-DAEMON: postmaster
+postmaster: root
-root LOGIN
# End /etc/aliases
+++ /dev/null
-# CANONICAL(5) CANONICAL(5)
-#
-# NAME
-# canonical - Postfix canonical table format
-#
-# SYNOPSIS
-# postmap /etc/postfix/canonical
-#
-# postmap -q "string" /etc/postfix/canonical
-#
-# postmap -q - /etc/postfix/canonical <inputfile
-#
-# DESCRIPTION
-# The optional canonical(5) table specifies an address map-
-# ping for local and non-local addresses. The mapping is
-# used by the cleanup(8) daemon, before mail is stored into
-# the queue. The address mapping is recursive.
-#
-# Normally, the canonical(5) 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, or lookups can be directed to TCP-based server. In
-# that case, the lookups are done in a slightly different
-# way as described below under "REGULAR EXPRESSION TABLES"
-# and "TCP-BASED TABLES".
-#
-# By default the canonical(5) mapping affects both message
-# header addresses (i.e. addresses that appear inside mes-
-# sages) and message envelope addresses (for example, the
-# addresses that are used in SMTP protocol commands). Think
-# Sendmail rule set S3, if you like. This is controlled
-# with the canonical_classes parameter.
-#
-# NOTE: Postfix versions 2.2 and later rewrite message head-
-# ers from remote SMTP clients only if the client matches
-# the local_header_rewrite_clients parameter, or if the
-# remote_header_rewrite_domain configuration parameter spec-
-# ifies a non-empty value. To get the behavior before Post-
-# fix 2.2, specify "local_header_rewrite_clients =
-# static:all".
-#
-# Typically, one would use the canonical(5) table to replace
-# login names by Firstname.Lastname, or to clean up
-# addresses produced by legacy mail systems.
-#
-# The canonical(5) mapping is not to be confused with vir-
-# tual domain support. Use the virtual(5) map for that pur-
-# pose.
-#
-# The canonical(5) mapping is not to be confused with local
-# aliasing. Use the aliases(5) map for that purpose.
-#
-# TABLE FORMAT
-# 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
-# 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.
-#
-# TABLE SEARCH ORDER
-# 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:
-#
-# user@domain address
-# Replace user@domain 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
-# Replace user@site by address when site is equal to
-# $myorigin, when site is listed in $mydestination,
-# or when it is listed in $inet_interfaces or
-# $proxy_interfaces.
-#
-# This form is useful for replacing login names by
-# Firstname.Lastname.
-#
-# @domain address
-# Replace other addresses in domain by address. This
-# form has the lowest precedence.
-#
-# RESULT ADDRESS REWRITING
-# The lookup result is subject to address rewriting:
-#
-# o When the result has the form @otherdomain, the
-# result becomes the same user in otherdomain.
-#
-# o When "append_at_myorigin=yes", append "@$myorigin"
-# to addresses without "@domain".
-#
-# o When "append_dot_mydomain=yes", append ".$mydomain"
-# to addresses without ".domain".
-#
-# ADDRESS EXTENSION
-# 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.
-#
-# The propagate_unmatched_extensions parameter controls
-# whether an unmatched address extension (+foo) is propa-
-# gated to the result of table lookup.
-#
-# REGULAR EXPRESSION TABLES
-# 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
-# foo.
-#
-# Patterns are applied in the order as specified in the ta-
-# ble, until a pattern is found that matches the search
-# string.
-#
-# 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.
-#
-# TCP-BASED TABLES
-# This section describes how the table lookups change when
-# lookups are directed to a TCP-based server. For a descrip-
-# tion of the TCP client/server lookup protocol, see tcp_ta-
-# ble(5). This feature is not available up to and including
-# Postfix version 2.2.
-#
-# Each lookup operation uses the entire address once. 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 foo.
-#
-# Results are the same as with indexed file lookups.
-#
-# BUGS
-# The table format does not understand quoting conventions.
-#
-# CONFIGURATION PARAMETERS
-# The following main.cf parameters are especially relevant.
-# The text below provides only a parameter summary. See
-# postconf(5) for more details including examples.
-#
-# canonical_classes
-# What addresses are subject to canonical address
-# mapping.
-#
-# canonical_maps
-# List of canonical mapping tables.
-#
-# recipient_canonical_maps
-# Address mapping lookup table for envelope and
-# header recipient addresses.
-#
-# sender_canonical_maps
-# Address mapping lookup table for envelope and
-# header sender addresses.
-#
-# propagate_unmatched_extensions
-# A list of address rewriting or forwarding mecha-
-# nisms that propagate an address extension from the
-# original address to the result. Specify zero or
-# more of canonical, virtual, alias, forward,
-# include, or generic.
-#
-# Other parameters of interest:
-#
-# inet_interfaces
-# The network interface addresses that this system
-# receives mail on. You need to stop and start Post-
-# fix when this parameter changes.
-#
-# local_header_rewrite_clients
-# Rewrite message header addresses in mail from these
-# clients and update incomplete addresses with the
-# domain name in $myorigin or $mydomain; either don't
-# rewrite message headers from other clients at all,
-# or rewrite message headers and update incomplete
-# addresses with the domain specified in the
-# remote_header_rewrite_domain parameter.
-#
-# proxy_interfaces
-# Other interfaces that this machine receives mail on
-# by way of a proxy agent or network address transla-
-# tor.
-#
-# masquerade_classes
-# List of address classes subject to masquerading:
-# zero or more of envelope_sender, envelope_recipi-
-# ent, header_sender, header_recipient.
-#
-# masquerade_domains
-# List of domains that hide their subdomain struc-
-# ture.
-#
-# masquerade_exceptions
-# List of user names that are not subject to address
-# masquerading.
-#
-# mydestination
-# List of domains that this mail system considers
-# local.
-#
-# myorigin
-# The domain that is appended to locally-posted mail.
-#
-# owner_request_special
-# Give special treatment to owner-xxx and xxx-request
-# addresses.
-#
-# remote_header_rewrite_domain
-# Don't rewrite message headers from remote clients
-# at all when this parameter is empty; otherwise, re-
-# write message headers and append the specified
-# domain name to incomplete addresses.
-#
-# SEE ALSO
-# cleanup(8), canonicalize and enqueue mail
-# postmap(1), Postfix lookup table manager
-# postconf(5), configuration parameters
-# virtual(5), virtual aliasing
-#
-# README FILES
-# Use "postconf readme_directory" or "postconf html_direc-
-# tory" to locate this information.
-# DATABASE_README, Postfix lookup table overview
-# ADDRESS_REWRITING_README, address rewriting guide
-#
-# LICENSE
-# The Secure Mailer license must be distributed with this
-# software.
-#
-# AUTHOR(S)
-# Wietse Venema
-# IBM T.J. Watson Research
-# P.O. Box 704
-# Yorktown Heights, NY 10598, USA
-#
-# CANONICAL(5)
+++ /dev/null
-# GENERIC(5) GENERIC(5)
-#
-# NAME
-# generic - Postfix generic table format
-#
-# SYNOPSIS
-# postmap /etc/postfix/generic
-#
-# postmap -q "string" /etc/postfix/generic
-#
-# postmap -q - /etc/postfix/generic <inputfile
-#
-# DESCRIPTION
-# The optional generic(5) table specifies an address mapping
-# that applies when mail is delivered. This is the opposite
-# of canonical(5) mapping, which applies when mail is
-# received.
-#
-# Typically, one would use the generic(5) table on a system
-# that does not have a valid Internet domain name and that
-# uses something like localdomain.local instead. The
-# generic(5) table is then used by the smtp(8) client to
-# transform local mail addresses into valid Internet mail
-# addresses when mail has to be sent across the Internet.
-# See the EXAMPLE section at the end of this document.
-#
-# The generic(5) 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).
-#
-# Normally, the generic(5) 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/generic" 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, or lookups can be directed to TCP-based server. In
-# that case, the lookups are done in a slightly different
-# way as described below under "REGULAR EXPRESSION TABLES"
-# and "TCP-BASED TABLES".
-#
-# TABLE FORMAT
-# 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
-# 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.
-#
-# TABLE SEARCH ORDER
-# 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:
-#
-# user@domain address
-# Replace user@domain by address. This form has the
-# highest precedence.
-#
-# user address
-# Replace user@site by address when site is equal to
-# $myorigin, when site is listed in $mydestination,
-# or when it is listed in $inet_interfaces or
-# $proxy_interfaces.
-#
-# @domain address
-# Replace other addresses in domain by address. This
-# form has the lowest precedence.
-#
-# RESULT ADDRESS REWRITING
-# The lookup result is subject to address rewriting:
-#
-# o When the result has the form @otherdomain, the
-# result becomes the same user in otherdomain.
-#
-# o When "append_at_myorigin=yes", append "@$myorigin"
-# to addresses without "@domain".
-#
-# o When "append_dot_mydomain=yes", append ".$mydomain"
-# to addresses without ".domain".
-#
-# ADDRESS EXTENSION
-# 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.
-#
-# The propagate_unmatched_extensions parameter controls
-# whether an unmatched address extension (+foo) is propa-
-# gated to the result of table lookup.
-#
-# REGULAR EXPRESSION TABLES
-# 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
-# foo.
-#
-# Patterns are applied in the order as specified in the
-# table, until a pattern is found that matches the search
-# string.
-#
-# 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.
-#
-# TCP-BASED TABLES
-# This section describes how the table lookups change when
-# lookups are directed to a TCP-based server. For a descrip-
-# tion of the TCP client/server lookup protocol, see
-# tcp_table(5). This feature is not available up to and
-# including Postfix version 2.2.
-#
-# Each lookup operation uses the entire address once. 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 foo.
-#
-# Results are the same as with indexed file lookups.
-#
-# EXAMPLE
-# The following shows a generic mapping with an indexed
-# file. When mail is sent to a remote host via SMTP, this
-# replaces his@localdomain.local by his ISP mail address,
-# replaces her@localdomain.local by her ISP mail address,
-# and replaces other local addresses by his ISP account,
-# with an address extension of +local (this example assumes
-# that the ISP supports "+" style address extensions).
-#
-# /etc/postfix/main.cf:
-# smtp_generic_maps = hash:/etc/postfix/generic
-#
-# /etc/postfix/generic:
-# his@localdomain.local hisaccount@hisisp.example
-# her@localdomain.local heraccount@herisp.example
-# @localdomain.local hisaccount+local@hisisp.example
-#
-# Execute the command "postmap /etc/postfix/generic" when-
-# ever the table is changed. Instead of hash, some systems
-# use dbm database files. To find out what tables your sys-
-# tem supports use the command "postconf -m".
-#
-# BUGS
-# The table format does not understand quoting conventions.
-#
-# CONFIGURATION PARAMETERS
-# The following main.cf parameters are especially relevant.
-# The text below provides only a parameter summary. See
-# postconf(5) for more details including examples.
-#
-# smtp_generic_maps
-# Address mapping lookup table for envelope and
-# header sender and recipient addresses while deliv-
-# ering mail via SMTP.
-#
-# propagate_unmatched_extensions
-# A list of address rewriting or forwarding mecha-
-# nisms that propagate an address extension from the
-# original address to the result. Specify zero or
-# more of canonical, virtual, alias, forward,
-# include, or generic.
-#
-# Other parameters of interest:
-#
-# inet_interfaces
-# The network interface addresses that this system
-# receives mail on. You need to stop and start Post-
-# fix when this parameter changes.
-#
-# proxy_interfaces
-# Other interfaces that this machine receives mail on
-# by way of a proxy agent or network address transla-
-# tor.
-#
-# mydestination
-# List of domains that this mail system considers
-# local.
-#
-# myorigin
-# The domain that is appended to locally-posted mail.
-#
-# owner_request_special
-# Give special treatment to owner-xxx and xxx-request
-# addresses.
-#
-# SEE ALSO
-# postmap(1), Postfix lookup table manager
-# postconf(5), configuration parameters
-# smtp(8), Postfix SMTP client
-#
-# README FILES
-# Use "postconf readme_directory" or "postconf html_direc-
-# tory" to locate this information.
-# ADDRESS_REWRITING_README, address rewriting guide
-# DATABASE_README, Postfix lookup table overview
-# STANDARD_CONFIGURATION_README, configuration examples
-#
-# LICENSE
-# The Secure Mailer license must be distributed with this
-# software.
-#
-# HISTORY
-# A genericstable feature appears in the Sendmail MTA.
-#
-# This feature is available in Postfix 2.2 and later.
-#
-# AUTHOR(S)
-# Wietse Venema
-# IBM T.J. Watson Research
-# P.O. Box 704
-# Yorktown Heights, NY 10598, USA
-#
-# GENERIC(5)
mail_owner = postfix
setgid_group = postdrop
-#myhostname = host.domain.tld
+myhostname = ipfire.localdomain
myorigin = $myhostname
inet_interfaces = all
#proxy_interfaces =
-mydestination = $myhostname, localhost.$mydomain, localhost, mysql:/etc/postfix/mysql-mydestination.cf
+mydestination = $myhostname, localhost, mysql:/etc/postfix/mysql-mydestination.cf
unknown_local_recipient_reject_code = 550
mynetworks_style = host
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
-virtual_alias_maps = hash:/etc/postfix/virtual, mysql:/etc/postfix/mysql-virtual.cf
-sender_canonical_maps = hash:/etc/postfix/canonical, mysql:/etc/postfix/mysql-canonical.cf
+virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf
+sender_canonical_maps = mysql:/etc/postfix/mysql-canonical.cf
# Cyrus 2.1.5 (Amos Gouaux)
# Also specify in main.cf: cyrus_destination_recipient_limit=1
cyrus unix - n n - - pipe
- user=cyrus argv=/usr/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
+ user=cyrus argv=/usr/lib/cyrus/deliver -e -r ${sender} -m ${extension} ${user}
#
# See the Postfix UUCP_README file for configuration details.
#
+++ /dev/null
-# RELOCATED(5) RELOCATED(5)
-#
-# NAME
-# relocated - Postfix relocated table format
-#
-# SYNOPSIS
-# postmap /etc/postfix/relocated
-#
-# DESCRIPTION
-# The optional relocated(5) table provides the information
-# that is used in "user has moved to new_location" bounce
-# messages.
-#
-# Normally, the relocated(5) 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/relocated" in order to rebuild the
-# indexed file after changing the relocated 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, or lookups can be directed to TCP-based server. In
-# that case, the lookups are done in a slightly different
-# way as described below under "REGULAR EXPRESSION TABLES"
-# and "TCP-BASED TABLES".
-#
-# Table lookups are case insensitive.
-#
-# TABLE FORMAT
-# The input format for the postmap(1) command is as follows:
-#
-# o An entry has one of the following form:
-# pattern new_location
-# Where new_location specifies contact information
-# such as an email address, or perhaps a street
-# address or telephone number.
-#
-# o Empty lines and whitespace-only lines are ignored,
-# as are lines whose first non-whitespace character
-# is a `#'.
-#
-# o A logical line starts with non-whitespace text. A
-# line that starts with whitespace continues a logi-
-# cal line.
-#
-# TABLE SEARCH ORDER
-# 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:
-#
-# user@domain
-# Matches user@domain. This form has precedence over
-# all other forms.
-#
-# user Matches user@site when site is $myorigin, when site
-# is listed in $mydestination, or when site is listed
-# in $inet_interfaces or $proxy_interfaces.
-#
-# @domain
-# Matches other addresses in domain. This form has
-# the lowest precedence.
-#
-# ADDRESS EXTENSION
-# 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.
-#
-# REGULAR EXPRESSION TABLES
-# This section describes how the table lookups change when
-# the table is given in the form of regular expressions or
-# when lookups are directed to a TCP-based server. For a
-# description of regular expression lookup table syntax, see
-# regexp_table(5) or pcre_table(5). For a description of the
-# TCP client/server table lookup protocol, see tcp_table(5).
-# This feature is not available up to and including Postfix
-# version 2.2.
-#
-# 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
-# foo.
-#
-# Patterns are applied in the order as specified in the ta-
-# ble, until a pattern is found that matches the search
-# string.
-#
-# 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.
-#
-# TCP-BASED TABLES
-# This section describes how the table lookups change when
-# lookups are directed to a TCP-based server. For a descrip-
-# tion of the TCP client/server lookup protocol, see tcp_ta-
-# ble(5). This feature is not available up to and including
-# Postfix version 2.2.
-#
-# Each lookup operation uses the entire address once. 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 foo.
-#
-# Results are the same as with indexed file lookups.
-#
-# BUGS
-# The table format does not understand quoting conventions.
-#
-# CONFIGURATION PARAMETERS
-# The following main.cf parameters are especially relevant.
-# The text below provides only a parameter summary. See
-# postconf(5) for more details including examples.
-#
-# relocated_maps
-# List of lookup tables for relocated users or sites.
-#
-# Other parameters of interest:
-#
-# inet_interfaces
-# The network interface addresses that this system
-# receives mail on. You need to stop and start Post-
-# fix when this parameter changes.
-#
-# mydestination
-# List of domains that this mail system considers
-# local.
-#
-# myorigin
-# The domain that is appended to locally-posted mail.
-#
-# proxy_interfaces
-# Other interfaces that this machine receives mail on
-# by way of a proxy agent or network address transla-
-# tor.
-#
-# SEE ALSO
-# trivial-rewrite(8), address resolver
-# postmap(1), Postfix lookup table manager
-# postconf(5), configuration parameters
-#
-# README FILES
-# Use "postconf readme_directory" or "postconf html_direc-
-# tory" to locate this information.
-# DATABASE_README, Postfix lookup table overview
-# ADDRESS_REWRITING_README, address rewriting guide
-#
-# LICENSE
-# The Secure Mailer license must be distributed with this
-# software.
-#
-# AUTHOR(S)
-# Wietse Venema
-# IBM T.J. Watson Research
-# P.O. Box 704
-# Yorktown Heights, NY 10598, USA
-#
-# RELOCATED(5)
+++ /dev/null
-# TRANSPORT(5) TRANSPORT(5)
-#
-# NAME
-# transport - Postfix transport table format
-#
-# SYNOPSIS
-# postmap /etc/postfix/transport
-#
-# postmap -q "string" /etc/postfix/transport
-#
-# postmap -q - /etc/postfix/transport <inputfile
-#
-# DESCRIPTION
-# The optional transport(5) table specifies a mapping from
-# email addresses to message delivery transports and/or
-# relay hosts. The mapping is used by the trivial-rewrite(8)
-# daemon.
-#
-# This mapping overrides the default routing that is built
-# into Postfix:
-#
-# mydestination
-# A list of domains that is by default delivered via
-# $local_transport. This also includes domains that
-# match $inet_interfaces or $proxy_interfaces.
-#
-# virtual_mailbox_domains
-# A list of domains that is by default delivered via
-# $virtual_transport.
-#
-# relay_domains
-# A list of domains that is by default delivered via
-# $relay_transport.
-#
-# any other destination
-# Mail for any other destination is by default deliv-
-# ered via $default_transport.
-#
-# Normally, the transport(5) 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/transport" in order to rebuild the
-# indexed file after changing the transport 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, or lookups can be directed to TCP-based server. In
-# that case, the lookups are done in a slightly different
-# way as described below under "REGULAR EXPRESSION TABLES"
-# and "TCP-BASED TABLES".
-#
-# TABLE FORMAT
-# The input format for the postmap(1) command is as follows:
-#
-# pattern result
-# When pattern matches the recipient address or
-# domain, use the corresponding result.
-#
-# 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.
-#
-# The pattern specifies an email address, a domain name, or
-# a domain name hierarchy, as described in section "TABLE
-# LOOKUP".
-#
-# The result is of the form transport:nexthop and specifies
-# how or where to deliver mail. This is described in section
-# "RESULT FORMAT".
-#
-# TABLE SEARCH ORDER
-# 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:
-#
-# user+extension@domain transport:nexthop
-# Deliver mail for user+extension@domain through
-# transport to nexthop.
-#
-# user@domain transport:nexthop
-# Deliver mail for user@domain through transport to
-# nexthop.
-#
-# domain transport:nexthop
-# Deliver mail for domain through transport to nex-
-# thop.
-#
-# .domain transport:nexthop
-# Deliver mail for any subdomain of domain through
-# transport to nexthop. This applies only when the
-# string transport_maps is not listed in the par-
-# ent_domain_matches_subdomains configuration set-
-# ting. Otherwise, a domain name matches itself and
-# its subdomains.
-#
-# Note 1: the special pattern * represents any address (i.e.
-# it functions as the wild-card pattern).
-#
-# Note 2: the null recipient address is looked up as
-# $empty_address_recipient@$myhostname (default: mailer-dae-
-# mon@hostname).
-#
-# Note 3: user@domain or user+extension@domain lookup is
-# available in Postfix 2.0 and later.
-#
-# RESULT FORMAT
-# The lookup result is of the form transport:nexthop. The
-# transport field specifies a mail delivery transport such
-# as smtp or local. The nexthop field specifies where and
-# how to deliver mail.
-#
-# The transport field specifies the name of a mail delivery
-# transport (the first name of a mail delivery service entry
-# in the Postfix master.cf file).
-#
-# The interpretation of the nexthop field is transport
-# dependent. In the case of SMTP, specify a service on a
-# non-default port as host:service, and disable MX (mail
-# exchanger) DNS lookups with [host] or [host]:port. The []
-# form is required when you specify an IP address instead of
-# a hostname.
-#
-# A null transport and null nexthop result means "do not
-# change": use the delivery transport and nexthop informa-
-# tion that would be used when the entire transport table
-# did not exist.
-#
-# A non-null transport field with a null nexthop field
-# resets the nexthop information to the recipient domain.
-#
-# A null transport field with non-null nexthop field does
-# not modify the transport information.
-#
-# EXAMPLES
-# In order to deliver internal mail directly, while using a
-# mail relay for all other mail, specify a null entry for
-# internal destinations (do not change the delivery trans-
-# port or the nexthop information) and specify a wildcard
-# for all other destinations.
-#
-# my.domain :
-# .my.domain :
-# * smtp:outbound-relay.my.domain
-#
-# In order to send mail for example.com and its subdomains
-# via the uucp transport to the UUCP host named example:
-#
-# example.com uucp:example
-# .example.com uucp:example
-#
-# When no nexthop host name is specified, the destination
-# domain name is used instead. For example, the following
-# directs mail for user@example.com via the slow transport
-# to a mail exchanger for example.com. The slow transport
-# could be configured to run at most one delivery process at
-# a time:
-#
-# example.com slow:
-#
-# When no transport is specified, Postfix uses the transport
-# that matches the address domain class (see DESCRIPTION
-# above). The following sends all mail for example.com and
-# its subdomains to host gateway.example.com:
-#
-# example.com :[gateway.example.com]
-# .example.com :[gateway.example.com]
-#
-# In the above example, the [] suppress MX lookups. This
-# prevents mail routing loops when your machine is primary
-# MX host for example.com.
-#
-# In the case of delivery via SMTP, one may specify host-
-# name:service instead of just a host:
-#
-# example.com smtp:bar.example:2025
-#
-# This directs mail for user@example.com to host bar.example
-# port 2025. Instead of a numerical port a symbolic name may
-# be used. Specify [] around the hostname if MX lookups must
-# be disabled.
-#
-# The error mailer can be used to bounce mail:
-#
-# .example.com error:mail for *.example.com is not
-# deliverable
-#
-# This causes all mail for user@anything.example.com to be
-# bounced.
-#
-# REGULAR EXPRESSION TABLES
-# 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,
-# some.domain.hierarchy is not looked up via its parent
-# domains, nor is user+foo@domain looked up as user@domain.
-#
-# Patterns are applied in the order as specified in the
-# table, until a pattern is found that matches the search
-# string.
-#
-# 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.
-#
-# TCP-BASED TABLES
-# This section describes how the table lookups change when
-# lookups are directed to a TCP-based server. For a descrip-
-# tion of the TCP client/server lookup protocol, see
-# tcp_table(5). This feature is not available up to and
-# including Postfix version 2.2.
-#
-# Each lookup operation uses the entire recipient address
-# once. Thus, some.domain.hierarchy is not looked up via
-# its parent domains, nor is user+foo@domain looked up as
-# user@domain.
-#
-# Results are the same as with indexed file lookups.
-#
-# CONFIGURATION PARAMETERS
-# The following main.cf parameters are especially relevant.
-# The text below provides only a parameter summary. See
-# postconf(5) for more details including examples.
-#
-# empty_address_recipient
-# The address that is looked up instead of the null
-# sender address.
-#
-# parent_domain_matches_subdomains
-# List of Postfix features that use domain.tld pat-
-# terns to match sub.domain.tld (as opposed to
-# requiring .domain.tld patterns).
-#
-# transport_maps
-# List of transport lookup tables.
-#
-# SEE ALSO
-# trivial-rewrite(8), rewrite and resolve addresses
-# postconf(5), configuration parameters
-# postmap(1), Postfix lookup table manager
-#
-# README FILES
-# Use "postconf readme_directory" or "postconf html_direc-
-# tory" to locate this information.
-# DATABASE_README, Postfix lookup table overview
-# FILTER_README, external content filter
-#
-# LICENSE
-# The Secure Mailer license must be distributed with this
-# software.
-#
-# AUTHOR(S)
-# Wietse Venema
-# IBM T.J. Watson Research
-# P.O. Box 704
-# Yorktown Heights, NY 10598, USA
-#
-# TRANSPORT(5)
+++ /dev/null
-# VIRTUAL(5) VIRTUAL(5)
-#
-# NAME
-# virtual - Postfix virtual alias table format
-#
-# SYNOPSIS
-# postmap /etc/postfix/virtual
-#
-# postmap -q "string" /etc/postfix/virtual
-#
-# postmap -q - /etc/postfix/virtual <inputfile
-#
-# DESCRIPTION
-# The optional virtual(5) alias table rewrites recipient
-# addresses for all local, virtual and remote mail destina-
-# tions. This is unlike the aliases(5) table which is used
-# only for local(8) delivery. Virtual aliasing is recur-
-# sive, and is implemented by the Postfix cleanup(8) daemon
-# before mail is queued.
-#
-# The main applications of virtual aliasing are:
-#
-# o To redirect mail for one address to one or more
-# addresses.
-#
-# o To implement virtual alias domains where all
-# addresses are aliased to addresses in other
-# domains.
-#
-# Virtual alias domains are not to be confused with
-# the virtual mailbox domains that are implemented
-# with the Postfix virtual(8) mail delivery agent.
-# With virtual mailbox domains, each recipient
-# address can have its own mailbox.
-#
-# Virtual aliasing is applied only to recipient envelope
-# addresses, and does not affect message headers. Think
-# Sendmail rule set S0, if you like. Use canonical(5) map-
-# ping to rewrite header and envelope addresses in general.
-#
-# Normally, the virtual(5) alias 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/virtual" 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, or lookups can be directed to TCP-based server. In
-# that case, the lookups are done in a slightly different
-# way as described below under "REGULAR EXPRESSION TABLES"
-# and "TCP-BASED TABLES".
-#
-# TABLE FORMAT
-# 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
-# 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.
-#
-# TABLE SEARCH ORDER
-# 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:
-#
-# user@domain address, address, ...
-# Redirect mail for user@domain to address. This
-# form has the highest precedence.
-#
-# user address, address, ...
-# Redirect mail for user@site to address when site is
-# equal to $myorigin, when site is listed in $mydes-
-# tination, or when it is listed in $inet_interfaces
-# or $proxy_interfaces.
-#
-# This functionality overlaps with functionality of
-# the local aliases(5) database. The difference is
-# that virtual(5) mapping can be applied to non-local
-# addresses.
-#
-# @domain address, address, ...
-# Redirect mail for other users in domain to address.
-# This form has the lowest precedence.
-#
-# RESULT ADDRESS REWRITING
-# The lookup result is subject to address rewriting:
-#
-# o When the result has the form @otherdomain, the
-# result becomes the same user in otherdomain. This
-# works only for the first address in a multi-address
-# lookup result.
-#
-# o When "append_at_myorigin=yes", append "@$myorigin"
-# to addresses without "@domain".
-#
-# o When "append_dot_mydomain=yes", append ".$mydomain"
-# to addresses without ".domain".
-#
-# ADDRESS EXTENSION
-# 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.
-#
-# The propagate_unmatched_extensions parameter controls
-# whether an unmatched address extension (+foo) is propa-
-# gated to the result of table lookup.
-#
-# VIRTUAL ALIAS DOMAINS
-# Besides virtual aliases, the virtual alias table can also
-# be used to implement virtual alias domains. With a virtual
-# alias domain, all recipient addresses are aliased to
-# addresses in other domains.
-#
-# Virtual alias domains are not to be confused with the vir-
-# tual mailbox domains that are implemented with the Postfix
-# virtual(8) mail delivery agent. With virtual mailbox
-# domains, each recipient address can have its own mailbox.
-#
-# With a virtual alias domain, the virtual domain has its
-# own user name space. Local (i.e. non-virtual) usernames
-# are not visible in a virtual alias domain. In particular,
-# local aliases(5) and local mailing lists are not visible
-# as localname@virtual-alias.domain.
-#
-# Support for a virtual alias domain looks like:
-#
-# /etc/postfix/main.cf:
-# virtual_alias_maps = hash:/etc/postfix/virtual
-#
-# Note: some systems use dbm databases instead of hash.
-# See the output from "postconf -m" for available data-
-# base types.
-#
-# /etc/postfix/virtual:
-# virtual-alias.domain anything (right-hand content does not matter)
-# postmaster@virtual-alias.domain postmaster
-# user1@virtual-alias.domain address1
-# user2@virtual-alias.domain address2, address3
-#
-# The virtual-alias.domain anything entry is required for a
-# virtual alias domain. Without this entry, mail is rejected
-# with "relay access denied", or bounces with "mail loops
-# back to myself".
-#
-# Do not specify virtual alias domain names in the main.cf
-# mydestination or relay_domains configuration parameters.
-#
-# With a virtual alias domain, the Postfix SMTP server
-# accepts mail for known-user@virtual-alias.domain, and
-# rejects mail for unknown-user@virtual-alias.domain as
-# undeliverable.
-#
-# Instead of specifying the virtual alias domain name via
-# the virtual_alias_maps table, you may also specify it via
-# the main.cf virtual_alias_domains configuration parameter.
-# This latter parameter uses the same syntax as the main.cf
-# mydestination configuration parameter.
-#
-# REGULAR EXPRESSION TABLES
-# 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
-# foo.
-#
-# Patterns are applied in the order as specified in the ta-
-# ble, until a pattern is found that matches the search
-# string.
-#
-# 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.
-#
-# TCP-BASED TABLES
-# This section describes how the table lookups change when
-# lookups are directed to a TCP-based server. For a descrip-
-# tion of the TCP client/server lookup protocol, see tcp_ta-
-# ble(5). This feature is not available up to and including
-# Postfix version 2.2.
-#
-# Each lookup operation uses the entire address once. 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 foo.
-#
-# Results are the same as with indexed file lookups.
-#
-# BUGS
-# The table format does not understand quoting conventions.
-#
-# CONFIGURATION PARAMETERS
-# The following main.cf parameters are especially relevant
-# to this topic. See the Postfix main.cf file for syntax
-# details and for default values. Use the "postfix reload"
-# command after a configuration change.
-#
-# virtual_alias_maps
-# List of virtual aliasing tables.
-#
-# virtual_alias_domains
-# List of virtual alias domains. This uses the same
-# syntax as the mydestination parameter.
-#
-# propagate_unmatched_extensions
-# A list of address rewriting or forwarding mecha-
-# nisms that propagate an address extension from the
-# original address to the result. Specify zero or
-# more of canonical, virtual, alias, forward,
-# include, or generic.
-#
-# Other parameters of interest:
-#
-# inet_interfaces
-# The network interface addresses that this system
-# receives mail on. You need to stop and start Post-
-# fix when this parameter changes.
-#
-# mydestination
-# List of domains that this mail system considers
-# local.
-#
-# myorigin
-# The domain that is appended to any address that
-# does not have a domain.
-#
-# owner_request_special
-# Give special treatment to owner-xxx and xxx-request
-# addresses.
-#
-# proxy_interfaces
-# Other interfaces that this machine receives mail on
-# by way of a proxy agent or network address transla-
-# tor.
-#
-# SEE ALSO
-# cleanup(8), canonicalize and enqueue mail
-# postmap(1), Postfix lookup table manager
-# postconf(5), configuration parameters
-# canonical(5), canonical address mapping
-#
-# README FILES
-# Use "postconf readme_directory" or "postconf html_direc-
-# tory" to locate this information.
-# DATABASE_README, Postfix lookup table overview
-# ADDRESS_REWRITING_README, address rewriting guide
-# VIRTUAL_README, domain hosting guide
-#
-# LICENSE
-# The Secure Mailer license must be distributed with this
-# software.
-#
-# AUTHOR(S)
-# Wietse Venema
-# IBM T.J. Watson Research
-# P.O. Box 704
-# Yorktown Heights, NY 10598, USA
-#
-# VIRTUAL(5)
--- /dev/null
+usr/bin/idn
+#usr/include/idn-free.h
+#usr/include/idn-int.h
+#usr/include/idna.h
+#usr/include/pr29.h
+#usr/include/punycode.h
+#usr/include/stringprep.h
+#usr/include/tld.h
+#usr/lib/libidn.a
+#usr/lib/libidn.la
+usr/lib/libidn.so
+usr/lib/libidn.so.11
+usr/lib/libidn.so.11.5.28
+#usr/lib/pkgconfig/libidn.pc
+#usr/share/emacs
+#usr/share/emacs/site-lisp
+#usr/share/emacs/site-lisp/idna.el
+#usr/share/emacs/site-lisp/punycode.el
+#usr/share/info/libidn-components.png
+#usr/share/info/libidn.info
+#usr/share/man/man1/idn.1
+#usr/share/man/man3/idna_strerror.3
+#usr/share/man/man3/idna_to_ascii_4i.3
+#usr/share/man/man3/idna_to_ascii_4z.3
+#usr/share/man/man3/idna_to_ascii_8z.3
+#usr/share/man/man3/idna_to_ascii_lz.3
+#usr/share/man/man3/idna_to_unicode_44i.3
+#usr/share/man/man3/idna_to_unicode_4z4z.3
+#usr/share/man/man3/idna_to_unicode_8z4z.3
+#usr/share/man/man3/idna_to_unicode_8z8z.3
+#usr/share/man/man3/idna_to_unicode_8zlz.3
+#usr/share/man/man3/idna_to_unicode_lzlz.3
+#usr/share/man/man3/pr29_4.3
+#usr/share/man/man3/pr29_4z.3
+#usr/share/man/man3/pr29_8z.3
+#usr/share/man/man3/pr29_strerror.3
+#usr/share/man/man3/punycode_decode.3
+#usr/share/man/man3/punycode_encode.3
+#usr/share/man/man3/punycode_strerror.3
+#usr/share/man/man3/stringprep.3
+#usr/share/man/man3/stringprep_4i.3
+#usr/share/man/man3/stringprep_4zi.3
+#usr/share/man/man3/stringprep_check_version.3
+#usr/share/man/man3/stringprep_convert.3
+#usr/share/man/man3/stringprep_locale_charset.3
+#usr/share/man/man3/stringprep_locale_to_utf8.3
+#usr/share/man/man3/stringprep_profile.3
+#usr/share/man/man3/stringprep_strerror.3
+#usr/share/man/man3/stringprep_ucs4_nfkc_normalize.3
+#usr/share/man/man3/stringprep_ucs4_to_utf8.3
+#usr/share/man/man3/stringprep_unichar_to_utf8.3
+#usr/share/man/man3/stringprep_utf8_nfkc_normalize.3
+#usr/share/man/man3/stringprep_utf8_to_locale.3
+#usr/share/man/man3/stringprep_utf8_to_ucs4.3
+#usr/share/man/man3/stringprep_utf8_to_unichar.3
+#usr/share/man/man3/tld_check_4.3
+#usr/share/man/man3/tld_check_4t.3
+#usr/share/man/man3/tld_check_4tz.3
+#usr/share/man/man3/tld_check_4z.3
+#usr/share/man/man3/tld_check_8z.3
+#usr/share/man/man3/tld_check_lz.3
+#usr/share/man/man3/tld_default_table.3
+#usr/share/man/man3/tld_get_4.3
+#usr/share/man/man3/tld_get_4z.3
+#usr/share/man/man3/tld_get_table.3
+#usr/share/man/man3/tld_get_z.3
+#usr/share/man/man3/tld_strerror.3
#etc/postfix
#etc/postfix/LICENSE
#etc/postfix/TLS_LICENSE
-etc/postfix/access
#etc/postfix/bounce.cf.default
-etc/postfix/canonical
-etc/postfix/generic
etc/postfix/header_checks
etc/postfix/main.cf
#etc/postfix/makedefs.out
etc/postfix/post-install
etc/postfix/postfix-files
etc/postfix/postfix-script
-etc/postfix/relocated
-etc/postfix/transport
-etc/postfix/virtual
etc/rc.d/init.d/postfix
usr/bin/mailq
usr/bin/newaliases
-== List of softwares used to build IPFire Version: 2.0beta2 ==
+== List of softwares used to build IPFire Version: 2.0rc1t ==
* Archive-Tar-1.29
* Archive-Zip-1.16
* BerkeleyDB-0.27
cd $(DIR_APP) && make
cd $(DIR_APP) && make install
cd $(DIR_APP) && ln -v -sf /usr/bin/smbspool /usr/lib/cups/backend/smb
+ install -v -m 754 $(DIR_SRC)/src/initscripts/init.d/cups /etc/rc.d/init.d
@rm -rf $(DIR_APP)
@$(POSTBUILD)
--- /dev/null
+###############################################################################
+# #
+# IPFire.org - A linux based firewall #
+# Copyright (C) 2007 Michael Tremer & Christian Schmidt #
+# #
+# This program is free software: you can redistribute it and/or modify #
+# it under the terms of the GNU General Public License as published by #
+# the Free Software Foundation, either version 3 of the License, or #
+# (at your option) any later version. #
+# #
+# This program is distributed in the hope that it will be useful, #
+# but WITHOUT ANY WARRANTY; without even the implied warranty of #
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the #
+# GNU General Public License for more details. #
+# #
+# You should have received a copy of the GNU General Public License #
+# along with this program. If not, see <http://www.gnu.org/licenses/>. #
+# #
+###############################################################################
+
+###############################################################################
+# Definitions
+###############################################################################
+
+include Config
+
+VER = 0.6.14
+
+THISAPP = libidn-$(VER)
+DL_FILE = $(THISAPP).tar.gz
+DL_FROM = $(URL_IPFIRE)
+DIR_APP = $(DIR_SRC)/$(THISAPP)
+TARGET = $(DIR_INFO)/$(THISAPP)
+
+###############################################################################
+# Top-level Rules
+###############################################################################
+
+objects = $(DL_FILE)
+
+$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
+
+$(DL_FILE)_MD5 = 040f012a45feb56168853998bb87ad4d
+
+install : $(TARGET)
+
+check : $(patsubst %,$(DIR_CHK)/%,$(objects))
+
+download :$(patsubst %,$(DIR_DL)/%,$(objects))
+
+md5 : $(subst %,%_MD5,$(objects))
+
+###############################################################################
+# Downloading, checking, md5sum
+###############################################################################
+
+$(patsubst %,$(DIR_CHK)/%,$(objects)) :
+ @$(CHECK)
+
+$(patsubst %,$(DIR_DL)/%,$(objects)) :
+ @$(LOAD)
+
+$(subst %,%_MD5,$(objects)) :
+ @$(MD5)
+
+###############################################################################
+# Installation Details
+###############################################################################
+
+$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
+ @$(PREBUILD)
+ @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
+ cd $(DIR_APP) && ./configure --prefix=/usr --disable-nls
+ cd $(DIR_APP) && make $(MAKETUNING)
+ cd $(DIR_APP) && make install
+ @rm -rf $(DIR_APP)
+ @$(POSTBUILD)
cd $(DIR_APP) && make testdir=/tmp/mysql install
rm -rf /tmp/mysql
cd /usr/lib && ln -v -sf mysql/libmysqlclient{,_r}.so* .
- install -v -m644 /usr/share/mysql/my-medium.cnf /etc/my.cnf
+ install -v -m644 $(DIR_SRC)/config/mysql/my.cnf /etc/my.cnf
mkdir -p /srv/mysql
mysql_install_db --user=mysql --force
chgrp -v mysql /srv/mysql{,/test,/mysql}
# Top-level Rules
###############################################################################
-objects = $(DL_FILE)
+objects = $(DL_FILE) \
+ adodb502.tgz
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
+adodb502.tgz = $(DL_FROM)/adodb502.tgz
$(DL_FILE)_MD5 = c56bc9c41f9dd25da9dbf1b63a470333
+adodb502.tgz_MD5 = 850fe353400df5af006985a88620936d
install : $(TARGET)
/srv/web/openmailadmin/inc
cp -fv $(DIR_SRC)/config/openmailadmin/mail.dump \
/srv/web/openmailadmin/
+ tar xfz $(DIR_DL)/adodb502.tgz -C /srv/web/openmailadmin
+ ln -svf adodb5 /srv/web/openmailadmin/adodb
chown nobody.nobody /srv/web/openmailadmin/ -Rv
@$(POSTBUILD)
# Top-level Rules
###############################################################################
-objects = $(DL_FILE)
+objects = $(DL_FILE) idn-0.1.tgz
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
+idn-0.1.tgz = $(DL_FROM)/idn-0.1.tgz
$(DL_FILE)_MD5 = 55c97a671fdabf462cc7a82971a656d2
+idn-0.1.tgz_MD5 = ef8635ec22348325a76abd2abddca4a1
install : $(TARGET)
$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
- @rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar jxf $(DIR_DL)/$(DL_FILE)
+ @rm -rf $(DIR_APP) $(DIR_SRC)/idn-* $(DIR_SRC)/package.xml && \
+ cd $(DIR_SRC) && tar jxf $(DIR_DL)/$(DL_FILE)
cd $(DIR_APP) && sed -i 's/const char \*errpfx,/const DB_ENV *dbenv, & const/' ext/dba/dba_db4.c
cd $(DIR_APP) && ./configure --prefix=/usr \
--sysconfdir=/etc \
cd $(DIR_APP) && make $(MAKETUNING)
cd $(DIR_APP) && make install
cd $(DIR_APP) && install -v -m644 php.ini-recommended /etc/php.ini
- grep -v libphp5.so < /etc/httpd/conf/httpd.conf > /etc/httpd/conf/httpd.conf.bak
+ -grep -v libphp5.so < /etc/httpd/conf/httpd.conf > /etc/httpd/conf/httpd.conf.bak
mv -f /etc/httpd/conf/httpd.conf.bak /etc/httpd/conf/httpd.conf
- @rm -rf $(DIR_APP)
+ cd $(DIR_SRC) && tar xfz $(DIR_DL)/idn-0.1.tgz
+ -rm -f $(DIR_SRC)/package.xml
+ cd $(DIR_SRC)/idn-* && phpize
+ cd $(DIR_SRC)/idn-* && ./configure --prefix=/usr --with-idn
+ cd $(DIR_SRC)/idn-* && make
+ cd $(DIR_SRC)/idn-* && make install
+ @rm -rf $(DIR_APP) $(DIR_SRC)/idn-* $(DIR_SRC)/package.xml
@$(POSTBUILD)
ipfiremake curl
ipfiremake python
ipfiremake libnet
+ ipfiremake libidn
ipfiremake libjpeg
ipfiremake libpng
ipfiremake libtiff
eval $(/usr/local/bin/readhash /var/ipfire/ppp/settings)
- boot_mesg "Bringing up the PPPoE interface on ${DEVICE}..."
- ip addr add 1.1.1.1/24 broadcast 1.1.1.255 dev ${DEVICE}
-
[ -c "/dev/ppp" ] || mknod /dev/ppp c 108 0
+ if [ "$TYPE" == "pppoe" ]; then
+ boot_mesg "Bringing up the PPPoE interface on ${DEVICE}..."
+ ip addr add 1.1.1.1/24 broadcast 1.1.1.255 dev ${DEVICE}
+ else
+ boot_mesg "Bringing up the PPP via ${TYPE} on ${COMPORT}..."
+ fi
+
### ###
### Configuring the pppd ###
### ###
fi
fi
- ### When using plugin the device has to be the last option
+ ### When using pppoe-plugin the device has to be the last option
#
[ "${METHOD}" == "PPPOE_PLUGIN" ] && PLUGOPTS+=" ${DEVICE}"
+
+ if [ "$TYPE" == "modem" ]; then
+ PLUGOPTS=" /dev/${COMPORT} ${DTERATE} connect /etc/ppp/dialer"
+ elif [ "$TYPE" == "serial" ]; then
+ PLUGOPTS=" /dev/${COMPORT} ${DTERATE} connect /bin/true"
+ fi
### Standard PPP options we always use
#
PPP_STD_OPTIONS+=" mru ${MTU} noaccomp nodeflate nopcomp novj novjccomp"
PPP_STD_OPTIONS+=" nobsdcomp user ${USERNAME} lcp-echo-interval 20"
PPP_STD_OPTIONS+=" lcp-echo-failure 3 ${AUTH}"
+ [ "${TYPE}" eq "pppoe" ] || PPP_STD_OPTIONS+=" lock modem crtscts user ${USERNAME}"
### Debugging
#
### PPPoE invocation
#
- PPPOE_CMD="/usr/sbin/pppoe -p /var/run/ppp-ipfire.pid.pppoe -I ${DEVICE}"
- PPPOE_CMD+=" -T 80 -U $PPPOE_SYNC $ACNAME $SERVICENAMEOPT"
+ if [ "${TYPE}" == "pppoe" ]; then
+ PPPOE_CMD="/usr/sbin/pppoe -p /var/run/ppp-ipfire.pid.pppoe -I ${DEVICE}"
+ PPPOE_CMD+=" -T 80 -U $PPPOE_SYNC $ACNAME $SERVICENAMEOPT"
+ fi
### Run everything
#
--- /dev/null
+#!/bin/bash
+. /opt/pakfire/lib/functions.sh
+
+extract_files
--- /dev/null
+#!/bin/bash
+. /opt/pakfire/lib/functions.sh
+
+extract_files
extract_files
+postalias /etc/aliases
+
# Set postfix's hostname
postconf -e "myhostname=$(hostname -f)"