]> git.pld-linux.org Git - packages/exim-lite.git/blame - exim4.conf
- EXIM_4 -> HEAD
[packages/exim-lite.git] / exim4.conf
CommitLineData
32f9109c
AM
1######################################################################
2# Runtime configuration file for Exim #
3######################################################################
4
5
6# This is a default configuration file which will operate correctly in
7# uncomplicated installations. Please see the manual for a complete list
8# of all the runtime configuration options that can be included in a
9# configuration file. There are many more than are mentioned here. The
10# manual is in the file doc/spec.txt in the Exim distribution as a plain
11# ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are available
12# from the Exim ftp sites. The manual is also online at the Exim web sites.
13
14
15# This file is divided into several parts, all but the first of which are
16# headed by a line starting with the word "begin". Only those parts that
17# are required need to be present. Blank lines, and lines starting with #
18# are ignored.
19
20
21########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
22# #
23# Whenever you change Exim's configuration file, you *must* remember to #
24# HUP the Exim daemon, because it will not pick up the new configuration #
25# until you do. However, any other Exim processes that are started, for #
26# example, a process started by an MUA in order to send a message, will #
27# see the new configuration as soon as it is in place. #
28# #
29# You do not need to HUP the daemon for changes in auxiliary files that #
30# are referenced from this file. They are read every time they are used. #
31# #
32# It is usually a good idea to test a new configuration for syntactic #
33# correctness before installing it (for example, by running the command #
34# "exim -C /config/file.new -bV"). #
35# #
36########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
37
38
39
40######################################################################
41# MAIN CONFIGURATION SETTINGS #
42######################################################################
43
44# Specify your host's canonical name here. This should normally be the fully
45# qualified "official" name of your host. If this option is not set, the
46# uname() function is called to obtain the name. In many cases this does
47# the right thing and you need not set anything explicitly.
48
49# primary_hostname =
50
51
52# The next three settings create two lists of domains and one list of hosts.
53# These lists are referred to later in this configuration using the syntax
54# +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
55# are all colon-separated lists:
56
57domainlist local_domains = @
58domainlist relay_to_domains =
59hostlist relay_from_hosts = 127.0.0.1
60
61# Most straightforward access control requirements can be obtained by
62# appropriate settings of the above options. In more complicated situations, you
63# may need to modify the Access Control List (ACL) which appears later in this
64# file.
65
66# The first setting specifies your local domains, for example:
67#
68# domainlist local_domains = my.first.domain : my.second.domain
69#
70# You can use "@" to mean "the name of the local host", as in the default
71# setting above. This is the name that is specified by primary_hostname,
72# as specified above (or defaulted). If you do not want to do any local
73# deliveries, remove the "@" rom the setting above. If you want to accept mail
74# addressed to your host's literal IP address, for example, mail addressed to
75# "user@[192.168.23.44]", you can add "@[]" as an item in the local domains
76# list. You also need to uncomment "allow_domain_literals" below. This is not
77# recommended for today's Internet.
78
79# The second setting specifies domains for which your host is an incoming relay.
80# If you are not doing any relaying, you should leave the list empty. However,
81# if your host is an MX backup or gateway of some kind for some domains, you
82# must set relay_to_domains to match those domains. For example:
83#
84# domainlist relay_to_domains = *.myco.com : my.friend.org
85#
86# This will allow any host to relay through your host to those domains.
87# See the section of the manual entitled "Control of relaying" for more
88# information.
89
90# The third setting specifies hosts that can use your host as an outgoing relay
91# to any other host on the Internet. Such a setting commonly refers to a
92# complete local network as well as the localhost. For example:
93#
94# hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16
95#
96# The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
97# have to include 127.0.0.1 if you want to allow processes on your host to send
98# SMTP mail by using the loopback address. A number of MUAs use this method of
99# sending mail.
100
101
102# All three of these lists may contain many different kinds of item, including
103# wildcarded names, regular expressions, and file lookups. See the reference
104# manual for details. The lists above are used in the access control list for
105# incoming messages. The name of this ACL is defined here:
106
107acl_smtp_rcpt = acl_check_rcpt
108
109# You should not change that setting until you understand how ACLs work.
110
111
112# Specify the domain you want to be added to all unqualified addresses
113# here. An unqualified address is one that does not contain an "@" character
114# followed by a domain. For example, "caesar@rome.ex" is a fully qualified
115# address, but the string "caesar" (i.e. just a login name) is an unqualified
116# email address. Unqualified addresses are accepted only from local callers by
117# default. See the recipient_unqualified_hosts option if you want to permit
118# unqualified addresses from remote sources. If this option is not set, the
119# primary_hostname value is used for qualification.
120
121# qualify_domain =
122
123
124# If you want unqualified recipient addresses to be qualified with a different
125# domain to unqualified sender addresses, specify the recipient domain here.
126# If this option is not set, the qualify_domain value is used.
127
128# qualify_recipient =
129
130
131# The following line must be uncommented if you want Exim to recognize
132# addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
133# (an IP address) instead of a named domain. The RFCs still require this form,
134# but it makes little sense to permit mail to be sent to specific hosts by
135# their IP address in the modern Internet. This ancient format has been used
136# by those seeking to abuse hosts by using them for unwanted relaying. If you
137# really do want to support domain literals, uncomment the following line, and
138# see also the "domain_literal" router below.
139
140# allow_domain_literals
141
142
143# No deliveries will ever be run under the uids of these users (a colon-
144# separated list). An attempt to do so causes a panic error to be logged, and
145# the delivery to be deferred. This is a paranoic safety catch. Note that the
146# default setting means you cannot deliver mail addressed to root as if it
147# were a normal user. This isn't usually a problem, as most sites have an alias
148# for root that redirects such mail to a human administrator.
149
150never_users = root
151
152
153# The setting below causes Exim to do a reverse DNS lookup on all incoming
154# IP calls, in order to get the true host name. If you feel this is too
155# expensive, you can specify the networks for which a lookup is done, or
156# remove the setting entirely.
157
158host_lookup = *
159
160
161# The settings below, which are actually the same as the defaults in the
162# code, cause Exim to make RFC 1413 (ident) callbacks for all incoming SMTP
163# calls. You can limit the hosts to which these calls are made, and/or change
164# the timeout that is used. If you set the timeout to zero, all RFC 1413 calls
165# are disabled. RFC 1413 calls are cheap and can provide useful information
166# for tracing problem messages, but some hosts and firewalls have problems
167# with them. This can result in a timeout instead of an immediate refused
168# connection, leading to delays on starting up an SMTP session.
169
170rfc1413_hosts = *
171rfc1413_query_timeout = 30s
172
173
174# By default, Exim expects all envelope addresses to be fully qualified, that
175# is, they must contain both a local part and a domain. If you want to accept
176# unqualified addresses (just a local part) from certain hosts, you can specify
177# these hosts by setting one or both of
178#
179# sender_unqualified_hosts =
180# recipient_unqualified_hosts =
181#
182# to control sender and recipient addresses, respectively. When this is done,
183# unqualified addresses are qualified using the settings of qualify_domain
184# and/or qualify_recipient (see above).
185
186
187# If you want Exim to support the "percent hack" for certain domains,
188# uncomment the following line and provide a list of domains. The "percent
189# hack" is the feature by which mail addressed to x%y@z (where z is one of
190# the domains listed) is locally rerouted to x@y and sent on. If z is not one
191# of the "percent hack" domains, x%y is treated as an ordinary local part. This
192# hack is rarely needed nowadays; you should not enable it unless you are sure
193# that you really need it.
194#
195# percent_hack_domains =
196#
197# As well as setting this option you will also need to remove the test
198# for local parts containing % in the ACL definition below.
199
200
201# When Exim can neither deliver a message nor return it to sender, it "freezes"
202# the delivery error message (aka "bounce message"). There are also other
203# circumstances in which messages get frozen. They will stay on the queue for
204# ever unless one of the following options is set.
205
206# This option unfreezes frozen bounce messages after two days, tries
207# once more to deliver them, and ignores any delivery failures.
208
209ignore_bounce_errors_after = 2d
210
211# This option cancels (removes) frozen messages that are older than a week.
212
213timeout_frozen_after = 7d
214
215
216
217######################################################################
218# ACL CONFIGURATION #
219# Specifies access control lists for incoming SMTP mail #
220######################################################################
221
222begin acl
223
224# This access control list is used for every RCPT command in an incoming
225# SMTP message. The tests are run in order until the address is either
226# accepted or denied.
227
228acl_check_rcpt:
229
230 # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
231 # testing for an empty sending host field.
232
233 accept hosts = :
234
235 # Deny if the local part contains @ or % or / or | or !. These are rarely
236 # found in genuine local parts, but are often tried by people looking to
237 # circumvent relaying restrictions.
238
239 deny local_parts = ^.*[@%!/|]
240
241 # Accept mail to postmaster in any local domain, regardless of the source,
242 # and without verifying the sender.
243
244 accept local_parts = postmaster
245 domains = +local_domains
246
247 # Deny unless the sender address can be verified.
248
249 require verify = sender
250
251 #############################################################################
252 # There are no checks on DNS "black" lists because the domains that contain
253 # these lists are changing all the time. However, here are two examples of
254 # how you could get Exim to perform a DNS black list lookup at this point.
255 # The first one denies, while the second just warns.
256 #
257 # deny message = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
258 # dnslists = black.list.example
259 #
260 # warn message = X-Warning: $sender_host_address is in a black list at $dnslist_domain
261 # log_message = found in $dnslist_domain
262 # dnslists = black.list.example
263 #############################################################################
264
265 # Accept if the address is in a local domain, but only if the recipient can
266 # be verified. Otherwise deny. The "endpass" line is the border between
267 # passing on to the next ACL statement (if tests above it fail) or denying
268 # access (if tests below it fail).
269
270 accept domains = +local_domains
271 endpass
272 message = unknown user
273 verify = recipient
274
275 # Accept if the address is in a domain for which we are relaying, but again,
276 # only if the recipient can be verified.
277
278 accept domains = +relay_to_domains
279 endpass
280 message = unrouteable address
281 verify = recipient
282
283 # If control reaches this point, the domain is neither in +local_domains
284 # nor in +relay_to_domains.
285
286 # Accept if the message comes from one of the hosts for which we are an
287 # outgoing relay. Recipient verification is omitted here, because in many
288 # cases the clients are dumb MUAs that don't cope well with SMTP error
289 # responses. If you are actually relaying out from MTAs, you should probably
290 # add recipient verification here.
291
292 accept hosts = +relay_from_hosts
293
294 # Accept if the message arrived over an authenticated connection, from
295 # any host. Again, these messages are usually from MUAs, so recipient
296 # verification is omitted.
297
298 accept authenticated = *
299
300 # Reaching the end of the ACL causes a "deny", but we might as well give
301 # an explicit message.
302
303 deny message = relay not permitted
304
305
306
307######################################################################
308# ROUTERS CONFIGURATION #
309# Specifies how addresses are handled #
310######################################################################
311# THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
312# An address is passed to each router in turn until it is accepted. #
313######################################################################
314
315begin routers
316
317# This router routes to remote hosts over SMTP by explicit IP address,
318# when an email address is given in "domain literal" form, for example,
319# <user@[192.168.35.64]>. The RFCs require this facility. However, it is
320# little-known these days, and has been exploited by evil people seeking
321# to abuse SMTP relays. Consequently it is commented out in the default
322# configuration. If you uncomment this router, you also need to uncomment
323# allow_domain_literals above, so that Exim can recognize the syntax of
324# domain literal addresses.
325
326# domain_literal:
327# driver = ipliteral
328# transport = remote_smtp
329
330
331# This router routes addresses that are not in local domains by doing a DNS
332# lookup on the domain name. Any domain that resolves to a loopback interface
333# address (127.0.0.0/8) is treated as if it had no DNS entry. If the DNS
334# lookup fails, no further routers are tried because of the no_more setting,
335# and consequently the address is unrouteable.
336
337dnslookup:
338 driver = dnslookup
339 domains = ! +local_domains
340 transport = remote_smtp
341 ignore_target_hosts = 127.0.0.0/8
342 no_more
343
344
345# The remaining routers handle addresses in the local domain(s).
346
347
348# This router handles aliasing using a traditional /etc/aliases file.
349#
350##### NB You must ensure that /etc/aliases exists. It used to be the case
351##### NB that every Unix had that file, because it was the Sendmail default.
352##### NB These days, there are systems that don't have it. Your aliases
353##### NB file should at least contain an alias for "postmaster".
354#
355# If any of your aliases expand to pipes or files, you will need to set
356# up a user and a group for these deliveries to run under. You can do
357# this by uncommenting the "user" option below (changing the user name
358# as appropriate) and adding a "group" option if necessary. Alternatively, you
359# can specify "user" on the transports that are used. Note that the transports
360# listed below are the same as are used for .forward files; you might want
361# to set up different ones for pipe and file deliveries from aliases.
362
363system_aliases:
364 driver = redirect
365 allow_fail
366 allow_defer
367 data = ${lookup{$local_part}lsearch{/etc/aliases}}
368# user = exim
369 file_transport = address_file
370 pipe_transport = address_pipe
371
372
373# This router handles forwarding using traditional .forward files in users'
374# home directories. If you want it also to allow mail filtering when a forward
375# file starts with the string "# Exim filter", uncomment the "allow_filter"
376# option.
377
378# The no_verify setting means that this router is skipped when Exim is
379# verifying addresses. Similarly, no_expn means that this router is skipped if
380# Exim is processing an EXPN command.
381
382# The check_ancestor option means that if the forward file generates an
383# address that is an ancestor of the current one, the current one gets
384# passed on instead. This covers the case where A is aliased to B and B
385# has a .forward file pointing to A.
386
387# The three transports specified at the end are those that are used when
388# forwarding generates a direct delivery to a file, or to a pipe, or sets
389# up an auto-reply, respectively.
390
391userforward:
392 driver = redirect
393 check_local_user
394 file = $home/.forward
395 no_verify
396 no_expn
397 check_ancestor
398# allow_filter
399 file_transport = address_file
400 pipe_transport = address_pipe
401 reply_transport = address_reply
402
403
404# This router matches local user mailboxes.
405
406localuser:
407 driver = accept
408 check_local_user
409 transport = local_delivery
410
411
412
413######################################################################
414# TRANSPORTS CONFIGURATION #
415######################################################################
416# ORDER DOES NOT MATTER #
417# Only one appropriate transport is called for each delivery. #
418######################################################################
419
420# A transport is used only when referenced from a router that successfully
421# handles an address.
422
423begin transports
424
425
426# This transport is used for delivering messages over SMTP connections.
427
428remote_smtp:
429 driver = smtp
430
431
432# This transport is used for local delivery to user mailboxes in traditional
433# BSD mailbox format. By default it will be run under the uid and gid of the
434# local user, and requires the sticky bit to be set on the /var/mail directory.
435# Some systems use the alternative approach of running mail deliveries under a
436# particular group instead of using the sticky bit. The commented options below
437# show how this can be done.
438
439local_delivery:
440 driver = appendfile
441 file = /var/mail/$local_part
442 delivery_date_add
443 envelope_to_add
444 return_path_add
445# group = mail
446# mode = 0660
447
448
449# This transport is used for handling pipe deliveries generated by alias or
450# .forward files. If the pipe generates any standard output, it is returned
451# to the sender of the message as a delivery error. Set return_fail_output
452# instead of return_output if you want this to happen only when the pipe fails
453# to complete normally. You can set different transports for aliases and
454# forwards if you want to - see the references to address_pipe in the routers
455# section above.
456
457address_pipe:
458 driver = pipe
459 return_output
460
461
462# This transport is used for handling deliveries directly to files that are
463# generated by aliasing or forwarding.
464
465address_file:
466 driver = appendfile
467 delivery_date_add
468 envelope_to_add
469 return_path_add
470
471
472# This transport is used for handling autoreplies generated by the filtering
473# option of the userforward router.
474
475address_reply:
476 driver = autoreply
477
478
479
480######################################################################
481# RETRY CONFIGURATION #
482######################################################################
483
484begin retry
485
486# This single retry rule applies to all domains and all errors. It specifies
487# retries every 15 minutes for 2 hours, then increasing retry intervals,
488# starting at 1 hour and increasing each time by a factor of 1.5, up to 16
489# hours, then retries every 6 hours until 4 days have passed since the first
490# failed delivery.
491
492# Domain Error Retries
493# ------ ----- -------
494
495* * F,2h,15m; G,16h,1h,1.5; F,4d,6h
496
497
498
499######################################################################
500# REWRITE CONFIGURATION #
501######################################################################
502
503# There are no rewriting specifications in this default configuration file.
504
505begin rewrite
506
507
508
509######################################################################
510# AUTHENTICATION CONFIGURATION #
511######################################################################
512
513# There are no authenticator specifications in this default configuration file.
514
515begin authenticators
516
517
518# End of Exim configuration file
This page took 0.166029 seconds and 4 git commands to generate.