<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Jernej Simončič wrote:
<blockquote cite="mid:951427849.20071104140235@ena.si" type="cite">
<pre wrap="">On Sunday, November 4, 2007, 13:49:55, Mitja Znidaric wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Še vedno nisem rešil zadeve 5.7.1.-Relay access denied...... :(
Prilagam dovecot.conf:
</pre>
</blockquote>
<pre wrap=""><!---->
Pošte verjetno ne pošiljaš prek Dovecota. Če uporabljaš postfix,
poglej nastavitev mynetworks v main.conf.
</pre>
</blockquote>
Lokalne nastavitve:<br>
IP od serverja: 10.20.30.37<br>
Mask: 255.255.255.0<br>
<br>
To imam vpisano:<br>
mynetworks = 10.20.30.0/24, 127.0.0.0/8<br>
<br>
Evo še ta datoteka... main.conf:<br>
<br>
# Global Postfix configuration file. This file lists only a subset<br>
# of all parameters. For the syntax, and for a complete parameter<br>
# list, see the postconf(5) manual page (command: "man 5 postconf").<br>
#<br>
# For common configuration examples, see BASIC_CONFIGURATION_README<br>
# and STANDARD_CONFIGURATION_README. To find these documents, use<br>
# the command "postconf html_directory readme_directory", or go to<br>
# <a class="moz-txt-link-freetext" href="http://www.postfix.org/">http://www.postfix.org/</a>.<br>
#<br>
# For best results, change no more than 2-3 parameters at a time,<br>
# and test if Postfix still works after every change.<br>
<br>
# 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<br>
<br>
# 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>
#<br>
queue_directory = /var/spool/postfix<br>
<br>
# The command_directory parameter specifies the location of all<br>
# postXXX commands.<br>
#<br>
command_directory = /usr/sbin<br>
<br>
# 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<br>
<br>
# 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>
#<br>
mail_owner = postfix<br>
<br>
# 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<br>
<br>
# 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 = mail.international-security.net<br>
#myhostname = virtual.domain.tld<br>
<br>
# 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 = international-security.net<br>
<br>
# 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 class="moz-txt-link-abbreviated"
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<br>
<br>
# RECEIVING MAIL<br>
<br>
# 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
class="moz-txt-link-abbreviated" href="mailto:user@%5Bip.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 = all<br>
#inet_interfaces = $myhostname<br>
#inet_interfaces = $myhostname, localhost<br>
#inet_interfaces = localhost<br>
<br>
# 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<br>
<br>
# 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 class="moz-txt-link-abbreviated"
href="mailto:user@%5Bthe.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,
international-security.net<br>
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain<br>
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,<br>
# mail.$mydomain, <a class="moz-txt-link-abbreviated"
href="http://www.$mydomain">www.$mydomain</a>, <a
class="moz-txt-link-abbreviated" href="ftp://ftp.$mydomain">ftp.$mydomain</a><br>
<br>
# 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 class="moz-txt-link-abbreviated"
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 =<br>
<br>
# 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<br>
<br>
# TRUST AND RELAY CONTROL<br>
<br>
# 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<br>
<br>
# 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 = 10.20.30.0/24, 127.0.0.0/8<br>
#mynetworks = $config_directory/mynetworks<br>
#mynetworks = hash:/etc/postfix/network_table<br>
<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<br>
<br>
# INTERNET OR INTRANET<br>
<br>
# 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 = $mydomain<br>
#relayhost = [gateway.my.domain]<br>
#relayhost = [mailserver.isp.tld]<br>
#relayhost = uucphost<br>
#relayhost = [an.ip.add.ress]<br>
<br>
# 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 class="moz-txt-link-abbreviated" href="mailto:user@domain.tld">user@domain.tld</a>
address.<br>
# <br>
#relay_recipient_maps = hash:/etc/postfix/relay_recipients<br>
<br>
# 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<br>
<br>
# 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.<br>
<br>
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)<br>
#<br>
# The VIRTUAL_README document gives information about the many forms<br>
# of domain hosting that Postfix supports.<br>
<br>
# "USER HAS MOVED" BOUNCE MESSAGES<br>
#<br>
# See the discussion in the ADDRESS_REWRITING_README document.<br>
<br>
# TRANSPORT MAP<br>
#<br>
# See the discussion in the ADDRESS_REWRITING_README document.<br>
<br>
# 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>
virtual_maps = hash:/etc/postfix/virtual<br>
#alias_maps = hash:/etc/aliases, nis:mail.aliases<br>
#alias_maps = netinfo:/aliases<br>
<br>
# 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>
virtual_database = hash:/etc/postfix/virtual<br>
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases<br>
<br>
# 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 = +<br>
<br>
# 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<br>
<br>
# 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"<br>
<br>
# 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:/var/lib/imap/socket/lmtp<br>
<br>
# If using the cyrus-imapd IMAP server deliver local mail to the IMAP<br>
# server using LMTP (Local Mail Transport Protocol), this is prefered<br>
# over the older cyrus deliver program by setting the<br>
# mailbox_transport as below:<br>
#<br>
# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp<br>
#<br>
# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via<br>
# these settings.<br>
#<br>
# local_destination_recipient_limit = 300<br>
# local_destination_concurrency_limit = 5<br>
#<br>
# Of course you should adjust these settings as appropriate for the<br>
# capacity of the hardware you are using. The recipient limit setting<br>
# can be used to take advantage of the single instance message store<br>
# capability of Cyrus. The concurrency limit can be used to control<br>
# how many simultaneous LMTP sessions will be permitted to the Cyrus<br>
# message store. <br>
#<br>
# To use the old cyrus deliver program you have to set:<br>
#mailbox_transport = cyrus<br>
<br>
# 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:/var/lib/imap/socket/lmtp<br>
#fallback_transport =<br>
<br>
# The luser_relay parameter specifies an optional destination address<br>
# for unknown recipients. By default, mail for unknown@$mydestination,<br>
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] 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 = $user@other.host<br>
#luser_relay = $local@other.host<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.<br>
<br>
# 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<br>
<br>
# 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<br>
<br>
# 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)<br>
<br>
# 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.<br>
<br>
#local_destination_concurrency_limit = 2<br>
#default_destination_concurrency_limit = 20<br>
<br>
# 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<br>
<br>
# 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<br>
<br>
# 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<br>
<br>
# 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<br>
<br>
# 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<br>
<br>
# 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<br>
<br>
# 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<br>
<br>
# 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<br>
<br>
# html_directory: The location of the Postfix HTML documentation.<br>
#<br>
html_directory = no<br>
<br>
# manpage_directory: The location of the Postfix on-line manual pages.<br>
#<br>
manpage_directory = /usr/share/man<br>
<br>
# 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.4.3/samples<br>
<br>
# readme_directory: The location of the Postfix README files.<br>
#<br>
readme_directory = /usr/share/doc/postfix-2.4.3/README_FILES<br>
message_size_limit = 20480000<br>
<br>
<br>
Lp,<br>
Mitja<br>
</body>
</html>