{"id":214,"date":"2012-02-17T16:27:43","date_gmt":"2012-02-17T07:27:43","guid":{"rendered":"http:\/\/kaz.it-n.jp\/wordpress\/?page_id=214"},"modified":"2012-02-17T16:27:43","modified_gmt":"2012-02-17T07:27:43","slug":"main-cf","status":"publish","type":"page","link":"https:\/\/kaz.it-n.jp\/?page_id=214","title":{"rendered":"main.cf"},"content":{"rendered":"<p># Global Postfix configuration file. This file lists only a subset<br \/>\n# of all parameters. For the syntax, and for a complete parameter<br \/>\n# list, see the postconf(5) manual page (command: &#8220;man 5 postconf&#8221;).<br \/>\n#<br \/>\n# For common configuration examples, see BASIC_CONFIGURATION_README<br \/>\n# and STANDARD_CONFIGURATION_README. To find these documents, use<br \/>\n# the command &#8220;postconf html_directory readme_directory&#8221;, or go to<br \/>\n# http:\/\/www.postfix.org\/.<br \/>\n#<br \/>\n# For best results, change no more than 2-3 parameters at a time,<br \/>\n# and test if Postfix still works after every change.<\/p>\n<p># SOFT BOUNCE<br \/>\n#<br \/>\n# The soft_bounce parameter provides a limited safety net for<br \/>\n# testing. When soft_bounce is enabled, mail will remain queued that<br \/>\n# would otherwise bounce. This parameter disables locally-generated<br \/>\n# bounces, and prevents the SMTP server from rejecting mail permanently<br \/>\n# (by changing 5xx replies into 4xx replies). However, soft_bounce<br \/>\n# is no cure for address rewriting mistakes or mail routing mistakes.<br \/>\n#<br \/>\n#soft_bounce = no<\/p>\n<p># LOCAL PATHNAME INFORMATION<br \/>\n#<br \/>\n# The queue_directory specifies the location of the Postfix queue.<br \/>\n# This is also the root directory of Postfix daemons that run chrooted.<br \/>\n# See the files in examples\/chroot-setup for setting up Postfix chroot<br \/>\n# environments on different UNIX systems.<br \/>\n#<br \/>\nqueue_directory = \/var\/spool\/postfix<\/p>\n<p># The command_directory parameter specifies the location of all<br \/>\n# postXXX commands.<br \/>\n#<br \/>\ncommand_directory = \/usr\/sbin<\/p>\n<p># The daemon_directory parameter specifies the location of all Postfix<br \/>\n# daemon programs (i.e. programs listed in the master.cf file). This<br \/>\n# directory must be owned by root.<br \/>\n#<br \/>\ndaemon_directory = \/usr\/libexec\/postfix<\/p>\n<p># The data_directory parameter specifies the location of Postfix-writable<br \/>\n# data files (caches, random numbers). This directory must be owned<br \/>\n# by the mail_owner account (see below).<br \/>\n#<br \/>\ndata_directory = \/var\/lib\/postfix<\/p>\n<p># QUEUE AND PROCESS OWNERSHIP<br \/>\n#<br \/>\n# The mail_owner parameter specifies the owner of the Postfix queue<br \/>\n# and of most Postfix daemon processes. Specify the name of a user<br \/>\n# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS<br \/>\n# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In<br \/>\n# particular, don&#8217;t specify nobody or daemon. PLEASE USE A DEDICATED<br \/>\n# USER.<br \/>\n#<br \/>\nmail_owner = postfix<\/p>\n<p># The default_privs parameter specifies the default rights used by<br \/>\n# the local delivery agent for delivery to external file or command.<br \/>\n# These rights are used in the absence of a recipient user context.<br \/>\n# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.<br \/>\n#<br \/>\n#default_privs = nobody<\/p>\n<p># INTERNET HOST AND DOMAIN NAMES<br \/>\n#<br \/>\n# The myhostname parameter specifies the internet hostname of this<br \/>\n# mail system. The default is to use the fully-qualified domain name<br \/>\n# from gethostname(). $myhostname is used as a default value for many<br \/>\n# other configuration parameters.<br \/>\n#<br \/>\n#myhostname = host.domain.tld<br \/>\n#myhostname = virtual.domain.tld<br \/>\n<strong><span style=\"color: #ff0000;\">myhostname = mail.example.jp<\/span><\/strong><\/p>\n<p># The mydomain parameter specifies the local internet domain name.<br \/>\n# The default is to use $myhostname minus the first component.<br \/>\n# $mydomain is used as a default value for many other configuration<br \/>\n# parameters.<br \/>\n#<br \/>\n#mydomain = domain.tld<br \/>\n<strong><span style=\"color: #ff0000;\">mydomain = example.jp<\/span><\/strong><\/p>\n<p># SENDING MAIL<br \/>\n#<br \/>\n# The myorigin parameter specifies the domain that locally-posted<br \/>\n# mail appears to come from. The default is to append $myhostname,<br \/>\n# which is fine for small sites. If you run a domain with multiple<br \/>\n# machines, you should (1) change this to $mydomain and (2) set up<br \/>\n# a domain-wide alias database that aliases each user to<br \/>\n# user@that.users.mailhost.<br \/>\n#<br \/>\n# For the sake of consistency between sender and recipient addresses,<br \/>\n# myorigin also specifies the default domain name that is appended<br \/>\n# to recipient addresses that have no @domain part.<br \/>\n#<br \/>\n#myorigin = $myhostname<br \/>\n<strong><span style=\"color: #ff0000;\">myorigin = $mydomain<\/span><\/strong><\/p>\n<p># RECEIVING MAIL<\/p>\n<p># The inet_interfaces parameter specifies the network interface<br \/>\n# addresses that this mail system receives mail on. By default,<br \/>\n# the software claims all active interfaces on the machine. The<br \/>\n# parameter also controls delivery of mail to user@[ip.address].<br \/>\n#<br \/>\n# See also the proxy_interfaces parameter, for network addresses that<br \/>\n# are forwarded to us via a proxy or network address translator.<br \/>\n#<br \/>\n# Note: you need to stop\/start Postfix when this parameter changes.<br \/>\n#<br \/>\n<strong><span style=\"color: #ff0000;\">inet_interfaces = all<\/span><\/strong><br \/>\n#inet_interfaces = $myhostname<br \/>\n#inet_interfaces = $myhostname, localhost<\/p>\n<p># The proxy_interfaces parameter specifies the network interface<br \/>\n# addresses that this mail system receives mail on by way of a<br \/>\n# proxy or network address translation unit. This setting extends<br \/>\n# the address list specified with the inet_interfaces parameter.<br \/>\n#<br \/>\n# You must specify your proxy\/NAT addresses when your system is a<br \/>\n# backup MX host for other domains, otherwise mail delivery loops<br \/>\n# will happen when the primary MX host is down.<br \/>\n#<br \/>\n#proxy_interfaces =<br \/>\n#proxy_interfaces = 1.2.3.4<\/p>\n<p># The mydestination parameter specifies the list of domains that this<br \/>\n# machine considers itself the final destination for.<br \/>\n#<br \/>\n# These domains are routed to the delivery agent specified with the<br \/>\n# local_transport parameter setting. By default, that is the UNIX<br \/>\n# compatible delivery agent that lookups all recipients in \/etc\/passwd<br \/>\n# and \/etc\/aliases or their equivalent.<br \/>\n#<br \/>\n# The default is $myhostname + localhost.$mydomain. On a mail domain<br \/>\n# gateway, you should also include $mydomain.<br \/>\n#<br \/>\n# Do not specify the names of virtual domains &#8211; those domains are<br \/>\n# specified elsewhere (see VIRTUAL_README).<br \/>\n#<br \/>\n# Do not specify the names of domains that this machine is backup MX<br \/>\n# host for. Specify those names via the relay_domains settings for<br \/>\n# the SMTP server, or use permit_mx_backup if you are lazy (see<br \/>\n# STANDARD_CONFIGURATION_README).<br \/>\n#<br \/>\n# The local machine is always the final destination for mail addressed<br \/>\n# to user@[the.net.work.address] of an interface that the mail system<br \/>\n# receives mail on (see the inet_interfaces parameter).<br \/>\n#<br \/>\n# Specify a list of host or domain names, \/file\/name or type:table<br \/>\n# patterns, separated by commas and\/or whitespace. A \/file\/name<br \/>\n# pattern is replaced by its contents; a type:table is matched when<br \/>\n# a name matches a lookup key (the right-hand side is ignored).<br \/>\n# Continue long lines by starting the next line with whitespace.<br \/>\n#<br \/>\n# See also below, section &#8220;REJECTING MAIL FOR UNKNOWN LOCAL USERS&#8221;.<br \/>\n#<br \/>\n#mydestination = $myhostname, localhost.$mydomain, localhost<br \/>\nmydestination = $myhostname, localhost.$mydomain, localhost, $mydomain<br \/>\n#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,<br \/>\n# mail.$mydomain, www.$mydomain, ftp.$mydomain<\/p>\n<p># REJECTING MAIL FOR UNKNOWN LOCAL USERS<br \/>\n#<br \/>\n# The local_recipient_maps parameter specifies optional lookup tables<br \/>\n# with all names or addresses of users that are local with respect<br \/>\n# to $mydestination, $inet_interfaces or $proxy_interfaces.<br \/>\n#<br \/>\n# If this parameter is defined, then the SMTP server will reject<br \/>\n# mail for unknown local users. This parameter is defined by default.<br \/>\n#<br \/>\n# To turn off local recipient checking in the SMTP server, specify<br \/>\n# local_recipient_maps = (i.e. empty).<br \/>\n#<br \/>\n# The default setting assumes that you use the default Postfix local<br \/>\n# delivery agent for local delivery. You need to update the<br \/>\n# local_recipient_maps setting if:<br \/>\n#<br \/>\n# &#8211; You define $mydestination domain recipients in files other than<br \/>\n# \/etc\/passwd, \/etc\/aliases, or the $virtual_alias_maps files.<br \/>\n# For example, you define $mydestination domain recipients in<br \/>\n# the $virtual_mailbox_maps files.<br \/>\n#<br \/>\n# &#8211; You redefine the local delivery agent in master.cf.<br \/>\n#<br \/>\n# &#8211; You redefine the &#8220;local_transport&#8221; setting in main.cf.<br \/>\n#<br \/>\n# &#8211; You use the &#8220;luser_relay&#8221;, &#8220;mailbox_transport&#8221;, or &#8220;fallback_transport&#8221;<br \/>\n# feature of the Postfix local delivery agent (see local(8)).<br \/>\n#<br \/>\n# Details are described in the LOCAL_RECIPIENT_README file.<br \/>\n#<br \/>\n# Beware: if the Postfix SMTP server runs chrooted, you probably have<br \/>\n# to access the passwd file via the proxymap service, in order to<br \/>\n# overcome chroot restrictions. The alternative, having a copy of<br \/>\n# the system passwd file in the chroot jail is just not practical.<br \/>\n#<br \/>\n# The right-hand side of the lookup tables is conveniently ignored.<br \/>\n# In the left-hand side, specify a bare username, an @domain.tld<br \/>\n# wild-card, or specify a user@domain.tld address.<br \/>\n#<br \/>\n#local_recipient_maps = unix:passwd.byname $alias_maps<br \/>\n#local_recipient_maps = proxy:unix:passwd.byname $alias_maps<br \/>\n#local_recipient_maps =<\/p>\n<p># The unknown_local_recipient_reject_code specifies the SMTP server<br \/>\n# response code when a recipient domain matches $mydestination or<br \/>\n# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty<br \/>\n# and the recipient address or address local-part is not found.<br \/>\n#<br \/>\n# The default setting is 550 (reject mail) but it is safer to start<br \/>\n# with 450 (try again later) until you are certain that your<br \/>\n# local_recipient_maps settings are OK.<br \/>\n#<br \/>\nunknown_local_recipient_reject_code = 550<\/p>\n<p># TRUST AND RELAY CONTROL<\/p>\n<p># The mynetworks parameter specifies the list of &#8220;trusted&#8221; SMTP<br \/>\n# clients that have more privileges than &#8220;strangers&#8221;.<br \/>\n#<br \/>\n# In particular, &#8220;trusted&#8221; SMTP clients are allowed to relay mail<br \/>\n# through Postfix. See the smtpd_recipient_restrictions parameter<br \/>\n# in postconf(5).<br \/>\n#<br \/>\n# You can specify the list of &#8220;trusted&#8221; network addresses by hand<br \/>\n# or you can let Postfix do it for you (which is the default).<br \/>\n#<br \/>\n# By default (mynetworks_style = subnet), Postfix &#8220;trusts&#8221; SMTP<br \/>\n# clients in the same IP subnetworks as the local machine.<br \/>\n# On Linux, this does works correctly only with interfaces specified<br \/>\n# with the &#8220;ifconfig&#8221; command.<br \/>\n#<br \/>\n# Specify &#8220;mynetworks_style = class&#8221; when Postfix should &#8220;trust&#8221; SMTP<br \/>\n# clients in the same IP class A\/B\/C networks as the local machine.<br \/>\n# Don&#8217;t do this with a dialup site &#8211; it would cause Postfix to &#8220;trust&#8221;<br \/>\n# your entire provider&#8217;s network. Instead, specify an explicit<br \/>\n# mynetworks list by hand, as described below.<br \/>\n#<br \/>\n# Specify &#8220;mynetworks_style = host&#8221; when Postfix should &#8220;trust&#8221;<br \/>\n# only the local machine.<br \/>\n#<br \/>\n#mynetworks_style = class<br \/>\n#mynetworks_style = subnet<br \/>\n#mynetworks_style = host<\/p>\n<p># Alternatively, you can specify the mynetworks list by hand, in<br \/>\n# which case Postfix ignores the mynetworks_style setting.<br \/>\n#<br \/>\n# Specify an explicit list of network\/netmask patterns, where the<br \/>\n# mask specifies the number of bits in the network part of a host<br \/>\n# address.<br \/>\n#<br \/>\n# You can also specify the absolute pathname of a pattern file instead<br \/>\n# of listing the patterns here. Specify type:table for table-based lookups<br \/>\n# (the value on the table right-hand side is not used).<br \/>\n#<br \/>\n#mynetworks = 168.100.189.0\/28, 127.0.0.0\/8<br \/>\n#mynetworks = $config_directory\/mynetworks<br \/>\n#mynetworks = hash:\/etc\/postfix\/network_table<\/p>\n<p># The relay_domains parameter restricts what destinations this system will<br \/>\n# relay mail to. See the smtpd_recipient_restrictions description in<br \/>\n# postconf(5) for detailed information.<br \/>\n#<br \/>\n# By default, Postfix relays mail<br \/>\n# &#8211; from &#8220;trusted&#8221; clients (IP address matches $mynetworks) to any destination,<br \/>\n# &#8211; from &#8220;untrusted&#8221; clients to destinations that match $relay_domains or<br \/>\n# subdomains thereof, except addresses with sender-specified routing.<br \/>\n# The default relay_domains value is $mydestination.<br \/>\n#<br \/>\n# In addition to the above, the Postfix SMTP server by default accepts mail<br \/>\n# that Postfix is final destination for:<br \/>\n# &#8211; destinations that match $inet_interfaces or $proxy_interfaces,<br \/>\n# &#8211; destinations that match $mydestination<br \/>\n# &#8211; destinations that match $virtual_alias_domains,<br \/>\n# &#8211; destinations that match $virtual_mailbox_domains.<br \/>\n# These destinations do not need to be listed in $relay_domains.<br \/>\n#<br \/>\n# Specify a list of hosts or domains, \/file\/name patterns or type:name<br \/>\n# lookup tables, separated by commas and\/or whitespace. Continue<br \/>\n# long lines by starting the next line with whitespace. A file name<br \/>\n# is replaced by its contents; a type:name table is matched when a<br \/>\n# (parent) domain appears as lookup key.<br \/>\n#<br \/>\n# NOTE: Postfix will not automatically forward mail for domains that<br \/>\n# list this system as their primary or backup MX host. See the<br \/>\n# permit_mx_backup restriction description in postconf(5).<br \/>\n#<br \/>\n#relay_domains = $mydestination<\/p>\n<p># INTERNET OR INTRANET<\/p>\n<p># The relayhost parameter specifies the default host to send mail to<br \/>\n# when no entry is matched in the optional transport(5) table. When<br \/>\n# no relayhost is given, mail is routed directly to the destination.<br \/>\n#<br \/>\n# On an intranet, specify the organizational domain name. If your<br \/>\n# internal DNS uses no MX records, specify the name of the intranet<br \/>\n# gateway host instead.<br \/>\n#<br \/>\n# In the case of SMTP, specify a domain, host, host:port, [host]:port,<br \/>\n# [address] or [address]:port; the form [host] turns off MX lookups.<br \/>\n#<br \/>\n# If you&#8217;re connected via UUCP, see also the default_transport parameter.<br \/>\n#<br \/>\n#relayhost = $mydomain<br \/>\n#relayhost = [gateway.my.domain]<br \/>\n#relayhost = [mailserver.isp.tld]<br \/>\n#relayhost = uucphost<br \/>\n#relayhost = [an.ip.add.ress]<\/p>\n<p># REJECTING UNKNOWN RELAY USERS<br \/>\n#<br \/>\n# The relay_recipient_maps parameter specifies optional lookup tables<br \/>\n# with all addresses in the domains that match $relay_domains.<br \/>\n#<br \/>\n# If this parameter is defined, then the SMTP server will reject<br \/>\n# mail for unknown relay users. This feature is off by default.<br \/>\n#<br \/>\n# The right-hand side of the lookup tables is conveniently ignored.<br \/>\n# In the left-hand side, specify an @domain.tld wild-card, or specify<br \/>\n# a user@domain.tld address.<br \/>\n#<br \/>\n#relay_recipient_maps = hash:\/etc\/postfix\/relay_recipients<\/p>\n<p># INPUT RATE CONTROL<br \/>\n#<br \/>\n# The in_flow_delay configuration parameter implements mail input<br \/>\n# flow control. This feature is turned on by default, although it<br \/>\n# still needs further development (it&#8217;s disabled on SCO UNIX due<br \/>\n# to an SCO bug).<br \/>\n#<br \/>\n# A Postfix process will pause for $in_flow_delay seconds before<br \/>\n# accepting a new message, when the message arrival rate exceeds the<br \/>\n# message delivery rate. With the default 100 SMTP server process<br \/>\n# limit, this limits the mail inflow to 100 messages a second more<br \/>\n# than the number of messages delivered per second.<br \/>\n#<br \/>\n# Specify 0 to disable the feature. Valid delays are 0..10.<br \/>\n#<br \/>\n#in_flow_delay = 1s<\/p>\n<p># ADDRESS REWRITING<br \/>\n#<br \/>\n# The ADDRESS_REWRITING_README document gives information about<br \/>\n# address masquerading or other forms of address rewriting including<br \/>\n# username-&gt;Firstname.Lastname mapping.<\/p>\n<p># ADDRESS REDIRECTION (VIRTUAL DOMAIN)<br \/>\n#<br \/>\n# The VIRTUAL_README document gives information about the many forms<br \/>\n# of domain hosting that Postfix supports.<\/p>\n<p># &#8220;USER HAS MOVED&#8221; BOUNCE MESSAGES<br \/>\n#<br \/>\n# See the discussion in the ADDRESS_REWRITING_README document.<\/p>\n<p># TRANSPORT MAP<br \/>\n#<br \/>\n# See the discussion in the ADDRESS_REWRITING_README document.<\/p>\n<p># ALIAS DATABASE<br \/>\n#<br \/>\n# The alias_maps parameter specifies the list of alias databases used<br \/>\n# by the local delivery agent. The default list is system dependent.<br \/>\n#<br \/>\n# On systems with NIS, the default is to search the local alias<br \/>\n# database, then the NIS alias database. See aliases(5) for syntax<br \/>\n# details.<br \/>\n#<br \/>\n# If you change the alias database, run &#8220;postalias \/etc\/aliases&#8221; (or<br \/>\n# wherever your system stores the mail alias file), or simply run<br \/>\n# &#8220;newaliases&#8221; to build the necessary DBM or DB file.<br \/>\n#<br \/>\n# It will take a minute or so before changes become visible. Use<br \/>\n# &#8220;postfix reload&#8221; to eliminate the delay.<br \/>\n#<br \/>\n#alias_maps = dbm:\/etc\/aliases<br \/>\n<strong><span style=\"color: #ff0000;\">alias_maps = hash:\/etc\/aliases<\/span><\/strong><br \/>\n#alias_maps = hash:\/etc\/aliases, nis:mail.aliases<br \/>\n#alias_maps = netinfo:\/aliases<\/p>\n<p># The alias_database parameter specifies the alias database(s) that<br \/>\n# are built with &#8220;newaliases&#8221; or &#8220;sendmail -bi&#8221;. This is a separate<br \/>\n# configuration parameter, because alias_maps (see above) may specify<br \/>\n# tables that are not necessarily all under control by Postfix.<br \/>\n#<br \/>\n#alias_database = dbm:\/etc\/aliases<br \/>\n#alias_database = dbm:\/etc\/mail\/aliases<br \/>\n<strong><span style=\"color: #ff0000;\">alias_database = hash:\/etc\/aliases<\/span><\/strong><br \/>\n#alias_database = hash:\/etc\/aliases, hash:\/opt\/majordomo\/aliases<\/p>\n<p># ADDRESS EXTENSIONS (e.g., user+foo)<br \/>\n#<br \/>\n# The recipient_delimiter parameter specifies the separator between<br \/>\n# user names and address extensions (user+foo). See canonical(5),<br \/>\n# local(8), relocated(5) and virtual(5) for the effects this has on<br \/>\n# aliases, canonical, virtual, relocated and .forward file lookups.<br \/>\n# Basically, the software tries user+foo and .forward+foo before<br \/>\n# trying user and .forward.<br \/>\n#<br \/>\n#recipient_delimiter = +<\/p>\n<p># DELIVERY TO MAILBOX<br \/>\n#<br \/>\n# The home_mailbox parameter specifies the optional pathname of a<br \/>\n# mailbox file relative to a user&#8217;s home directory. The default<br \/>\n# mailbox file is \/var\/spool\/mail\/user or \/var\/mail\/user. Specify<br \/>\n# &#8220;Maildir\/&#8221; for qmail-style delivery (the \/ is required).<br \/>\n#<br \/>\n#home_mailbox = Mailbox<br \/>\n<strong><span style=\"color: #ff0000;\">home_mailbox = Maildir\/<\/span><\/strong><\/p>\n<p># The mail_spool_directory parameter specifies the directory where<br \/>\n# UNIX-style mailboxes are kept. The default setting depends on the<br \/>\n# system type.<br \/>\n#<br \/>\n#mail_spool_directory = \/var\/mail<br \/>\n#mail_spool_directory = \/var\/spool\/mail<\/p>\n<p># The mailbox_command parameter specifies the optional external<br \/>\n# command to use instead of mailbox delivery. The command is run as<br \/>\n# the recipient with proper HOME, SHELL and LOGNAME environment settings.<br \/>\n# Exception: delivery for root is done as $default_user.<br \/>\n#<br \/>\n# Other environment variables of interest: USER (recipient username),<br \/>\n# EXTENSION (address extension), DOMAIN (domain part of address),<br \/>\n# and LOCAL (the address localpart).<br \/>\n#<br \/>\n# Unlike other Postfix configuration parameters, the mailbox_command<br \/>\n# parameter is not subjected to $parameter substitutions. This is to<br \/>\n# make it easier to specify shell syntax (see example below).<br \/>\n#<br \/>\n# Avoid shell meta characters because they will force Postfix to run<br \/>\n# an expensive shell process. Procmail alone is expensive enough.<br \/>\n#<br \/>\n# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN<br \/>\n# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.<br \/>\n#<br \/>\n#mailbox_command = \/some\/where\/procmail<br \/>\n#mailbox_command = \/some\/where\/procmail -a &#8220;$EXTENSION&#8221;<\/p>\n<p># The mailbox_transport specifies the optional transport in master.cf<br \/>\n# to use after processing aliases and .forward files. This parameter<br \/>\n# has precedence over the mailbox_command, fallback_transport and<br \/>\n# luser_relay parameters.<br \/>\n#<br \/>\n# Specify a string of the form transport:nexthop, where transport is<br \/>\n# the name of a mail delivery transport defined in master.cf. The<br \/>\n# :nexthop part is optional. For more details see the sample transport<br \/>\n# configuration file.<br \/>\n#<br \/>\n# NOTE: if you use this feature for accounts not in the UNIX password<br \/>\n# file, then you must update the &#8220;local_recipient_maps&#8221; setting in<br \/>\n# the main.cf file, otherwise the SMTP server will reject mail for<br \/>\n# non-UNIX accounts with &#8220;User unknown in local recipient table&#8221;.<br \/>\n#<br \/>\n#mailbox_transport = lmtp:unix:\/file\/name<br \/>\n#mailbox_transport = cyrus<\/p>\n<p># The fallback_transport specifies the optional transport in master.cf<br \/>\n# to use for recipients that are not found in the UNIX passwd database.<br \/>\n# This parameter has precedence over the luser_relay parameter.<br \/>\n#<br \/>\n# Specify a string of the form transport:nexthop, where transport is<br \/>\n# the name of a mail delivery transport defined in master.cf. The<br \/>\n# :nexthop part is optional. For more details see the sample transport<br \/>\n# configuration file.<br \/>\n#<br \/>\n# NOTE: if you use this feature for accounts not in the UNIX password<br \/>\n# file, then you must update the &#8220;local_recipient_maps&#8221; setting in<br \/>\n# the main.cf file, otherwise the SMTP server will reject mail for<br \/>\n# non-UNIX accounts with &#8220;User unknown in local recipient table&#8221;.<br \/>\n#<br \/>\n#fallback_transport = lmtp:unix:\/file\/name<br \/>\n#fallback_transport = cyrus<br \/>\n#fallback_transport =<\/p>\n<p># The luser_relay parameter specifies an optional destination address<br \/>\n# for unknown recipients. By default, mail for unknown@$mydestination,<br \/>\n# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned<br \/>\n# as undeliverable.<br \/>\n#<br \/>\n# The following expansions are done on luser_relay: $user (recipient<br \/>\n# username), $shell (recipient shell), $home (recipient home directory),<br \/>\n# $recipient (full recipient address), $extension (recipient address<br \/>\n# extension), $domain (recipient domain), $local (entire recipient<br \/>\n# localpart), $recipient_delimiter. Specify ${name?value} or<br \/>\n# ${name:value} to expand value only when $name does (does not) exist.<br \/>\n#<br \/>\n# luser_relay works only for the default Postfix local delivery agent.<br \/>\n#<br \/>\n# NOTE: if you use this feature for accounts not in the UNIX password<br \/>\n# file, then you must specify &#8220;local_recipient_maps =&#8221; (i.e. empty) in<br \/>\n# the main.cf file, otherwise the SMTP server will reject mail for<br \/>\n# non-UNIX accounts with &#8220;User unknown in local recipient table&#8221;.<br \/>\n#<br \/>\n#luser_relay = $user@other.host<br \/>\n#luser_relay = $local@other.host<br \/>\n#luser_relay = admin+$local<\/p>\n<p># JUNK MAIL CONTROLS<br \/>\n#<br \/>\n# The controls listed here are only a very small subset. The file<br \/>\n# SMTPD_ACCESS_README provides an overview.<\/p>\n<p># The header_checks parameter specifies an optional table with patterns<br \/>\n# that each logical message header is matched against, including<br \/>\n# headers that span multiple physical lines.<br \/>\n#<br \/>\n# By default, these patterns also apply to MIME headers and to the<br \/>\n# headers of attached messages. With older Postfix versions, MIME and<br \/>\n# attached message headers were treated as body text.<br \/>\n#<br \/>\n# For details, see &#8220;man header_checks&#8221;.<br \/>\n#<br \/>\n#header_checks = regexp:\/etc\/postfix\/header_checks<\/p>\n<p># FAST ETRN SERVICE<br \/>\n#<br \/>\n# Postfix maintains per-destination logfiles with information about<br \/>\n# deferred mail, so that mail can be flushed quickly with the SMTP<br \/>\n# &#8220;ETRN domain.tld&#8221; command, or by executing &#8220;sendmail -qRdomain.tld&#8221;.<br \/>\n# See the ETRN_README document for a detailed description.<br \/>\n#<br \/>\n# The fast_flush_domains parameter controls what destinations are<br \/>\n# eligible for this service. By default, they are all domains that<br \/>\n# this server is willing to relay mail to.<br \/>\n#<br \/>\n#fast_flush_domains = $relay_domains<\/p>\n<p># SHOW SOFTWARE VERSION OR NOT<br \/>\n#<br \/>\n# The smtpd_banner parameter specifies the text that follows the 220<br \/>\n# code in the SMTP server&#8217;s greeting banner. Some people like to see<br \/>\n# the mail version advertised. By default, Postfix shows no version.<br \/>\n#<br \/>\n# You MUST specify $myhostname at the start of the text. That is an<br \/>\n# RFC requirement. Postfix itself does not care.<br \/>\n#<br \/>\n#smtpd_banner = $myhostname ESMTP $mail_name<br \/>\n#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)<\/p>\n<p># PARALLEL DELIVERY TO THE SAME DESTINATION<br \/>\n#<br \/>\n# How many parallel deliveries to the same user or domain? With local<br \/>\n# delivery, it does not make sense to do massively parallel delivery<br \/>\n# to the same user, because mailbox updates must happen sequentially,<br \/>\n# and expensive pipelines in .forward files can cause disasters when<br \/>\n# too many are run at the same time. With SMTP deliveries, 10<br \/>\n# simultaneous connections to the same domain could be sufficient to<br \/>\n# raise eyebrows.<br \/>\n#<br \/>\n# Each message delivery transport has its XXX_destination_concurrency_limit<br \/>\n# parameter. The default is $default_destination_concurrency_limit for<br \/>\n# most delivery transports. For the local delivery agent the default is 2.<\/p>\n<p>#local_destination_concurrency_limit = 2<br \/>\n#default_destination_concurrency_limit = 20<\/p>\n<p># DEBUGGING CONTROL<br \/>\n#<br \/>\n# The debug_peer_level parameter specifies the increment in verbose<br \/>\n# logging level when an SMTP client or server host name or address<br \/>\n# matches a pattern in the debug_peer_list parameter.<br \/>\n#<br \/>\ndebug_peer_level = 2<\/p>\n<p># The debug_peer_list parameter specifies an optional list of domain<br \/>\n# or network patterns, \/file\/name patterns or type:name tables. When<br \/>\n# an SMTP client or server host name or address matches a pattern,<br \/>\n# increase the verbose logging level by the amount specified in the<br \/>\n# debug_peer_level parameter.<br \/>\n#<br \/>\n#debug_peer_list = 127.0.0.1<br \/>\n#debug_peer_list = some.domain<\/p>\n<p># The debugger_command specifies the external command that is executed<br \/>\n# when a Postfix daemon program is run with the -D option.<br \/>\n#<br \/>\n# Use &#8220;command .. &amp; sleep 5&#8221; so that the debugger can attach before<br \/>\n# the process marches on. If you use an X-based debugger, be sure to<br \/>\n# set up your XAUTHORITY environment variable before starting Postfix.<br \/>\n#<br \/>\ndebugger_command =<br \/>\nPATH=\/bin:\/usr\/bin:\/usr\/local\/bin:\/usr\/X11R6\/bin<br \/>\nddd $daemon_directory\/$process_name $process_id &amp; sleep 5<\/p>\n<p># If you can&#8217;t use X, use this to capture the call stack when a<br \/>\n# daemon crashes. The result is in a file in the configuration<br \/>\n# directory, and is named after the process name and the process ID.<br \/>\n#<br \/>\n# debugger_command =<br \/>\n# PATH=\/bin:\/usr\/bin:\/usr\/local\/bin; export PATH; (echo cont;<br \/>\n# echo where) | gdb $daemon_directory\/$process_name $process_id 2&gt;&amp;1<br \/>\n# &gt;$config_directory\/$process_name.$process_id.log &amp; sleep 5<br \/>\n#<br \/>\n# Another possibility is to run gdb under a detached screen session.<br \/>\n# To attach to the screen sesssion, su root and run &#8220;screen -r<br \/>\n# &#8221; where uniquely matches one of the detached<br \/>\n# sessions (from &#8220;screen -list&#8221;).<br \/>\n#<br \/>\n# debugger_command =<br \/>\n# PATH=\/bin:\/usr\/bin:\/sbin:\/usr\/sbin; export PATH; screen<br \/>\n# -dmS $process_name gdb $daemon_directory\/$process_name<br \/>\n# $process_id &amp; sleep 1<\/p>\n<p># INSTALL-TIME CONFIGURATION INFORMATION<br \/>\n#<br \/>\n# The following parameters are used when installing a new Postfix version.<br \/>\n#<br \/>\n# sendmail_path: The full pathname of the Postfix sendmail command.<br \/>\n# This is the Sendmail-compatible mail posting interface.<br \/>\n#<br \/>\nsendmail_path = \/usr\/sbin\/sendmail<\/p>\n<p># newaliases_path: The full pathname of the Postfix newaliases command.<br \/>\n# This is the Sendmail-compatible command to build alias databases.<br \/>\n#<br \/>\nnewaliases_path = \/usr\/bin\/newaliases<\/p>\n<p># mailq_path: The full pathname of the Postfix mailq command. This<br \/>\n# is the Sendmail-compatible mail queue listing command.<br \/>\n#<br \/>\nmailq_path = \/usr\/bin\/mailq<\/p>\n<p># setgid_group: The group for mail submission and queue management<br \/>\n# commands. This must be a group name with a numerical group ID that<br \/>\n# is not shared with other accounts, not even with the Postfix account.<br \/>\n#<br \/>\nsetgid_group = postdrop<\/p>\n<p># html_directory: The location of the Postfix HTML documentation.<br \/>\n#<br \/>\nhtml_directory = no<\/p>\n<p># manpage_directory: The location of the Postfix on-line manual pages.<br \/>\n#<br \/>\nmanpage_directory = \/usr\/local\/man<\/p>\n<p># sample_directory: The location of the Postfix sample configuration files.<br \/>\n# This parameter is obsolete as of Postfix 2.1.<br \/>\n#<br \/>\nsample_directory = \/etc\/postfix<\/p>\n<p># readme_directory: The location of the Postfix README files.<br \/>\n#<br \/>\nreadme_directory = no<\/p>\n<p><strong><span style=\"color: #ff0000;\">disable_vrfy_command = yes<\/span><\/strong><\/p>\n<p><strong><span style=\"color: #ff0000;\">smtpd_sasl_auth_enable = yes<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> #broken_sasl_auth_clients = yes<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> smtpd_sasl_type = dovecot<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> smtpd_sasl_path = private\/auth<\/span><\/strong><\/p>\n<p><strong><span style=\"color: #ff0000;\">smtpd_client_restrictions = permit_mynetworks,<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\">\u00a0 check_client_access regexp:\/etc\/postfix\/white-list.txt,<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\">\u00a0 check_client_access regexp:\/etc\/postfix\/tarpit_client,<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\">\u00a0 reject_unknown_client_hostname<\/span><\/strong><\/p>\n<p><strong><span style=\"color: #ff0000;\">smtpd_sender_restrictions = permit_mynetworks,<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\">\u00a0 check_sender_access hash:\/etc\/postfix\/access,<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\">\u00a0 reject_non_fqdn_sender,reject_unknown_sender_domain<\/span><\/strong><\/p>\n<p><strong><span style=\"color: #ff0000;\">smtpd_recipient_restrictions = permit_mynetworks,<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\">\u00a0 permit_sasl_authenticated,reject_unauth_destination<\/span><\/strong><\/p>\n<p><strong><span style=\"color: #ff0000;\"># TLS<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> smtpd_use_tls = yes<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> smtpd_tls_cert_file = \/etc\/pki\/tls\/certs\/mail.pem<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> smtpd_tls_key_file = \/etc\/pki\/tls\/certs\/mail.pem<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> smtpd_tls_loglevel = 1<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> smtpd_tls_session_cache_database = btree:\/var\/lib\/postfix\/smtpd_scache<\/span><\/strong><\/p>\n<p><strong><span style=\"color: #ff0000;\"># postscreen<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> postscreen_access_list = permit_mynetworks,<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\">\u00a0 cidr:\/etc\/postfix\/postscreen_access<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> postscreen_blacklist_action= drop<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> postscreen_greet_action = enforce<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> postscreen_dnsbl_sites = all.rbl.jp=127.0.0.[2;4],<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\">\u00a0 zen.spamhaus.org=127.0.0.[2..7;10;11]<\/span><\/strong><br \/>\n<strong><span style=\"color: #ff0000;\"> postscreen_dnsbl_action = enforce<\/span><\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p># Global Postfix configuration file. This file lists only a subset # of all parameters. For the syntax, and fo &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/kaz.it-n.jp\/?page_id=214\" class=\"more-link\"><span class=\"screen-reader-text\">&#8220;main.cf&#8221; \u306e<\/span>\u7d9a\u304d\u3092\u8aad\u3080<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":205,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"footnotes":""},"class_list":["post-214","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/kaz.it-n.jp\/index.php?rest_route=\/wp\/v2\/pages\/214","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kaz.it-n.jp\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/kaz.it-n.jp\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/kaz.it-n.jp\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kaz.it-n.jp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=214"}],"version-history":[{"count":0,"href":"https:\/\/kaz.it-n.jp\/index.php?rest_route=\/wp\/v2\/pages\/214\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/kaz.it-n.jp\/index.php?rest_route=\/wp\/v2\/pages\/205"}],"wp:attachment":[{"href":"https:\/\/kaz.it-n.jp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=214"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}