1 # $Cambridge: exim/exim-src/src/configure.default,v 1.14 2009/10/16 07:46:13 tom Exp $
3 ######################################################################
4 # Runtime configuration file for Exim #
5 ######################################################################
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.
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 #
23 ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
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. #
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. #
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"). #
38 ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
42 ######################################################################
43 # MAIN CONFIGURATION SETTINGS #
44 ######################################################################
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.
51 primary_hostname = <%= node[:fqdn] %>
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:
59 domainlist local_domains = <%= node[:exim][:local_domains].join(" : ") %>
60 domainlist relay_to_domains = <%= @relay_to_domains.join(" : ") %>
61 hostlist relay_from_hosts = <; <%= @relay_from_hosts.join(" ; ") %>
63 # Most straightforward access control requirements can be obtained by
64 # appropriate settings of the above options. In more complicated situations,
65 # you may need to modify the Access Control Lists (ACLs) which appear later in
68 # The first setting specifies your local domains, for example:
70 # domainlist local_domains = my.first.domain : my.second.domain
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.
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:
86 # domainlist relay_to_domains = *.myco.com : my.friend.org
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
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:
96 # hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16
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
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
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:
108 acl_smtp_rcpt = acl_check_rcpt
109 acl_smtp_data = acl_check_data
111 # You should not change those settings until you understand how ACLs work.
114 <% if File.exist?("/var/run/clamav/clamd.ctl") -%>
115 # If you are running a version of Exim that was compiled with the content-
116 # scanning extension, you can cause incoming messages to be automatically
117 # scanned for viruses. You have to modify the configuration in two places to
118 # set this up. The first of them is here, where you define the interface to
119 # your scanner. This example is typical for ClamAV; see the manual for details
120 # of what to set for other virus scanners. The second modification is in the
121 # acl_check_data access control list (see below).
123 av_scanner = clamd:/var/run/clamav/clamd.ctl
127 <% if File.exist?("/var/run/spamd.pid") -%>
128 # For spam scanning, there is a similar option that defines the interface to
129 # SpamAssassin. You do not need to set this if you are using the default, which
130 # is shown in this commented example. As for virus scanning, you must also
131 # modify the acl_check_data access control list to enable spam scanning.
133 spamd_address = 127.0.0.1 783
137 # If Exim is compiled with support for TLS, you may want to enable the
138 # following options so that Exim allows clients to make encrypted
139 # connections. In the authenticators section below, there are template
140 # configurations for plaintext username/password authentication. This kind
141 # of authentication is only safe when used within a TLS connection, so the
142 # authenticators will only work if the following TLS settings are turned on
145 # Allow any client to use TLS.
147 tls_advertise_hosts = <; !127.0.0.1 ; !::1
149 # Specify the location of the Exim server's TLS certificate and private key.
150 # The private key must not be encrypted (password protected). You can put
151 # the certificate and private key in the same file, in which case you only
152 # need the first setting, or in separate files, in which case you need both
155 tls_certificate = /etc/ssl/certs/exim.pem
156 tls_privatekey = /etc/ssl/private/exim.key
158 # In order to support roaming users who wish to send email from anywhere,
159 # you may want to make Exim listen on other ports as well as port 25, in
160 # case these users need to send email from a network that blocks port 25.
161 # The standard port for this purpose is port 587, the "message submission"
162 # port. See RFC 4409 for details. Microsoft MUAs cannot be configured to
163 # talk the message submission protocol correctly, so if you need to support
164 # them you should also allow TLS-on-connect on the traditional but
165 # non-standard port 465.
167 daemon_smtp_ports = <%= node[:exim][:daemon_smtp_ports].join(" : ") %>
168 # tls_on_connect_ports = 465
171 # Specify the domain you want to be added to all unqualified addresses
172 # here. An unqualified address is one that does not contain an "@" character
173 # followed by a domain. For example, "caesar@rome.example" is a fully qualified
174 # address, but the string "caesar" (i.e. just a login name) is an unqualified
175 # email address. Unqualified addresses are accepted only from local callers by
176 # default. See the recipient_unqualified_hosts option if you want to permit
177 # unqualified addresses from remote sources. If this option is not set, the
178 # primary_hostname value is used for qualification.
180 qualify_domain = openstreetmap.org
183 # If you want unqualified recipient addresses to be qualified with a different
184 # domain to unqualified sender addresses, specify the recipient domain here.
185 # If this option is not set, the qualify_domain value is used.
187 qualify_recipient = <%= node[:fqdn] %>
190 # The following line must be uncommented if you want Exim to recognize
191 # addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
192 # (an IP address) instead of a named domain. The RFCs still require this form,
193 # but it makes little sense to permit mail to be sent to specific hosts by
194 # their IP address in the modern Internet. This ancient format has been used
195 # by those seeking to abuse hosts by using them for unwanted relaying. If you
196 # really do want to support domain literals, uncomment the following line, and
197 # see also the "domain_literal" router below.
199 # allow_domain_literals
202 # No deliveries will ever be run under the uids of users specified by
203 # never_users (a colon-separated list). An attempt to do so causes a panic
204 # error to be logged, and the delivery to be deferred. This is a paranoic
205 # safety catch. There is an even stronger safety catch in the form of the
206 # FIXED_NEVER_USERS setting in the configuration for building Exim. The list of
207 # users that it specifies is built into the binary, and cannot be changed. The
208 # option below just adds additional users to the list. The default for
209 # FIXED_NEVER_USERS is "root", but just to be absolutely sure, the default here
212 # Note that the default setting means you cannot deliver mail addressed to root
213 # as if it were a normal user. This isn't usually a problem, as most sites have
214 # an alias for root that redirects such mail to a human administrator.
219 # The setting below causes Exim to do a reverse DNS lookup on all incoming
220 # IP calls, in order to get the true host name. If you feel this is too
221 # expensive, you can specify the networks for which a lookup is done, or
222 # remove the setting entirely.
227 # The settings below, which are actually the same as the defaults in the
228 # code, cause Exim to make RFC 1413 (ident) callbacks for all incoming SMTP
229 # calls. You can limit the hosts to which these calls are made, and/or change
230 # the timeout that is used. If you set the timeout to zero, all RFC 1413 calls
231 # are disabled. RFC 1413 calls are cheap and can provide useful information
232 # for tracing problem messages, but some hosts and firewalls have problems
233 # with them. This can result in a timeout instead of an immediate refused
234 # connection, leading to delays on starting up SMTP sessions. (The default was
235 # reduced from 30s to 5s for release 4.61.)
238 rfc1413_query_timeout = 5s
241 # By default, Exim expects all envelope addresses to be fully qualified, that
242 # is, they must contain both a local part and a domain. If you want to accept
243 # unqualified addresses (just a local part) from certain hosts, you can specify
244 # these hosts by setting one or both of
246 # sender_unqualified_hosts =
247 # recipient_unqualified_hosts =
249 # to control sender and recipient addresses, respectively. When this is done,
250 # unqualified addresses are qualified using the settings of qualify_domain
251 # and/or qualify_recipient (see above).
254 # If you want Exim to support the "percent hack" for certain domains,
255 # uncomment the following line and provide a list of domains. The "percent
256 # hack" is the feature by which mail addressed to x%y@z (where z is one of
257 # the domains listed) is locally rerouted to x@y and sent on. If z is not one
258 # of the "percent hack" domains, x%y is treated as an ordinary local part. This
259 # hack is rarely needed nowadays; you should not enable it unless you are sure
260 # that you really need it.
262 # percent_hack_domains =
264 # As well as setting this option you will also need to remove the test
265 # for local parts containing % in the ACL definition below.
268 # When Exim can neither deliver a message nor return it to sender, it "freezes"
269 # the delivery error message (aka "bounce message"). There are also other
270 # circumstances in which messages get frozen. They will stay on the queue for
271 # ever unless one of the following options is set.
273 # This option unfreezes frozen bounce messages after two days, tries
274 # once more to deliver them, and ignores any delivery failures.
276 ignore_bounce_errors_after = 2d
278 # This option cancels (removes) frozen messages that are older than a week.
280 timeout_frozen_after = 7d
283 # By default, messages that are waiting on Exim's queue are all held in a
284 # single directory called "input" which it itself within Exim's spool
285 # directory. (The default spool directory is specified when Exim is built, and
286 # is often /var/spool/exim/.) Exim works best when its queue is kept short, but
287 # there are circumstances where this is not always possible. If you uncomment
288 # the setting below, messages on the queue are held in 62 subdirectories of
289 # "input" instead of all in the same directory. The subdirectories are called
290 # 0, 1, ... A, B, ... a, b, ... z. This has two benefits: (1) If your file
291 # system degrades with many files in one directory, this is less likely to
292 # happen; (2) Exim can process the queue one subdirectory at a time instead of
293 # all at once, which can give better performance with large queues.
295 # split_spool_directory = true
298 # Log just about everything we can log so that we have the best
299 # possible chance of knowing what's going on.
301 log_selector = +all -skip_delivery
304 # Define trusted users.
306 trusted_users = <%= node[:exim][:trusted_users].join(" : ") %>
310 ######################################################################
311 # ACL CONFIGURATION #
312 # Specifies access control lists for incoming SMTP mail #
313 ######################################################################
317 # This access control list is used for every RCPT command in an incoming
318 # SMTP message. The tests are run in order until the address is either
319 # accepted or denied.
323 # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
324 # testing for an empty sending host field.
327 <% if node[:lsb][:release].to_i >= 10.04 -%>
328 control = dkim_disable_verify
331 #############################################################################
332 # The following section of the ACL is concerned with local parts that contain
333 # @ or % or ! or / or | or dots in unusual places.
335 # The characters other than dots are rarely found in genuine local parts, but
336 # are often tried by people looking to circumvent relaying restrictions.
337 # Therefore, although they are valid in local parts, these rules lock them
338 # out, as a precaution.
340 # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
341 # allows them because they have been encountered. (Consider local parts
342 # constructed as "firstinitial.secondinitial.familyname" when applied to
343 # someone like me, who has no second initial.) However, a local part starting
344 # with a dot or containing /../ can cause trouble if it is used as part of a
345 # file name (e.g. for a mailing list). This is also true for local parts that
346 # contain slashes. A pipe symbol can also be troublesome if the local part is
347 # incorporated unthinkingly into a shell command line.
349 # Two different rules are used. The first one is stricter, and is applied to
350 # messages that are addressed to one of the local domains handled by this
351 # host. The line "domains = +local_domains" restricts it to domains that are
352 # defined by the "domainlist local_domains" setting above. The rule blocks
353 # local parts that begin with a dot or contain @ % ! / or |. If you have
354 # local accounts that include these characters, you will have to modify this
357 deny message = Restricted characters in address
358 domains = +local_domains
359 local_parts = ^[.] : ^.*[@%!/|]
361 # The second rule applies to all other domains, and is less strict. The line
362 # "domains = !+local_domains" restricts it to domains that are NOT defined by
363 # the "domainlist local_domains" setting above. The exclamation mark is a
364 # negating operator. This rule allows your own users to send outgoing
365 # messages to sites that use slashes and vertical bars in their local parts.
366 # It blocks local parts that begin with a dot, slash, or vertical bar, but
367 # allows these characters within the local part. However, the sequence /../
368 # is barred. The use of @ % and ! is blocked, as before. The motivation here
369 # is to prevent your users (or your users' viruses) from mounting certain
370 # kinds of attack on remote sites.
372 deny message = Restricted characters in address
373 domains = !+local_domains
374 local_parts = ^[./|] : ^.*[@%!] : ^.*/\\.\\./
375 #############################################################################
377 # Accept mail to postmaster in any local domain, regardless of the source,
378 # and without verifying the sender.
380 accept local_parts = postmaster
381 domains = +local_domains
383 # Deny incoming mail unless the sender address can be verified.
385 deny !hosts = +relay_from_hosts
386 !verify = sender/callout/defer_ok
388 # Accept if the message comes from one of the hosts for which we are an
389 # outgoing relay. It is assumed that such hosts are most likely to be MUAs,
390 # so we set control=submission to make Exim treat the message as a
391 # submission. It will fix up various errors in the message, for example, the
392 # lack of a Date: header line. If you are actually relaying out out from
393 # MTAs, you may want to disable this. If you are handling both relaying from
394 # MTAs and submissions from MUAs you should probably split them into two
395 # lists, and handle them differently.
397 # Recipient verification is omitted here, because in many cases the clients
398 # are dumb MUAs that don't cope well with SMTP error responses. If you are
399 # actually relaying out from MTAs, you should probably add recipient
402 # Note that, by putting this test before any DNS black list checks, you will
403 # always accept from these hosts, even if they end up on a black list. The
404 # assumption is that they are your friends, and if they get onto a black
405 # list, it is a mistake.
407 accept hosts = +relay_from_hosts
409 <% if node[:lsb][:release].to_i >= 10.04 -%>
410 control = dkim_disable_verify
413 # Accept if the message arrived over an authenticated connection, from
414 # any host. Again, these messages are usually from MUAs, so recipient
415 # verification is omitted, and submission mode is set. And again, we do this
416 # check before any black list tests.
418 accept authenticated = *
420 <% if node[:lsb][:release].to_i >= 10.04 -%>
421 control = dkim_disable_verify
424 # Insist that any other recipient address that we accept is either in one of
425 # our local domains, or is in a domain for which we explicitly allow
426 # relaying. Any other domain is rejected as being unacceptable for relaying.
428 require message = relay not permitted
429 domains = +local_domains : +relay_to_domains
431 # We also require all accepted addresses to be verifiable. This check will
432 # do local part verification for local domains, but only check the domain
433 # for remote domains. The only way to check local parts for the remote
434 # relay domains is to use a callout (add /callout), but please read the
435 # documentation about callouts before doing this.
437 require verify = recipient
439 <% if node[:exim][:dns_blacklists] -%>
440 # Deny any messages from hosts in certain blacklists.
442 deny message = Rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
443 dnslists = <%= node[:exim][:dns_blacklists].join(" : ") %>
446 #############################################################################
447 # This check is commented out because it is recognized that not every
448 # sysadmin will want to do it. If you enable it, the check performs
449 # Client SMTP Authorization (csa) checks on the sending host. These checks
450 # do DNS lookups for SRV records. The CSA proposal is currently (May 2005)
451 # an Internet draft. You can, of course, add additional conditions to this
452 # ACL statement to restrict the CSA checks to certain hosts only.
454 # require verify = csa
455 #############################################################################
457 # At this point, the address has passed all the checks that have been
458 # configured, so we accept it unconditionally.
463 # This ACL is used after the contents of a message have been received. This
464 # is the ACL in which you can test a message's headers or body, and in
465 # particular, this is where you can invoke external virus or spam scanners.
466 # Some suggested ways of configuring these tests are shown below, commented
467 # out. Without any tests, this ACL accepts all messages. If you want to use
468 # such tests, you must ensure that Exim is compiled with the content-scanning
469 # extension (WITH_CONTENT_SCAN=yes in Local/Makefile).
473 <% if File.exist?("/var/run/clamav/clamd.ctl") -%>
474 # Deny if the message contains a virus. Before enabling this check, you
475 # must install a virus scanner and set the av_scanner option above.
479 message = This message contains a virus ($malware_name).
482 <% if File.exist?("/var/run/spamd.pid") -%>
483 # Deny if the message looks like spam. Before enabling this check, you
484 # must install spamassassin and set the spamd_address option above.
486 deny spam = nobody/deferok
487 message = This message scored $spam_score SpamAssassin points.
490 # Accept the message.
496 ######################################################################
497 # ROUTERS CONFIGURATION #
498 # Specifies how addresses are handled #
499 ######################################################################
500 # THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
501 # An address is passed to each router in turn until it is accepted. #
502 ######################################################################
506 # This router handles aliasing using a linearly searched alias file with the
507 # name /etc/aliases. When this configuration is installed automatically,
508 # the name gets inserted into this file from whatever is set in Exim's
509 # build-time configuration. The default path is the traditional /etc/aliases.
510 # If you install this configuration by hand, you need to specify the correct
511 # path in the "data" setting below.
513 ##### NB You must ensure that the alias file exists. It used to be the case
514 ##### NB that every Unix had that file, because it was the Sendmail default.
515 ##### NB These days, there are systems that don't have it. Your aliases
516 ##### NB file should at least contain an alias for "postmaster".
518 # If any of your aliases expand to pipes or files, you will need to set
519 # up a user and a group for these deliveries to run under. You can do
520 # this by uncommenting the "user" option below (changing the user name
521 # as appropriate) and adding a "group" option if necessary. Alternatively, you
522 # can specify "user" on the transports that are used. Note that the transports
523 # listed below are the same as are used for .forward files; you might want
524 # to set up different ones for pipe and file deliveries from aliases.
528 domains = +local_domains
531 data = ${lookup{$local_part}lsearch{/etc/aliases}}
533 file_transport = address_file
534 pipe_transport = address_pipe
536 <% if File.directory?("/var/lib/mailman") -%>
537 # This router handles mail for mailman mailing lists.
541 domains = +local_domains
542 condition = ${lookup{$local_part@$domain}lsearch{/var/lib/mailman/data/virtual-mailman}{1}{0}}
543 require_files = /var/lib/mailman/lists/$local_part/config.pck
544 local_part_suffix = -bounces : -bounces+* : \
545 -confirm+* : -join : -leave : \
546 -subscribe : -unsubscribe : \
547 -owner : -request : -admin
548 local_part_suffix_optional
552 # This router handles mail for noreply.openstreetmap.org
556 domains = noreply.openstreetmap.org
557 require_files = /etc/exim4/noreply/$local_part
560 <% node[:exim][:routes].each do |name,details| -%>
561 # This router handles mail for <%= details[:comment] -%>.
564 <% if details[:host] -%>
569 <% if details[:domains] -%>
570 domains = <%= details[:domains].join(" : ") %>
572 <% if details[:local_parts] -%>
573 local_parts = <%= details[:local_parts].join(" : ") %>
575 <% if details[:host] -%>
576 <% if details[:host].kind_of?(Array) -%>
577 route_data = <%= details[:host].join(":") %> byname
579 route_data = <%= details[:host] %> byname
581 transport = remote_smtp
583 transport = <%= name %>
588 <% if node[:exim][:smarthost_via] -%>
589 # This router routes addresses that are not in local domains by
590 # forwarding them to a smarthost.
594 domains = ! +local_domains
595 transport = remote_smtp
596 route_data = <%= node[:exim][:smarthost_via].gsub(":", "::") -%> byname
597 same_domain_copy_routing = yes
600 # This router routes addresses that are not in local domains by doing a DNS
601 # lookup on the domain name. The exclamation mark that appears in "domains = !
602 # +local_domains" is a negating operator, that is, it can be read as "not". The
603 # recipient's domain must not be one of those defined by "domainlist
604 # local_domains" above for this router to be used.
606 # If the router is used, any domain that resolves to 0.0.0.0 or to a loopback
607 # interface address (127.0.0.0/8) is treated as if it had no DNS entry. Note
608 # that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated as the
609 # local host inside the network stack. It is not 0.0.0.0/0, the default route.
610 # If the DNS lookup fails, no further routers are tried because of the no_more
611 # setting, and consequently the address is unrouteable.
615 domains = ! +local_domains
616 transport = remote_smtp
617 same_domain_copy_routing = yes
618 ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
623 ######################################################################
624 # TRANSPORTS CONFIGURATION #
625 ######################################################################
626 # ORDER DOES NOT MATTER #
627 # Only one appropriate transport is called for each delivery. #
628 ######################################################################
630 # A transport is used only when referenced from a router that successfully
631 # handles an address.
636 # This transport is used for delivering messages over SMTP connections.
642 # This transport is used for handling pipe deliveries generated by alias or
643 # .forward files. If the pipe generates any standard output, it is returned
644 # to the sender of the message as a delivery error. Set return_fail_output
645 # instead of return_output if you want this to happen only when the pipe fails
646 # to complete normally. You can set different transports for aliases and
647 # forwards if you want to - see the references to address_pipe in the routers
655 # This transport is used for handling deliveries directly to files that are
656 # generated by aliasing or forwarding.
665 <% if File.directory?("/var/lib/mailman") -%>
666 # This transport is used for handling deliveries to mailman mailing lists.
670 command = /var/lib/mailman/mail/mailman \
671 '${if def:local_part_suffix \
672 {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
675 current_directory = /var/lib/mailman
676 home_directory = /var/lib/mailman
679 freeze_exec_fail = true
683 # This transport handles mail for noreply.openstreetmap.org
687 from = OpenStreetMap <noreply@openstreetmap.org>
689 subject = Re: $header_subject:
690 headers = MIME-Version: 1.0\nContent-Type: text/plain; charset=utf-8
691 file = /etc/exim4/noreply/$local_part
695 <% node[:exim][:routes].each do |name,details| -%>
696 <% if details[:command] -%>
697 # This transport handles mail for <%= details[:comment] -%>.
701 command = <%= details[:command] %>
702 user = <%= details[:user] %>
703 <% if details[:group] -%>
704 group = <%= details[:group] %>
706 home_directory = <%= details[:home_directory] %>
713 ######################################################################
714 # RETRY CONFIGURATION #
715 ######################################################################
719 # This single retry rule applies to all domains and all errors. It specifies
720 # retries every 15 minutes for 2 hours, then increasing retry intervals,
721 # starting at 1 hour and increasing each time by a factor of 1.5, up to 16
722 # hours, then retries every 6 hours until 4 days have passed since the first
725 # WARNING: If you do not have any retry rules at all (this section of the
726 # configuration is non-existent or empty), Exim will not do any retries of
727 # messages that fail to get delivered at the first attempt. The effect will
728 # be to treat temporary errors as permanent. Therefore, DO NOT remove this
729 # retry rule unless you really don't want any retries.
731 # Address or Domain Error Retries
732 # ----------------- ----- -------
734 * * F,2h,15m; G,16h,1h,1.5; F,4d,6h
738 ######################################################################
739 # REWRITE CONFIGURATION #
740 ######################################################################
742 # There are no rewriting specifications in this default configuration file.
748 ######################################################################
749 # AUTHENTICATION CONFIGURATION #
750 ######################################################################
752 # The following authenticators support plaintext username/password
753 # authentication using the standard PLAIN mechanism and the traditional
754 # but non-standard LOGIN mechanism, with Exim acting as the server.
755 # PLAIN and LOGIN are enough to support most MUA software.
757 # These authenticators are not complete: you need to change the
758 # server_condition settings to specify how passwords are verified.
759 # They are set up to offer authentication to the client only if the
760 # connection is encrypted with TLS, so you also need to add support
761 # for TLS. See the global configuration options section at the start
762 # of this file for more about TLS.
764 # The default RCPT ACL checks for successful authentication, and will accept
765 # messages from authenticated users from anywhere on the Internet.
769 # PLAIN authentication has no server prompts. The client sends its
770 # credentials in one lump, containing an authorization ID (which we do not
771 # use), an authentication ID, and a password. The latter two appear as
772 # $auth2 and $auth3 in the configuration and should be checked against a
773 # valid username and password. In a real configuration you would typically
774 # use $auth2 as a lookup key, and compare $auth3 against the result of the
775 # lookup, perhaps using the crypteq{}{} condition.
779 # server_set_id = $auth2
781 # server_condition = Authentication is not yet configured
782 # server_advertise_condition = ${if def:tls_cipher }
784 # LOGIN authentication has traditional prompts and responses. There is no
785 # authorization ID in this mechanism, so unlike PLAIN the username and
786 # password are $auth1 and $auth2. Apart from that you can use the same
787 # server_condition setting for both authenticators.
791 # server_set_id = $auth1
792 # server_prompts = <| Username: | Password:
793 # server_condition = Authentication is not yet configured
794 # server_advertise_condition = ${if def:tls_cipher }
797 ######################################################################
798 # CONFIGURATION FOR local_scan() #
799 ######################################################################
801 # If you have built Exim to include a local_scan() function that contains
802 # tables for private options, you can define those options here. Remember to
803 # uncomment the "begin" line. It is commented by default because it provokes
804 # an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
805 # set in the Local/Makefile.
810 # End of Exim configuration file