Reduce rfc1413_query_timeout default from 30s to 5s.
[exim.git] / src / src / configure.default
CommitLineData
8def5aaf 1# $Cambridge: exim/src/src/configure.default,v 1.7 2006/02/20 16:31:49 ph10 Exp $
059ec3d9
PH
2
3######################################################################
4# Runtime configuration file for Exim #
5######################################################################
6
7
8# This is a default configuration file which will operate correctly in
9# uncomplicated installations. Please see the manual for a complete list
10# of all the runtime configuration options that can be included in a
11# configuration file. There are many more than are mentioned here. The
12# manual is in the file doc/spec.txt in the Exim distribution as a plain
13# ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are available
14# from the Exim ftp sites. The manual is also online at the Exim web sites.
15
16
17# This file is divided into several parts, all but the first of which are
18# headed by a line starting with the word "begin". Only those parts that
19# are required need to be present. Blank lines, and lines starting with #
20# are ignored.
21
22
23########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
24# #
25# Whenever you change Exim's configuration file, you *must* remember to #
26# HUP the Exim daemon, because it will not pick up the new configuration #
27# until you do. However, any other Exim processes that are started, for #
28# example, a process started by an MUA in order to send a message, will #
29# see the new configuration as soon as it is in place. #
30# #
31# You do not need to HUP the daemon for changes in auxiliary files that #
32# are referenced from this file. They are read every time they are used. #
33# #
34# It is usually a good idea to test a new configuration for syntactic #
35# correctness before installing it (for example, by running the command #
36# "exim -C /config/file.new -bV"). #
37# #
38########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
39
40
41
42######################################################################
43# MAIN CONFIGURATION SETTINGS #
44######################################################################
45
46# Specify your host's canonical name here. This should normally be the fully
47# qualified "official" name of your host. If this option is not set, the
48# uname() function is called to obtain the name. In many cases this does
49# the right thing and you need not set anything explicitly.
50
51# primary_hostname =
52
53
54# The next three settings create two lists of domains and one list of hosts.
55# These lists are referred to later in this configuration using the syntax
56# +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
57# are all colon-separated lists:
58
59domainlist local_domains = @
60domainlist relay_to_domains =
61hostlist relay_from_hosts = 127.0.0.1
62
63# Most straightforward access control requirements can be obtained by
53394084
PH
64# appropriate settings of the above options. In more complicated situations,
65# you may need to modify the Access Control List (ACL) which appears later in
66# this file.
059ec3d9
PH
67
68# The first setting specifies your local domains, for example:
69#
70# domainlist local_domains = my.first.domain : my.second.domain
71#
72# You can use "@" to mean "the name of the local host", as in the default
73# setting above. This is the name that is specified by primary_hostname,
74# as specified above (or defaulted). If you do not want to do any local
75# deliveries, remove the "@" from the setting above. If you want to accept mail
76# addressed to your host's literal IP address, for example, mail addressed to
77# "user@[192.168.23.44]", you can add "@[]" as an item in the local domains
78# list. You also need to uncomment "allow_domain_literals" below. This is not
79# recommended for today's Internet.
80
81# The second setting specifies domains for which your host is an incoming relay.
82# If you are not doing any relaying, you should leave the list empty. However,
83# if your host is an MX backup or gateway of some kind for some domains, you
84# must set relay_to_domains to match those domains. For example:
85#
86# domainlist relay_to_domains = *.myco.com : my.friend.org
87#
88# This will allow any host to relay through your host to those domains.
89# See the section of the manual entitled "Control of relaying" for more
90# information.
91
92# The third setting specifies hosts that can use your host as an outgoing relay
93# to any other host on the Internet. Such a setting commonly refers to a
94# complete local network as well as the localhost. For example:
95#
96# hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16
97#
98# The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
99# have to include 127.0.0.1 if you want to allow processes on your host to send
100# SMTP mail by using the loopback address. A number of MUAs use this method of
101# sending mail.
102
059ec3d9
PH
103# All three of these lists may contain many different kinds of item, including
104# wildcarded names, regular expressions, and file lookups. See the reference
74e0617f
PH
105# manual for details. The lists above are used in the access control lists for
106# checking incoming messages. The names of these ACLs are defined here:
059ec3d9
PH
107
108acl_smtp_rcpt = acl_check_rcpt
74e0617f
PH
109acl_smtp_data = acl_check_data
110
111# You should not change those settings until you understand how ACLs work.
112
113
114# If you are running a version of Exim that was compiled with the content-
115# scanning extension, you can cause incoming messages to be automatically
116# scanned for viruses. You have to modify the configuration in two places to
117# set this up. The first of them is here, where you define the interface to
118# your scanner. This example is typical for ClamAV; see the manual for details
119# of what to set for other virus scanners. The second modification is in the
120# acl_check_data access control list (see below).
059ec3d9 121
74e0617f
PH
122# av_scanner = clamd:/tmp/clamd
123
124
125# For spam scanning, there is a similar option that defines the interface to
126# SpamAssassin. You do not need to set this if you are using the default, which
127# is shown in this commented example. As for virus scanning, you must also
128# modify the acl_check_data access control list to enable spam scanning.
129
130# spamd_address = 127.0.0.1 783
059ec3d9
PH
131
132
133# Specify the domain you want to be added to all unqualified addresses
134# here. An unqualified address is one that does not contain an "@" character
135# followed by a domain. For example, "caesar@rome.example" is a fully qualified
136# address, but the string "caesar" (i.e. just a login name) is an unqualified
137# email address. Unqualified addresses are accepted only from local callers by
138# default. See the recipient_unqualified_hosts option if you want to permit
139# unqualified addresses from remote sources. If this option is not set, the
140# primary_hostname value is used for qualification.
141
142# qualify_domain =
143
144
145# If you want unqualified recipient addresses to be qualified with a different
146# domain to unqualified sender addresses, specify the recipient domain here.
147# If this option is not set, the qualify_domain value is used.
148
149# qualify_recipient =
150
151
152# The following line must be uncommented if you want Exim to recognize
153# addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
154# (an IP address) instead of a named domain. The RFCs still require this form,
155# but it makes little sense to permit mail to be sent to specific hosts by
156# their IP address in the modern Internet. This ancient format has been used
157# by those seeking to abuse hosts by using them for unwanted relaying. If you
158# really do want to support domain literals, uncomment the following line, and
159# see also the "domain_literal" router below.
160
161# allow_domain_literals
162
163
164# No deliveries will ever be run under the uids of these users (a colon-
165# separated list). An attempt to do so causes a panic error to be logged, and
166# the delivery to be deferred. This is a paranoic safety catch. There is an
167# even stronger safety catch in the form of the FIXED_NEVER_USERS setting
168# in the configuration for building Exim. The list of users that it specifies
169# is built into the binary, and cannot be changed. The option below just adds
170# additional users to the list. The default for FIXED_NEVER_USERS is "root",
171# but just to be absolutely sure, the default here is also "root".
172
173# Note that the default setting means you cannot deliver mail addressed to root
174# as if it were a normal user. This isn't usually a problem, as most sites have
175# an alias for root that redirects such mail to a human administrator.
176
177never_users = root
178
179
180# The setting below causes Exim to do a reverse DNS lookup on all incoming
181# IP calls, in order to get the true host name. If you feel this is too
182# expensive, you can specify the networks for which a lookup is done, or
183# remove the setting entirely.
184
185host_lookup = *
186
187
188# The settings below, which are actually the same as the defaults in the
189# code, cause Exim to make RFC 1413 (ident) callbacks for all incoming SMTP
190# calls. You can limit the hosts to which these calls are made, and/or change
191# the timeout that is used. If you set the timeout to zero, all RFC 1413 calls
192# are disabled. RFC 1413 calls are cheap and can provide useful information
193# for tracing problem messages, but some hosts and firewalls have problems
194# with them. This can result in a timeout instead of an immediate refused
8def5aaf
PH
195# connection, leading to delays on starting up SMTP sessions. (The default was
196# reduced from 30s to 5s for release 4.61.)
059ec3d9
PH
197
198rfc1413_hosts = *
8def5aaf 199rfc1413_query_timeout = 5s
059ec3d9
PH
200
201
202# By default, Exim expects all envelope addresses to be fully qualified, that
203# is, they must contain both a local part and a domain. If you want to accept
204# unqualified addresses (just a local part) from certain hosts, you can specify
205# these hosts by setting one or both of
206#
207# sender_unqualified_hosts =
208# recipient_unqualified_hosts =
209#
210# to control sender and recipient addresses, respectively. When this is done,
211# unqualified addresses are qualified using the settings of qualify_domain
212# and/or qualify_recipient (see above).
213
214
215# If you want Exim to support the "percent hack" for certain domains,
216# uncomment the following line and provide a list of domains. The "percent
217# hack" is the feature by which mail addressed to x%y@z (where z is one of
218# the domains listed) is locally rerouted to x@y and sent on. If z is not one
219# of the "percent hack" domains, x%y is treated as an ordinary local part. This
220# hack is rarely needed nowadays; you should not enable it unless you are sure
221# that you really need it.
222#
223# percent_hack_domains =
224#
225# As well as setting this option you will also need to remove the test
226# for local parts containing % in the ACL definition below.
227
228
229# When Exim can neither deliver a message nor return it to sender, it "freezes"
230# the delivery error message (aka "bounce message"). There are also other
231# circumstances in which messages get frozen. They will stay on the queue for
232# ever unless one of the following options is set.
233
234# This option unfreezes frozen bounce messages after two days, tries
235# once more to deliver them, and ignores any delivery failures.
236
237ignore_bounce_errors_after = 2d
238
239# This option cancels (removes) frozen messages that are older than a week.
240
241timeout_frozen_after = 7d
242
243
244
245######################################################################
246# ACL CONFIGURATION #
247# Specifies access control lists for incoming SMTP mail #
248######################################################################
249
250begin acl
251
252# This access control list is used for every RCPT command in an incoming
253# SMTP message. The tests are run in order until the address is either
254# accepted or denied.
255
256acl_check_rcpt:
257
258 # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
259 # testing for an empty sending host field.
260
261 accept hosts = :
262
263 #############################################################################
264 # The following section of the ACL is concerned with local parts that contain
265 # @ or % or ! or / or | or dots in unusual places.
266 #
267 # The characters other than dots are rarely found in genuine local parts, but
268 # are often tried by people looking to circumvent relaying restrictions.
269 # Therefore, although they are valid in local parts, these rules lock them
270 # out, as a precaution.
271 #
272 # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
273 # allows them because they have been encountered. (Consider local parts
274 # constructed as "firstinitial.secondinitial.familyname" when applied to
275 # someone like me, who has no second initial.) However, a local part starting
276 # with a dot or containing /../ can cause trouble if it is used as part of a
277 # file name (e.g. for a mailing list). This is also true for local parts that
278 # contain slashes. A pipe symbol can also be troublesome if the local part is
279 # incorporated unthinkingly into a shell command line.
280 #
281 # Two different rules are used. The first one is stricter, and is applied to
282 # messages that are addressed to one of the local domains handled by this
53394084
PH
283 # host. The line "domains = +local_domains" restricts it to domains that are
284 # defined by the "domainlist local_domains" setting above. The rule blocks
285 # local parts that begin with a dot or contain @ % ! / or |. If you have
286 # local accounts that include these characters, you will have to modify this
287 # rule.
059ec3d9
PH
288
289 deny message = Restricted characters in address
290 domains = +local_domains
291 local_parts = ^[.] : ^.*[@%!/|]
292
53394084
PH
293 # The second rule applies to all other domains, and is less strict. The line
294 # "domains = !+local_domains" restricts it to domains that are NOT defined by
295 # the "domainlist local_domains" setting above. The exclamation mark is a
296 # negating operator. This rule allows your own users to send outgoing
297 # messages to sites that use slashes and vertical bars in their local parts.
298 # It blocks local parts that begin with a dot, slash, or vertical bar, but
299 # allows these characters within the local part. However, the sequence /../
300 # is barred. The use of @ % and ! is blocked, as before. The motivation here
301 # is to prevent your users (or your users' viruses) from mounting certain
302 # kinds of attack on remote sites.
059ec3d9
PH
303
304 deny message = Restricted characters in address
305 domains = !+local_domains
306 local_parts = ^[./|] : ^.*[@%!] : ^.*/\\.\\./
307 #############################################################################
308
309 # Accept mail to postmaster in any local domain, regardless of the source,
310 # and without verifying the sender.
311
312 accept local_parts = postmaster
313 domains = +local_domains
314
315 # Deny unless the sender address can be verified.
316
317 require verify = sender
318
5de37277 319 # Accept if the message comes from one of the hosts for which we are an
cc38ddbf
PH
320 # outgoing relay. It is assumed that such hosts are most likely to be MUAs,
321 # so we set control=submission to make Exim treat the message as a
322 # submission. It will fix up various errors in the message, for example, the
323 # lack of a Date: header line. If you are actually relaying out out from
324 # MTAs, you may want to disable this. If you are handling both relaying from
325 # MTAs and submissions from MUAs you should probably split them into two
326 # lists, and handle them differently.
327
328 # Recipient verification is omitted here, because in many cases the clients
329 # are dumb MUAs that don't cope well with SMTP error responses. If you are
330 # actually relaying out from MTAs, you should probably add recipient
331 # verification here.
332
333 # Note that, by putting this test before any DNS black list checks, you will
334 # always accept from these hosts, even if they end up on a black list. The
335 # assumption is that they are your friends, and if they get onto a black
336 # list, it is a mistake.
5de37277
PH
337
338 accept hosts = +relay_from_hosts
cc38ddbf 339 control = submission
5de37277
PH
340
341 # Accept if the message arrived over an authenticated connection, from
342 # any host. Again, these messages are usually from MUAs, so recipient
cc38ddbf
PH
343 # verification is omitted, and submission mode is set. And again, we do this
344 # check before any black list tests.
5de37277
PH
345
346 accept authenticated = *
cc38ddbf 347 control = submission
5de37277 348
059ec3d9 349 #############################################################################
5de37277
PH
350 # There are no default checks on DNS black lists because the domains that
351 # contain these lists are changing all the time. However, here are two
352 # examples of how you can get Exim to perform a DNS black list lookup at this
353 # point. The first one denies, whereas the second just warns.
059ec3d9
PH
354 #
355 # deny message = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
356 # dnslists = black.list.example
357 #
358 # warn message = X-Warning: $sender_host_address is in a black list at $dnslist_domain
359 # log_message = found in $dnslist_domain
360 # dnslists = black.list.example
361 #############################################################################
362
a4e3111f
PH
363 #############################################################################
364 # This check is commented out because it is recognized that not every
365 # sysadmin will want to do it. If you enable it, the check performs
366 # Client SMTP Authorization (csa) checks on the sending host. These checks
367 # do DNS lookups for SRV records. The CSA proposal is currently (May 2005)
368 # an Internet draft. You can, of course, add additional conditions to this
369 # ACL statement to restrict the CSA checks to certain hosts only.
370 #
371 # require verify = csa
372 #############################################################################
373
059ec3d9
PH
374 # Accept if the address is in a local domain, but only if the recipient can
375 # be verified. Otherwise deny. The "endpass" line is the border between
376 # passing on to the next ACL statement (if tests above it fail) or denying
377 # access (if tests below it fail).
378
379 accept domains = +local_domains
380 endpass
381 verify = recipient
382
5de37277
PH
383 # Accept if the address is in a domain for which we are an incoming relay,
384 # but again, only if the recipient can be verified.
059ec3d9
PH
385
386 accept domains = +relay_to_domains
387 endpass
388 verify = recipient
389
059ec3d9
PH
390 # Reaching the end of the ACL causes a "deny", but we might as well give
391 # an explicit message.
392
393 deny message = relay not permitted
394
395
74e0617f
PH
396# This ACL is used after the contents of a message have been received. This
397# is the ACL in which you can test a message's headers or body, and in
398# particular, this is where you can invoke external virus or spam scanners.
399# Some suggested ways of configuring these tests are shown below, commented
400# out. Without any tests, this ACL accepts all messages. If you want to use
401# such tests, you must ensure that Exim is compiled with the content-scanning
402# extension (WITH_CONTENT_SCAN=yes in Local/Makefile).
403
404acl_check_data:
405
406 # Deny if the message contains a virus. Before enabling this check, you
407 # must install a virus scanner and set the av_scanner option above.
408 #
409 # deny malware = *
410 # message = This message contains a virus ($malware_name).
411
412 # Add headers to a message if it is judged to be spam. Before enabling this,
413 # you must install SpamAssassin. You may also need to set the spamd_address
414 # option above.
415 #
416 # warn spam = nobody
417 # message = X-Spam_score: $spam_score\n\
418 # X-Spam_score_int: $spam_score_int\n\
419 # X-Spam_bar: $spam_bar\n\
420 # X-Spam_report: $spam_report
421
422 # Accept the message.
423
424 accept
425
426
059ec3d9
PH
427
428######################################################################
429# ROUTERS CONFIGURATION #
430# Specifies how addresses are handled #
431######################################################################
432# THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
433# An address is passed to each router in turn until it is accepted. #
434######################################################################
435
436begin routers
437
438# This router routes to remote hosts over SMTP by explicit IP address,
439# when an email address is given in "domain literal" form, for example,
440# <user@[192.168.35.64]>. The RFCs require this facility. However, it is
441# little-known these days, and has been exploited by evil people seeking
442# to abuse SMTP relays. Consequently it is commented out in the default
443# configuration. If you uncomment this router, you also need to uncomment
444# allow_domain_literals above, so that Exim can recognize the syntax of
445# domain literal addresses.
446
447# domain_literal:
448# driver = ipliteral
449# domains = ! +local_domains
450# transport = remote_smtp
451
452
453# This router routes addresses that are not in local domains by doing a DNS
53394084
PH
454# lookup on the domain name. The exclamation mark that appears in "domains = !
455# +local_domains" is a negating operator, that is, it can be read as "not". The
456# recipient's domain must not be one of those defined by "domainlist
457# local_domains" above for this router to be used.
458#
459# If the router is used, any domain that resolves to 0.0.0.0 or to a loopback
460# interface address (127.0.0.0/8) is treated as if it had no DNS entry. Note
461# that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated as the
462# local host inside the network stack. It is not 0.0.0.0/0, the default route.
463# If the DNS lookup fails, no further routers are tried because of the no_more
464# setting, and consequently the address is unrouteable.
059ec3d9
PH
465
466dnslookup:
467 driver = dnslookup
468 domains = ! +local_domains
469 transport = remote_smtp
470 ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
471 no_more
472
473
53394084
PH
474# The remaining routers handle addresses in the local domain(s), that is those
475# domains that are defined by "domainlist local_domains" above.
059ec3d9
PH
476
477
478# This router handles aliasing using a linearly searched alias file with the
479# name SYSTEM_ALIASES_FILE. When this configuration is installed automatically,
480# the name gets inserted into this file from whatever is set in Exim's
481# build-time configuration. The default path is the traditional /etc/aliases.
482# If you install this configuration by hand, you need to specify the correct
483# path in the "data" setting below.
484#
485##### NB You must ensure that the alias file exists. It used to be the case
486##### NB that every Unix had that file, because it was the Sendmail default.
487##### NB These days, there are systems that don't have it. Your aliases
488##### NB file should at least contain an alias for "postmaster".
489#
490# If any of your aliases expand to pipes or files, you will need to set
491# up a user and a group for these deliveries to run under. You can do
492# this by uncommenting the "user" option below (changing the user name
493# as appropriate) and adding a "group" option if necessary. Alternatively, you
494# can specify "user" on the transports that are used. Note that the transports
495# listed below are the same as are used for .forward files; you might want
496# to set up different ones for pipe and file deliveries from aliases.
497
498system_aliases:
499 driver = redirect
500 allow_fail
501 allow_defer
502 data = ${lookup{$local_part}lsearch{SYSTEM_ALIASES_FILE}}
503# user = exim
504 file_transport = address_file
505 pipe_transport = address_pipe
506
507
508# This router handles forwarding using traditional .forward files in users'
509# home directories. If you want it also to allow mail filtering when a forward
510# file starts with the string "# Exim filter" or "# Sieve filter", uncomment
511# the "allow_filter" option.
512
513# If you want this router to treat local parts with suffixes introduced by "-"
514# or "+" characters as if the suffixes did not exist, uncomment the two local_
515# part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
516# in the same way as xxxx@your.domain by this router. You probably want to make
517# the same change to the localuser router.
518
519# The no_verify setting means that this router is skipped when Exim is
520# verifying addresses. Similarly, no_expn means that this router is skipped if
521# Exim is processing an EXPN command.
522
523# The check_ancestor option means that if the forward file generates an
524# address that is an ancestor of the current one, the current one gets
525# passed on instead. This covers the case where A is aliased to B and B
526# has a .forward file pointing to A.
527
528# The three transports specified at the end are those that are used when
529# forwarding generates a direct delivery to a file, or to a pipe, or sets
530# up an auto-reply, respectively.
531
532userforward:
533 driver = redirect
534 check_local_user
535# local_part_suffix = +* : -*
536# local_part_suffix_optional
537 file = $home/.forward
538# allow_filter
539 no_verify
540 no_expn
541 check_ancestor
542 file_transport = address_file
543 pipe_transport = address_pipe
544 reply_transport = address_reply
545
546
547# This router matches local user mailboxes. If the router fails, the error
548# message is "Unknown user".
549
550# If you want this router to treat local parts with suffixes introduced by "-"
551# or "+" characters as if the suffixes did not exist, uncomment the two local_
552# part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
553# in the same way as xxxx@your.domain by this router.
554
555localuser:
556 driver = accept
557 check_local_user
558# local_part_suffix = +* : -*
559# local_part_suffix_optional
560 transport = local_delivery
561 cannot_route_message = Unknown user
562
563
564
565######################################################################
566# TRANSPORTS CONFIGURATION #
567######################################################################
568# ORDER DOES NOT MATTER #
569# Only one appropriate transport is called for each delivery. #
570######################################################################
571
572# A transport is used only when referenced from a router that successfully
573# handles an address.
574
575begin transports
576
577
578# This transport is used for delivering messages over SMTP connections.
579
580remote_smtp:
581 driver = smtp
582
583
584# This transport is used for local delivery to user mailboxes in traditional
585# BSD mailbox format. By default it will be run under the uid and gid of the
586# local user, and requires the sticky bit to be set on the /var/mail directory.
587# Some systems use the alternative approach of running mail deliveries under a
588# particular group instead of using the sticky bit. The commented options below
589# show how this can be done.
590
591local_delivery:
592 driver = appendfile
593 file = /var/mail/$local_part
594 delivery_date_add
595 envelope_to_add
596 return_path_add
597# group = mail
598# mode = 0660
599
600
601# This transport is used for handling pipe deliveries generated by alias or
602# .forward files. If the pipe generates any standard output, it is returned
603# to the sender of the message as a delivery error. Set return_fail_output
604# instead of return_output if you want this to happen only when the pipe fails
605# to complete normally. You can set different transports for aliases and
606# forwards if you want to - see the references to address_pipe in the routers
607# section above.
608
609address_pipe:
610 driver = pipe
611 return_output
612
613
614# This transport is used for handling deliveries directly to files that are
615# generated by aliasing or forwarding.
616
617address_file:
618 driver = appendfile
619 delivery_date_add
620 envelope_to_add
621 return_path_add
622
623
624# This transport is used for handling autoreplies generated by the filtering
625# option of the userforward router.
626
627address_reply:
628 driver = autoreply
629
630
631
632######################################################################
633# RETRY CONFIGURATION #
634######################################################################
635
636begin retry
637
638# This single retry rule applies to all domains and all errors. It specifies
639# retries every 15 minutes for 2 hours, then increasing retry intervals,
640# starting at 1 hour and increasing each time by a factor of 1.5, up to 16
641# hours, then retries every 6 hours until 4 days have passed since the first
642# failed delivery.
643
644# Address or Domain Error Retries
645# ----------------- ----- -------
646
647* * F,2h,15m; G,16h,1h,1.5; F,4d,6h
648
649
650
651######################################################################
652# REWRITE CONFIGURATION #
653######################################################################
654
655# There are no rewriting specifications in this default configuration file.
656
657begin rewrite
658
659
660
661######################################################################
662# AUTHENTICATION CONFIGURATION #
663######################################################################
664
665# There are no authenticator specifications in this default configuration file.
666
667begin authenticators
668
669
670
671######################################################################
672# CONFIGURATION FOR local_scan() #
673######################################################################
674
675# If you have built Exim to include a local_scan() function that contains
676# tables for private options, you can define those options here. Remember to
677# uncomment the "begin" line. It is commented by default because it provokes
678# an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
679# set in the Local/Makefile.
680
681# begin local_scan
682
683
684# End of Exim configuration file