summaryrefslogtreecommitdiff
path: root/conf.d/000_local.conf.example
diff options
context:
space:
mode:
Diffstat (limited to 'conf.d/000_local.conf.example')
-rw-r--r--conf.d/000_local.conf.example68
1 files changed, 68 insertions, 0 deletions
diff --git a/conf.d/000_local.conf.example b/conf.d/000_local.conf.example
new file mode 100644
index 0000000..edb41fa
--- /dev/null
+++ b/conf.d/000_local.conf.example
@@ -0,0 +1,68 @@
1######################################################################
2# LOCAL CONFIGURATION #
3# Specifies settings specific for the current host #
4######################################################################
5
6# Specify your host's canonical name here. This should normally be the fully
7# qualified "official" name of your host. If this option is not set, the
8# uname() function is called to obtain the name. In many cases this does
9# the right thing and you need not set anything explicitly.
10
11primary_hostname =
12
13# The next three settings create two lists of domains and one list of hosts.
14# These lists are referred to later in this configuration using the syntax
15# +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
16# are all colon-separated lists:
17
18domainlist local_domains = @
19domainlist relay_to_domains =
20hostlist relay_from_hosts = localhost
21hostlist trusted_relay_hosts =
22# (We rely upon hostname resolution working for localhost, because the default
23# uncommented configuration needs to work in IPv4-only environments.)
24
25# Most straightforward access control requirements can be obtained by
26# appropriate settings of the above options. In more complicated situations,
27# you may need to modify the Access Control Lists (ACLs) which appear later in
28# this file.
29
30# The first setting specifies your local domains, for example:
31#
32# domainlist local_domains = my.first.domain : my.second.domain
33#
34# You can use "@" to mean "the name of the local host", as in the default
35# setting above. This is the name that is specified by primary_hostname,
36# as specified above (or defaulted). If you do not want to do any local
37# deliveries, remove the "@" from the setting above. If you want to accept mail
38# addressed to your host's literal IP address, for example, mail addressed to
39# "user@[192.168.23.44]", you can add "@[]" as an item in the local domains
40# list. You also need to uncomment "allow_domain_literals" below. This is not
41# recommended for today's Internet.
42
43# The second setting specifies domains for which your host is an incoming relay.
44# If you are not doing any relaying, you should leave the list empty. However,
45# if your host is an MX backup or gateway of some kind for some domains, you
46# must set relay_to_domains to match those domains. For example:
47#
48# domainlist relay_to_domains = *.myco.com : my.friend.org
49#
50# This will allow any host to relay through your host to those domains.
51# See the section of the manual entitled "Control of relaying" for more
52# information.
53
54# The third setting specifies hosts that can use your host as an outgoing relay
55# to any other host on the Internet. Such a setting commonly refers to a
56# complete local network as well as the localhost. For example:
57#
58# hostlist relay_from_hosts = <; 127.0.0.1 ; ::1 ; 192.168.0.0/16
59#
60# The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
61# have to include 127.0.0.1 if you want to allow processes on your host to send
62# SMTP mail by using the loopback address. A number of MUAs use this method of
63# sending mail. Often, connections are made to "localhost", which might be ::1
64# on IPv6-enabled hosts. Do not forget CIDR for your IPv6 networks.
65
66# All three of these lists may contain many different kinds of item, including
67# wildcarded names, regular expressions, and file lookups. See the reference
68# manual for details.