<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006>Hallo
zusammen</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=625221108-28092006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006>Ich lage mich immer
noch mit dem Postfix herum, hab von einiger Zeit von Sendmail auf Postfix
umgestellt. Da ich immer wieder gelesen habe das Postfix einfacher sei zu
konfigurieren. Aber irgenwie hatte ich mit Sendmail keine problem bei der
konfiguration</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=625221108-28092006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006>Mein problem ist
folgendes:</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=625221108-28092006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006>Sobale eine Email
local versendet wird, Spich über webmail oder von von Webmin aus wird die
angegebene Absender Adresse nicht genommen. Absender ist dann immer <A
href="mailto:Benutzer@hauptdomain">Benutzer@hauptdomain</A> </SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=625221108-28092006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006>Ich füge mal meine
main.cf an </SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=625221108-28092006></SPAN></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006> Global Postfix
configuration file. This file lists only a subset<BR># of all 300+ parameters.
See the postconf(5) manual page for a<BR># complete list.<BR>#<BR># The general
format of each line is: parameter = value. Lines<BR># that begin with whitespace
continue the previous line. A value can<BR># contain references to other $names
or ${name}s.<BR>#<BR># NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND
TEST IF<BR># POSTFIX STILL WORKS AFTER EVERY CHANGE.</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># SOFT
BOUNCE<BR>#<BR># The soft_bounce parameter provides a limited safety net
for<BR># testing. When soft_bounce is enabled, mail will remain queued
that<BR># would otherwise bounce. This parameter disables locally-generated<BR>#
bounces, and prevents the SMTP server from rejecting mail permanently<BR># (by
changing 5xx replies into 4xx replies). However, soft_bounce<BR># is no cure for
address rewriting mistakes or mail routing mistakes.<BR>#<BR>#soft_bounce =
no</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># LOCAL PATHNAME
INFORMATION<BR>#<BR># The queue_directory specifies the location of the Postfix
queue.<BR># This is also the root directory of Postfix daemons that run
chrooted.<BR># See the files in examples/chroot-setup for setting up Postfix
chroot<BR># environments on different UNIX systems.<BR>#</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># The
command_directory parameter specifies the location of all<BR># postXXX
commands.<BR>#<BR>command_directory = /usr/sbin</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># The
daemon_directory parameter specifies the location of all Postfix<BR># daemon
programs (i.e. programs listed in the master.cf file). This<BR># directory must
be owned by root.<BR>#<BR>daemon_directory =
/usr/libexec/postfix</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># QUEUE AND PROCESS
OWNERSHIP<BR>#<BR># The mail_owner parameter specifies the owner of the Postfix
queue<BR># and of most Postfix daemon processes. Specify the name of a
user<BR># account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER
ACCOUNTS<BR># AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.
In<BR># particular, don't specify nobody or daemon. PLEASE USE A DEDICATED<BR>#
USER.<BR>#</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># The default_privs
parameter specifies the default rights used by<BR># the local delivery agent for
delivery to external file or command.<BR># These rights are used in the absence
of a recipient user context.<BR># DO NOT SPECIFY A PRIVILEGED USER OR THE
POSTFIX OWNER.<BR>#<BR>#default_privs = nobody</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># INTERNET HOST AND
DOMAIN NAMES<BR># <BR># The myhostname parameter specifies the internet hostname
of this<BR># mail system. The default is to use the fully-qualified domain
name<BR># from gethostname(). $myhostname is used as a default value for
many<BR># other configuration parameters.<BR>#<BR>#myhostname =
host.domain.tld<BR>#myhostname = virtual.domain.tld</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># The mydomain
parameter specifies the local internet domain name.<BR># The default is to use
$myhostname minus the first component.<BR># $mydomain is used as a default value
for many other configuration<BR># parameters.<BR>#<BR>#mydomain =
domain.tld</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># SENDING MAIL<BR>#
<BR># The myorigin parameter specifies the domain that locally-posted<BR># mail
appears to come from. The default is to append $myhostname,<BR># which is fine
for small sites. If you run a domain with multiple<BR># machines, you
should (1) change this to $mydomain and (2) set up<BR># a domain-wide alias
database that aliases each user to<BR># <A
href="mailto:user@that.users.mailhost">user@that.users.mailhost</A>.<BR>#<BR>#
For the sake of consistency between sender and recipient addresses,<BR>#
myorigin also specifies the default domain name that is appended<BR># to
recipient addresses that have no @domain part.<BR>#<BR>#myorigin =
$myhostname<BR>#myorigin = $mydomain</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># RECEIVING
MAIL</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># The
inet_interfaces parameter specifies the network interface<BR># addresses that
this mail system receives mail on. By default,<BR># the software claims
all active interfaces on the machine. The<BR># parameter also controls delivery
of mail to <A href="mailto:user@[ip.address">user@[ip.address</A>].<BR>#<BR>#
See also the proxy_interfaces parameter, for network addresses that<BR># are
forwarded to us via a proxy or network address translator.<BR>#<BR># Note: you
need to stop/start Postfix when this parameter changes.<BR>#<BR>#inet_interfaces
= $myhostname<BR>#inet_interfaces = $myhostname, localhost</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># The
proxy_interfaces parameter specifies the network interface<BR># addresses that
this mail system receives mail on by way of a<BR># proxy or network address
translation unit. This setting extends<BR># the address list specified with the
inet_interfaces parameter.<BR>#<BR># You must specify your proxy/NAT addresses
when your system is a<BR># backup MX host for other domains, otherwise mail
delivery loops<BR># will happen when the primary MX host is
down.<BR>#<BR>#proxy_interfaces =<BR>#proxy_interfaces =
1.2.3.4</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># The mydestination
parameter specifies the list of domains that this<BR># machine considers itself
the final destination for.<BR>#<BR># These domains are routed to the delivery
agent specified with the<BR># local_transport parameter setting. By default,
that is the UNIX<BR># compatible delivery agent that lookups all recipients in
/etc/passwd<BR># and /etc/aliases or their equivalent.<BR>#<BR># The default is
$myhostname + localhost.$mydomain. On a mail domain<BR># gateway, you
should also include $mydomain.<BR>#<BR># Do not specify the names of virtual
domains - those domains are<BR># specified elsewhere (see
VIRTUAL_README).<BR>#<BR># Do not specify the names of domains that this machine
is backup MX<BR># host for. Specify those names via the relay_domains settings
for<BR># the SMTP server, or use permit_mx_backup if you are lazy (see<BR>#
STANDARD_CONFIGURATION_README).<BR>#<BR># The local machine is always the final
destination for mail addressed<BR># to <A
href="mailto:user@[the.net.work.address">user@[the.net.work.address</A>] of an
interface that the mail system<BR># receives mail on (see the inet_interfaces
parameter).<BR>#<BR># Specify a list of host or domain names, /file/name or
type:table<BR># patterns, separated by commas and/or whitespace. A
/file/name<BR># pattern is replaced by its contents; a type:table is matched
when<BR># a name matches a lookup key (the right-hand side is ignored).<BR>#
Continue long lines by starting the next line with whitespace.<BR>#<BR># See
also below, section "REJECTING MAIL FOR UNKNOWN LOCAL
USERS".<BR>#<BR>#mydestination = $myhostname, localhost.$mydomain, localhost,
$mydomain<BR>#mydestination = $myhostname, localhost.$mydomain, localhost,
$mydomain,<BR># mail.$mydomain, <A
href="http://www.$mydomain/">www.$mydomain</A>, <A
href="ftp://ftp.$mydomain/">ftp.$mydomain</A></SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006>mydestination =
$mydomain $myhostname <A
href="http://www.$mydomain/">www.$mydomain</A>
christm.ch partybedarf.ch hvbeinwil.ch
erotic-dreams.ch braun-kamin.ch pbraun.ch
naturregion.ch fahrschule-m-brenne.ch
tomthomson.ch illusion-event.ch quazzle.ch
mc-web.ch herrliag.ch pbhosting.ch
rachegeschenke.ch</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># REJECTING MAIL FOR
UNKNOWN LOCAL USERS<BR>#<BR># The local_recipient_maps parameter specifies
optional lookup tables<BR># with all names or addresses of users that are local
with respect<BR># to $mydestination, $inet_interfaces or
$proxy_interfaces.<BR>#<BR># If this parameter is defined, then the SMTP server
will reject<BR># mail for unknown local users. This parameter is defined by
default.<BR>#<BR># To turn off local recipient checking in the SMTP server,
specify<BR># local_recipient_maps = (i.e. empty).<BR>#<BR># The default setting
assumes that you use the default Postfix local<BR># delivery agent for local
delivery. You need to update the<BR># local_recipient_maps setting if:<BR>#<BR>#
- You define $mydestination domain recipients in files other
than<BR># /etc/passwd, /etc/aliases, or the $virtual_alias_maps
files.<BR># For example, you define $mydestination domain recipients
in <BR># the $virtual_mailbox_maps
files.<BR>#<BR># - You redefine the local delivery agent in master.cf.<BR>#<BR>#
- You redefine the "local_transport" setting in main.cf.<BR>#<BR># - You use the
"luser_relay", "mailbox_transport", or "fallback_transport"<BR>#
feature of the Postfix local delivery agent (see local(8)).<BR>#<BR># Details
are described in the LOCAL_RECIPIENT_README file.<BR>#<BR># Beware: if the
Postfix SMTP server runs chrooted, you probably have<BR># to access the passwd
file via the proxymap service, in order to<BR># overcome chroot restrictions.
The alternative, having a copy of<BR># the system passwd file in the chroot jail
is just not practical.<BR>#<BR># The right-hand side of the lookup tables is
conveniently ignored.<BR># In the left-hand side, specify a bare username, an
@domain.tld<BR># wild-card, or specify a <A
href="mailto:user@domain.tld">user@domain.tld</A> address.<BR>#
<BR>#local_recipient_maps = unix:passwd.byname
$alias_maps<BR>#local_recipient_maps = proxy:unix:passwd.byname
$alias_maps<BR>#local_recipient_maps =</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># The
unknown_local_recipient_reject_code specifies the SMTP server<BR># response code
when a recipient domain matches $mydestination or<BR># ${proxy,inet}_interfaces,
while $local_recipient_maps is non-empty<BR># and the recipient address or
address local-part is not found.<BR>#<BR># The default setting is 550 (reject
mail) but it is safer to start<BR># with 450 (try again later) until you are
certain that your<BR># local_recipient_maps settings are
OK.<BR>#<BR>unknown_local_recipient_reject_code = 550</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># TRUST AND RELAY
CONTROL</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># The mynetworks
parameter specifies the list of "trusted" SMTP<BR># clients that have more
privileges than "strangers".<BR>#<BR># In particular, "trusted" SMTP clients are
allowed to relay mail<BR># through Postfix. See the
smtpd_recipient_restrictions parameter<BR># in postconf(5).<BR>#<BR># You can
specify the list of "trusted" network addresses by hand<BR># or you can let
Postfix do it for you (which is the default).<BR>#<BR># By default
(mynetworks_style = subnet), Postfix "trusts" SMTP<BR># clients in the same IP
subnetworks as the local machine.<BR># On Linux, this does works correctly only
with interfaces specified<BR># with the "ifconfig" command.<BR># <BR># Specify
"mynetworks_style = class" when Postfix should "trust" SMTP<BR># clients in the
same IP class A/B/C networks as the local machine.<BR># Don't do this with a
dialup site - it would cause Postfix to "trust"<BR># your entire provider's
network. Instead, specify an explicit<BR># mynetworks list by hand, as
described below.<BR># <BR># Specify "mynetworks_style = host" when Postfix
should "trust"<BR># only the local machine.<BR># <BR>#mynetworks_style =
class<BR>#mynetworks_style = subnet<BR>#mynetworks_style =
host</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2><SPAN class=625221108-28092006># Alternatively, you
can specify the mynetworks list by hand, in<BR># which case Postfix ignores the
mynetworks_style setting.<BR>#<BR># Specify an explicit list of network/netmask
patterns, where the<BR># mask specifies the number of bits in the network part
of a host<BR># address.<BR>#<BR># You can also specify the absolute pathname of
a pattern file instead<BR># of listing the patterns here. Specify type:table for
table-based lookups<BR># (the value on the table right-hand side is not
used).<BR>#<BR>#mynetworks = $config_directory/mynetworks<BR>#mynetworks =
hash:/etc/postfix/network_table<BR>mynetworks = 213.200.248.99,127.0.0.1,
hash:/etc/postfix/access<BR>#smtpd_client_restrictions = check_client_access
hash:/etc/postfix/access</SPAN></FONT></DIV>
<DIV> </DIV><FONT face=Arial size=2><SPAN class=625221108-28092006>
<DIV><BR>#smtpd_sender_restrictions = check_sender_access
hash:/etc/postfix/access</DIV>
<DIV> </DIV>
<DIV><BR># The relay_domains parameter restricts what destinations this system
will<BR># relay mail to. See the smtpd_recipient_restrictions description
in<BR># postconf(5) for detailed information.<BR>#<BR># By default, Postfix
relays mail<BR># - from "trusted" clients (IP address matches $mynetworks) to
any destination,<BR># - from "untrusted" clients to destinations that match
$relay_domains or<BR># subdomains thereof, except addresses with
sender-specified routing.<BR># The default relay_domains value is
$mydestination.<BR># <BR># In addition to the above, the Postfix SMTP server by
default accepts mail<BR># that Postfix is final destination for:<BR># -
destinations that match $inet_interfaces or $proxy_interfaces,<BR># -
destinations that match $mydestination<BR># - destinations that match
$virtual_alias_domains,<BR># - destinations that match
$virtual_mailbox_domains.<BR># These destinations do not need to be listed in
$relay_domains.<BR># <BR># Specify a list of hosts or domains, /file/name
patterns or type:name<BR># lookup tables, separated by commas and/or
whitespace. Continue<BR># long lines by starting the next line with
whitespace. A file name<BR># is replaced by its contents; a type:name table is
matched when a<BR># (parent) domain appears as lookup key.<BR>#<BR># NOTE:
Postfix will not automatically forward mail for domains that<BR># list this
system as their primary or backup MX host. See the<BR># permit_mx_backup
restriction description in postconf(5).<BR>#<BR>#relay_domains =
$mydestination</DIV>
<DIV> </DIV>
<DIV># INTERNET OR INTRANET</DIV>
<DIV> </DIV>
<DIV># The relayhost parameter specifies the default host to send mail to<BR>#
when no entry is matched in the optional transport(5) table. When<BR># no
relayhost is given, mail is routed directly to the destination.<BR>#<BR># On an
intranet, specify the organizational domain name. If your<BR># internal DNS uses
no MX records, specify the name of the intranet<BR># gateway host
instead.<BR>#<BR># In the case of SMTP, specify a domain, host, host:port,
[host]:port,<BR># [address] or [address]:port; the form [host] turns off MX
lookups.<BR>#<BR># If you're connected via UUCP, see also the default_transport
parameter.<BR>#<BR>relayhost = smtp.cybernet.ch<BR>#relayhost =
[gateway.my.domain]<BR>#relayhost = [mailserver.isp.tld]<BR>#relayhost =
uucphost<BR>#relayhost = [an.ip.add.ress]</DIV>
<DIV> </DIV>
<DIV># REJECTING UNKNOWN RELAY USERS<BR>#<BR># The relay_recipient_maps
parameter specifies optional lookup tables<BR># with all addresses in the
domains that match $relay_domains.<BR>#<BR># If this parameter is defined, then
the SMTP server will reject<BR># mail for unknown relay users. This feature is
off by default.<BR>#<BR># The right-hand side of the lookup tables is
conveniently ignored.<BR># In the left-hand side, specify an @domain.tld
wild-card, or specify<BR># a <A
href="mailto:user@domain.tld">user@domain.tld</A> address.<BR>#
<BR>#relay_recipient_maps = hash:/etc/postfix/relay_recipients</DIV>
<DIV> </DIV>
<DIV># INPUT RATE CONTROL<BR>#<BR># The in_flow_delay configuration parameter
implements mail input<BR># flow control. This feature is turned on by default,
although it<BR># still needs further development (it's disabled on SCO UNIX
due<BR># to an SCO bug).<BR># <BR># A Postfix process will pause for
$in_flow_delay seconds before<BR># accepting a new message, when the message
arrival rate exceeds the<BR># message delivery rate. With the default 100 SMTP
server process<BR># limit, this limits the mail inflow to 100 messages a second
more<BR># than the number of messages delivered per second.<BR># <BR># Specify 0
to disable the feature. Valid delays are 0..10.<BR># <BR>#in_flow_delay =
1s</DIV>
<DIV> </DIV>
<DIV># ADDRESS REWRITING<BR>#<BR># The ADDRESS_REWRITING_README document gives
information about<BR># address masquerading or other forms of address rewriting
including<BR># username->Firstname.Lastname mapping.</DIV>
<DIV> </DIV>
<DIV># ADDRESS REDIRECTION (VIRTUAL DOMAIN)<BR>#<BR># The VIRTUAL_README
document gives information about the many forms<BR># of domain hosting that
Postfix supports.</DIV>
<DIV> </DIV>
<DIV># "USER HAS MOVED" BOUNCE MESSAGES<BR>#<BR># See the discussion in the
ADDRESS_REWRITING_README document.</DIV>
<DIV> </DIV>
<DIV># TRANSPORT MAP<BR>#<BR># See the discussion in the
ADDRESS_REWRITING_README document.</DIV>
<DIV> </DIV>
<DIV># ALIAS DATABASE<BR>#<BR># The alias_maps parameter specifies the list of
alias databases used<BR># by the local delivery agent. The default list is
system dependent.<BR>#<BR># On systems with NIS, the default is to search the
local alias<BR># database, then the NIS alias database. See aliases(5) for
syntax<BR># details.<BR># <BR># If you change the alias database, run "postalias
/etc/aliases" (or<BR># wherever your system stores the mail alias file), or
simply run<BR># "newaliases" to build the necessary DBM or DB file.<BR>#<BR># It
will take a minute or so before changes become visible. Use<BR># "postfix
reload" to eliminate the delay.<BR>#<BR>#alias_maps =
dbm:/etc/aliases<BR>alias_maps = hash:/etc/aliases<BR>#alias_maps =
hash:/etc/aliases, nis:mail.aliases<BR>#alias_maps = netinfo:/aliases</DIV>
<DIV> </DIV>
<DIV># The alias_database parameter specifies the alias database(s) that<BR>#
are built with "newaliases" or "sendmail -bi". This is a separate<BR>#
configuration parameter, because alias_maps (see above) may specify<BR># tables
that are not necessarily all under control by Postfix.<BR>#<BR>#alias_database =
dbm:/etc/aliases<BR>#alias_database = dbm:/etc/mail/aliases<BR>alias_database =
hash:/etc/aliases<BR>#alias_database = hash:/etc/aliases,
hash:/opt/majordomo/aliases</DIV>
<DIV> </DIV>
<DIV># ADDRESS EXTENSIONS (e.g., user+foo)<BR>#<BR># The recipient_delimiter
parameter specifies the separator between<BR># user names and address extensions
(user+foo). See canonical(5),<BR># local(8), relocated(5) and virtual(5) for the
effects this has on<BR># aliases, canonical, virtual, relocated and .forward
file lookups.<BR># Basically, the software tries user+foo and .forward+foo
before<BR># trying user and .forward.<BR>#<BR>#recipient_delimiter = +</DIV>
<DIV> </DIV>
<DIV># DELIVERY TO MAILBOX<BR>#<BR># The home_mailbox parameter specifies the
optional pathname of a<BR># mailbox file relative to a user's home directory.
The default<BR># mailbox file is /var/spool/mail/user or /var/mail/user.
Specify<BR># "Maildir/" for qmail-style delivery (the / is
required).<BR>#<BR>#home_mailbox = Mailbox<BR>#home_mailbox =
Maildir/<BR> <BR># The mail_spool_directory parameter specifies the
directory where<BR># UNIX-style mailboxes are kept. The default setting depends
on the<BR># system type.<BR>#<BR>#mail_spool_directory =
/var/mail<BR>#mail_spool_directory = /var/spool/mail</DIV>
<DIV> </DIV>
<DIV># The mailbox_command parameter specifies the optional external<BR>#
command to use instead of mailbox delivery. The command is run as<BR># the
recipient with proper HOME, SHELL and LOGNAME environment settings.<BR>#
Exception: delivery for root is done as $default_user.<BR>#<BR># Other
environment variables of interest: USER (recipient username),<BR># EXTENSION
(address extension), DOMAIN (domain part of address),<BR># and LOCAL (the
address localpart).<BR>#<BR># Unlike other Postfix configuration parameters, the
mailbox_command<BR># parameter is not subjected to $parameter substitutions.
This is to<BR># make it easier to specify shell syntax (see example
below).<BR>#<BR># Avoid shell meta characters because they will force Postfix to
run<BR># an expensive shell process. Procmail alone is expensive
enough.<BR>#<BR># IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP
AN<BR># ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL
USER.<BR>#<BR>#mailbox_command = /some/where/procmail<BR>#mailbox_command =
/some/where/procmail -a "$EXTENSION"</DIV>
<DIV> </DIV>
<DIV># The mailbox_transport specifies the optional transport in master.cf<BR>#
to use after processing aliases and .forward files. This parameter<BR># has
precedence over the mailbox_command, fallback_transport and<BR># luser_relay
parameters.<BR>#<BR># Specify a string of the form transport:nexthop, where
transport is<BR># the name of a mail delivery transport defined in
master.cf. The<BR># :nexthop part is optional. For more details see the
sample transport<BR># configuration file.<BR>#<BR># NOTE: if you use this
feature for accounts not in the UNIX password<BR># file, then you must update
the "local_recipient_maps" setting in<BR># the main.cf file, otherwise the SMTP
server will reject mail for <BR># non-UNIX accounts with "User
unknown in local recipient table".<BR>#<BR>#mailbox_transport =
lmtp:unix:/file/name<BR>#mailbox_transport = cyrus</DIV>
<DIV> </DIV>
<DIV># The fallback_transport specifies the optional transport in master.cf<BR>#
to use for recipients that are not found in the UNIX passwd database.<BR># This
parameter has precedence over the luser_relay parameter.<BR>#<BR># Specify a
string of the form transport:nexthop, where transport is<BR># the name of a mail
delivery transport defined in master.cf. The<BR># :nexthop part is
optional. For more details see the sample transport<BR># configuration
file.<BR>#<BR># NOTE: if you use this feature for accounts not in the UNIX
password<BR># file, then you must update the "local_recipient_maps" setting
in<BR># the main.cf file, otherwise the SMTP server will reject mail
for <BR># non-UNIX accounts with "User unknown in local
recipient table".<BR>#<BR>#fallback_transport =
lmtp:unix:/file/name<BR>#fallback_transport = cyrus<BR>#fallback_transport
=</DIV>
<DIV> </DIV>
<DIV># The luser_relay parameter specifies an optional destination address<BR>#
for unknown recipients. By default, mail for <A
href="mailto:unknown@$mydestination">unknown@$mydestination</A>,<BR># <A
href="mailto:unknown@[$inet_interfaces">unknown@[$inet_interfaces</A>] or <A
href="mailto:unknown@[$proxy_interfaces">unknown@[$proxy_interfaces</A>] is
returned<BR># as undeliverable.<BR>#<BR># The following expansions are done on
luser_relay: $user (recipient<BR># username), $shell (recipient shell), $home
(recipient home directory),<BR># $recipient (full recipient address), $extension
(recipient address<BR># extension), $domain (recipient domain), $local (entire
recipient<BR># localpart), $recipient_delimiter. Specify ${name?value} or<BR>#
${name:value} to expand value only when $name does (does not) exist.<BR>#<BR>#
luser_relay works only for the default Postfix local delivery agent.<BR>#<BR>#
NOTE: if you use this feature for accounts not in the UNIX password<BR># file,
then you must specify "local_recipient_maps =" (i.e. empty) in<BR># the main.cf
file, otherwise the SMTP server will reject mail for <BR>#
non-UNIX accounts with "User unknown in local recipient
table".<BR>#<BR>#luser_relay = <A
href="mailto:$user@other.host">$user@other.host</A><BR>#luser_relay = <A
href="mailto:$local@other.host">$local@other.host</A><BR>#luser_relay =
admin+$local<BR> <BR># JUNK MAIL CONTROLS<BR># <BR># The controls listed
here are only a very small subset. The file<BR># SMTPD_ACCESS_README provides an
overview.</DIV>
<DIV> </DIV>
<DIV># The header_checks parameter specifies an optional table with
patterns<BR># that each logical message header is matched against,
including<BR># headers that span multiple physical lines.<BR>#<BR># By default,
these patterns also apply to MIME headers and to the<BR># headers of attached
messages. With older Postfix versions, MIME and<BR># attached message headers
were treated as body text.<BR>#<BR># For details, see "man
header_checks".<BR>#<BR>#header_checks = regexp:/etc/postfix/header_checks</DIV>
<DIV> </DIV>
<DIV># FAST ETRN SERVICE<BR>#<BR># Postfix maintains per-destination logfiles
with information about<BR># deferred mail, so that mail can be flushed quickly
with the SMTP<BR># "ETRN domain.tld" command, or by executing "sendmail
-qRdomain.tld".<BR># See the ETRN_README document for a detailed
description.<BR># <BR># The fast_flush_domains parameter controls what
destinations are<BR># eligible for this service. By default, they are all
domains that<BR># this server is willing to relay mail to.<BR>#
<BR>#fast_flush_domains = $relay_domains</DIV>
<DIV> </DIV>
<DIV># SHOW SOFTWARE VERSION OR NOT<BR>#<BR># The smtpd_banner parameter
specifies the text that follows the 220<BR># code in the SMTP server's greeting
banner. Some people like to see<BR># the mail version advertised. By default,
Postfix shows no version.<BR>#<BR># You MUST specify $myhostname at the start of
the text. That is an<BR># RFC requirement. Postfix itself does not
care.<BR>#<BR>#smtpd_banner = $myhostname ESMTP $mail_name<BR>#smtpd_banner =
$myhostname ESMTP $mail_name ($mail_version)</DIV>
<DIV> </DIV>
<DIV># PARALLEL DELIVERY TO THE SAME DESTINATION<BR>#<BR># How many parallel
deliveries to the same user or domain? With local<BR># delivery, it does not
make sense to do massively parallel delivery<BR># to the same user, because
mailbox updates must happen sequentially,<BR># and expensive pipelines in
.forward files can cause disasters when<BR># too many are run at the same time.
With SMTP deliveries, 10<BR># simultaneous connections to the same domain could
be sufficient to<BR># raise eyebrows.<BR># <BR># Each message delivery transport
has its XXX_destination_concurrency_limit<BR># parameter. The default is
$default_destination_concurrency_limit for<BR># most delivery transports. For
the local delivery agent the default is 2.</DIV>
<DIV> </DIV>
<DIV>#local_destination_concurrency_limit =
2<BR>#default_destination_concurrency_limit = 20</DIV>
<DIV> </DIV>
<DIV># DEBUGGING CONTROL<BR>#<BR># The debug_peer_level parameter specifies the
increment in verbose<BR># logging level when an SMTP client or server host name
or address<BR># matches a pattern in the debug_peer_list
parameter.<BR>#<BR>debug_peer_level = 2</DIV>
<DIV> </DIV>
<DIV># The debug_peer_list parameter specifies an optional list of domain<BR>#
or network patterns, /file/name patterns or type:name tables. When<BR># an SMTP
client or server host name or address matches a pattern,<BR># increase the
verbose logging level by the amount specified in the<BR># debug_peer_level
parameter.<BR>#<BR>#debug_peer_list = 127.0.0.1<BR>#debug_peer_list =
some.domain</DIV>
<DIV> </DIV>
<DIV># The debugger_command specifies the external command that is executed<BR>#
when a Postfix daemon program is run with the -D option.<BR>#<BR># Use "command
.. & sleep 5" so that the debugger can attach before<BR># the process
marches on. If you use an X-based debugger, be sure to<BR># set up your
XAUTHORITY environment variable before starting
Postfix.<BR>#<BR>debugger_command =<BR>
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin<BR> xxgdb
$daemon_directory/$process_name $process_id & sleep 5</DIV>
<DIV> </DIV>
<DIV># If you can't use X, use this to capture the call stack when a<BR># daemon
crashes. The result is in a file in the configuration<BR># directory, and is
named after the process name and the process ID.<BR>#<BR># debugger_command
=<BR># PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo
cont;<BR># echo where) | gdb $daemon_directory/$process_name $process_id
2>&1<BR># >$config_directory/$process_name.$process_id.log &
sleep 5<BR>#<BR># Another possibility is to run gdb under a detached screen
session.<BR># To attach to the screen sesssion, su root and run "screen -r<BR>#
<id_string>" where <id_string> uniquely matches one of the
detached<BR># sessions (from "screen -list").<BR>#<BR># debugger_command
=<BR># PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH;
screen<BR># -dmS $process_name gdb
$daemon_directory/$process_name<BR># $process_id & sleep 1</DIV>
<DIV> </DIV>
<DIV># INSTALL-TIME CONFIGURATION INFORMATION<BR>#<BR># The following parameters
are used when installing a new Postfix version.<BR># <BR># sendmail_path: The
full pathname of the Postfix sendmail command.<BR># This is the
Sendmail-compatible mail posting interface.<BR># <BR>sendmail_path =
/usr/sbin/sendmail.postfix</DIV>
<DIV> </DIV>
<DIV># newaliases_path: The full pathname of the Postfix newaliases
command.<BR># This is the Sendmail-compatible command to build alias
databases.<BR>#<BR>newaliases_path = /usr/bin/newaliases.postfix</DIV>
<DIV> </DIV>
<DIV># mailq_path: The full pathname of the Postfix mailq command.
This<BR># is the Sendmail-compatible mail queue listing command.<BR>#
<BR>mailq_path = /usr/bin/mailq.postfix</DIV>
<DIV> </DIV>
<DIV># setgid_group: The group for mail submission and queue management<BR>#
commands. This must be a group name with a numerical group ID that<BR># is
not shared with other accounts, not even with the Postfix
account.<BR>#<BR>setgid_group = postdrop</DIV>
<DIV> </DIV>
<DIV># html_directory: The location of the Postfix HTML
documentation.<BR>#<BR>html_directory = no</DIV>
<DIV> </DIV>
<DIV># manpage_directory: The location of the Postfix on-line manual
pages.<BR>#<BR>manpage_directory = /usr/share/man</DIV>
<DIV> </DIV>
<DIV># sample_directory: The location of the Postfix sample configuration
files.<BR># This parameter is obsolete as of Postfix
2.1.<BR>#<BR>sample_directory = /usr/share/doc/postfix-2.2.2/samples</DIV>
<DIV> </DIV>
<DIV># readme_directory: The location of the Postfix README
files.<BR>#<BR>readme_directory =
/usr/share/doc/postfix-2.2.2/README_FILES<BR>canonical_maps =
hash:/etc/mail/virtusertable<BR>relayhost = smtp.cybernet.ch<BR>body_checks =
pcre:/etc/postfix/body_checks<BR>header_checks =
pcre:/etc/postfix/header_checks<BR>maps_rbl_domains =
bl.spamcop.net<BR>rbl_reply_maps =
hash:/etc/postfix/rbl_reply<BR>smtpd_client_restrictions = permit_mynetworks,
reject_rbl_client SB-EF4C-25TAH-3JWNB-T9N44-E6R2M-QHPLF.r.mail-abuse.com,
reject_rbl_client relays.ordb.org, reject_rbl_client opm.blitzed.org,
reject_rbl_client list.dsbl.org, reject_rbl_client sbl.spamhaus.org,
reject_rbl_client bl.spamcop.net, reject_rbl_client cbl.abuseat.org,
reject_rbl_client dul.dnsbl.sorbs.net, permit<BR>always_bcc =
rantalunta<BR>virtual_alias_maps = hash:/etc/postfix/local_domain<BR>
</DIV></SPAN></FONT></FONT></DIV></BODY></HTML>