1 ######################################################################
2 # Runtime configuration file for Exim #
3 ######################################################################
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.
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 #
21 ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
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. #
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. #
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"). #
36 ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
40 ######################################################################
41 # MAIN CONFIGURATION SETTINGS #
42 ######################################################################
45 # Specify your host's canonical name here. This should normally be the fully
46 # qualified "official" name of your host. If this option is not set, the
47 # uname() function is called to obtain the name. In many cases this does
48 # the right thing and you need not set anything explicitly.
53 # The next three settings create two lists of domains and one list of hosts.
54 # These lists are referred to later in this configuration using the syntax
55 # +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
56 # are all colon-separated lists:
58 domainlist local_domains = @
59 domainlist relay_to_domains =
60 hostlist relay_from_hosts = localhost
61 # (We rely upon hostname resolution working for localhost, because the default
62 # uncommented configuration needs to work in IPv4-only environments.)
64 # Most straightforward access control requirements can be obtained by
65 # appropriate settings of the above options. In more complicated situations,
66 # you may need to modify the Access Control Lists (ACLs) which appear later in
69 # The first setting specifies your local domains, for example:
71 # domainlist local_domains = my.first.domain : my.second.domain
73 # You can use "@" to mean "the name of the local host", as in the default
74 # setting above. This is the name that is specified by primary_hostname,
75 # as specified above (or defaulted). If you do not want to do any local
76 # deliveries, remove the "@" from the setting above. If you want to accept mail
77 # addressed to your host's literal IP address, for example, mail addressed to
78 # "user@[192.168.23.44]", you can add "@[]" as an item in the local domains
79 # list. You also need to uncomment "allow_domain_literals" below. This is not
80 # recommended for today's Internet.
82 # The second setting specifies domains for which your host is an incoming relay.
83 # If you are not doing any relaying, you should leave the list empty. However,
84 # if your host is an MX backup or gateway of some kind for some domains, you
85 # must set relay_to_domains to match those domains. For example:
87 # domainlist relay_to_domains = *.myco.com : my.friend.org
89 # This will allow any host to relay through your host to those domains.
90 # See the section of the manual entitled "Control of relaying" for more
93 # The third setting specifies hosts that can use your host as an outgoing relay
94 # to any other host on the Internet. Such a setting commonly refers to a
95 # complete local network as well as the localhost. For example:
97 # hostlist relay_from_hosts = <; 127.0.0.1 ; ::1 ; 192.168.0.0/16
99 # The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
100 # have to include 127.0.0.1 if you want to allow processes on your host to send
101 # SMTP mail by using the loopback address. A number of MUAs use this method of
102 # sending mail. Often, connections are made to "localhost", which might be ::1
103 # on IPv6-enabled hosts. Do not forget CIDR for your IPv6 networks.
105 # All three of these lists may contain many different kinds of item, including
106 # wildcarded names, regular expressions, and file lookups. See the reference
107 # manual for details. The lists above are used in the access control lists for
108 # checking incoming messages. The names of these ACLs are defined here:
110 acl_smtp_rcpt = acl_check_rcpt
111 acl_smtp_data = acl_check_data
113 # You should not change those settings until you understand how ACLs work.
116 # If you are running a version of Exim that was compiled with the content-
117 # scanning extension, you can cause incoming messages to be automatically
118 # scanned for viruses. You have to modify the configuration in two places to
119 # set this up. The first of them is here, where you define the interface to
120 # your scanner. This example is typical for ClamAV; see the manual for details
121 # of what to set for other virus scanners. The second modification is in the
122 # acl_check_data access control list (see below).
124 # av_scanner = clamd:/tmp/clamd
127 # For spam scanning, there is a similar option that defines the interface to
128 # SpamAssassin. You do not need to set this if you are using the default, which
129 # is shown in this commented example. As for virus scanning, you must also
130 # modify the acl_check_data access control list to enable spam scanning.
132 # spamd_address = 127.0.0.1 783
135 # If Exim is compiled with support for TLS, you may want to enable the
136 # following options so that Exim allows clients to make encrypted
137 # connections. In the authenticators section below, there are template
138 # configurations for plaintext username/password authentication. This kind
139 # of authentication is only safe when used within a TLS connection, so the
140 # authenticators will only work if the following TLS settings are turned on
143 # Allow any client to use TLS.
144 # tls_advertise_hosts = *
146 tls_advertise_hosts =
148 # Specify the location of the Exim server's TLS certificate and private key.
149 # The private key must not be encrypted (password protected). You can put
150 # the certificate and private key in the same file, in which case you only
151 # need the first setting, or in separate files, in which case you need both
154 # tls_certificate = /etc/ssl/exim.crt
155 # tls_privatekey = /etc/ssl/exim.pem
157 # In order to support roaming users who wish to send email from anywhere,
158 # you may want to make Exim listen on other ports as well as port 25, in
159 # case these users need to send email from a network that blocks port 25.
160 # The standard port for this purpose is port 587, the "message submission"
161 # port. See RFC 4409 for details. Microsoft MUAs cannot be configured to
162 # talk the message submission protocol correctly, so if you need to support
163 # them you should also allow TLS-on-connect on the traditional but
164 # non-standard port 465.
166 # daemon_smtp_ports = 25 : 465 : 587
167 # tls_on_connect_ports = 465
170 # Specify the domain you want to be added to all unqualified addresses
171 # here. An unqualified address is one that does not contain an "@" character
172 # followed by a domain. For example, "caesar@rome.example" is a fully qualified
173 # address, but the string "caesar" (i.e. just a login name) is an unqualified
174 # email address. Unqualified addresses are accepted only from local callers by
175 # default. See the recipient_unqualified_hosts option if you want to permit
176 # unqualified addresses from remote sources. If this option is not set, the
177 # primary_hostname value is used for qualification.
182 # If you want unqualified recipient addresses to be qualified with a different
183 # domain to unqualified sender addresses, specify the recipient domain here.
184 # If this option is not set, the qualify_domain value is used.
186 # qualify_recipient =
189 # The following line must be uncommented if you want Exim to recognize
190 # addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
191 # (an IP address) instead of a named domain. The RFCs still require this form,
192 # but it makes little sense to permit mail to be sent to specific hosts by
193 # their IP address in the modern Internet. This ancient format has been used
194 # by those seeking to abuse hosts by using them for unwanted relaying. If you
195 # really do want to support domain literals, uncomment the following line, and
196 # see also the "domain_literal" router below.
198 # allow_domain_literals
201 # No deliveries will ever be run under the uids of users specified by
202 # never_users (a colon-separated list). An attempt to do so causes a panic
203 # error to be logged, and the delivery to be deferred. This is a paranoic
204 # safety catch. There is an even stronger safety catch in the form of the
205 # FIXED_NEVER_USERS setting in the configuration for building Exim. The list of
206 # users that it specifies is built into the binary, and cannot be changed. The
207 # option below just adds additional users to the list. The default for
208 # FIXED_NEVER_USERS is "root", but just to be absolutely sure, the default here
211 # Note that the default setting means you cannot deliver mail addressed to root
212 # as if it were a normal user. This isn't usually a problem, as most sites have
213 # an alias for root that redirects such mail to a human administrator.
218 # The setting below causes Exim to do a reverse DNS lookup on all incoming
219 # IP calls, in order to get the true host name. If you feel this is too
220 # expensive, you can specify the networks for which a lookup is done, or
221 # remove the setting entirely.
226 # Advertise DSN for these hosts
228 dsn_advertise_hosts = *
230 # The settings below cause Exim to make RFC 1413 (ident) callbacks
231 # for all incoming SMTP calls. You can limit the hosts to which these
232 # calls are made, and/or change the timeout that is used. If you set
233 # the timeout to zero, all RFC 1413 calls are disabled. RFC 1413 calls
234 # are cheap and can provide useful information for tracing problem
235 # messages, but some hosts and firewalls have problems with them.
236 # This can result in a timeout instead of an immediate refused
237 # connection, leading to delays on starting up SMTP sessions.
238 # (The default was reduced from 30s to 5s for release 4.61. and to
239 # disabled for release 4.86)
242 #rfc1413_query_timeout = 5s
245 # Enable an efficiency feature. We advertise the feature; clients
246 # may request to use it. For multi-recipient mails we then can
247 # reject or accept per-user after the message is received.
252 # By default, Exim expects all envelope addresses to be fully qualified, that
253 # is, they must contain both a local part and a domain. If you want to accept
254 # unqualified addresses (just a local part) from certain hosts, you can specify
255 # these hosts by setting one or both of
257 # sender_unqualified_hosts =
258 # recipient_unqualified_hosts =
260 # to control sender and recipient addresses, respectively. When this is done,
261 # unqualified addresses are qualified using the settings of qualify_domain
262 # and/or qualify_recipient (see above).
265 # Unless you run a high-volume site you probably want more logging
266 # detail than the default. Adjust to suit.
268 log_selector = +smtp_protocol_error +smtp_syntax_error +tls_sni \
269 +tls_certificate_verified +smtp_confirmation +queue_time
272 # If you want Exim to support the "percent hack" for certain domains,
273 # uncomment the following line and provide a list of domains. The "percent
274 # hack" is the feature by which mail addressed to x%y@z (where z is one of
275 # the domains listed) is locally rerouted to x@y and sent on. If z is not one
276 # of the "percent hack" domains, x%y is treated as an ordinary local part. This
277 # hack is rarely needed nowadays; you should not enable it unless you are sure
278 # that you really need it.
280 # percent_hack_domains =
282 # As well as setting this option you will also need to remove the test
283 # for local parts containing % in the ACL definition below.
286 # When Exim can neither deliver a message nor return it to sender, it "freezes"
287 # the delivery error message (aka "bounce message"). There are also other
288 # circumstances in which messages get frozen. They will stay on the queue for
289 # ever unless one of the following options is set.
291 # This option unfreezes frozen bounce messages after two days, tries
292 # once more to deliver them, and ignores any delivery failures.
294 ignore_bounce_errors_after = 2d
296 # This option cancels (removes) frozen messages that are older than a week.
298 timeout_frozen_after = 7d
301 # By default, messages that are waiting on Exim's queue are all held in a
302 # single directory called "input" which it itself within Exim's spool
303 # directory. (The default spool directory is specified when Exim is built, and
304 # is often /var/spool/exim/.) Exim works best when its queue is kept short, but
305 # there are circumstances where this is not always possible. If you uncomment
306 # the setting below, messages on the queue are held in 62 subdirectories of
307 # "input" instead of all in the same directory. The subdirectories are called
308 # 0, 1, ... A, B, ... a, b, ... z. This has two benefits: (1) If your file
309 # system degrades with many files in one directory, this is less likely to
310 # happen; (2) Exim can process the queue one subdirectory at a time instead of
311 # all at once, which can give better performance with large queues.
313 # split_spool_directory = true
316 # If you're in a part of the world where ASCII is not sufficient for most
317 # text, then you're probably familiar with RFC2047 message header extensions.
318 # By default, Exim adheres to the specification, including a limit of 76
319 # characters to a line, with encoded words fitting within a line.
320 # If you wish to use decoded headers in message filters in such a way
321 # that successful decoding of malformed messages matters, you may wish to
322 # configure Exim to be more lenient.
324 # check_rfc2047_length = false
326 # In particular, the Exim maintainers have had multiple reports of problems
327 # from Russian administrators of issues until they disable this check,
328 # because of some popular, yet buggy, mail composition software.
331 # If you wish to be strictly RFC compliant, or if you know you'll be
332 # exchanging email with systems that are not 8-bit clean, then you may
333 # wish to disable advertising 8BITMIME. Uncomment this option to do so.
335 # accept_8bitmime = false
338 # Exim does not make use of environment variables itself. However,
339 # libraries that Exim uses (e.g. LDAP) depend on specific environment settings.
340 # There are two lists: keep_environment for the variables we trust, and
341 # add_environment for variables we want to set to a specific value.
342 # Note that TZ is handled separateley by the timezone runtime option
343 # and TIMEZONE_DEFAULT buildtime option.
345 # keep_environment = ^LDAP
346 # add_environment = PATH=/usr/bin::/bin
350 ######################################################################
351 # ACL CONFIGURATION #
352 # Specifies access control lists for incoming SMTP mail #
353 ######################################################################
357 # This access control list is used for every RCPT command in an incoming
358 # SMTP message. The tests are run in order until the address is either
359 # accepted or denied.
363 # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
364 # testing for an empty sending host field.
367 control = dkim_disable_verify
369 #############################################################################
370 # The following section of the ACL is concerned with local parts that contain
371 # @ or % or ! or / or | or dots in unusual places.
373 # The characters other than dots are rarely found in genuine local parts, but
374 # are often tried by people looking to circumvent relaying restrictions.
375 # Therefore, although they are valid in local parts, these rules lock them
376 # out, as a precaution.
378 # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
379 # allows them because they have been encountered. (Consider local parts
380 # constructed as "firstinitial.secondinitial.familyname" when applied to
381 # someone like me, who has no second initial.) However, a local part starting
382 # with a dot or containing /../ can cause trouble if it is used as part of a
383 # file name (e.g. for a mailing list). This is also true for local parts that
384 # contain slashes. A pipe symbol can also be troublesome if the local part is
385 # incorporated unthinkingly into a shell command line.
387 # Two different rules are used. The first one is stricter, and is applied to
388 # messages that are addressed to one of the local domains handled by this
389 # host. The line "domains = +local_domains" restricts it to domains that are
390 # defined by the "domainlist local_domains" setting above. The rule blocks
391 # local parts that begin with a dot or contain @ % ! / or |. If you have
392 # local accounts that include these characters, you will have to modify this
395 deny message = Restricted characters in address
396 domains = +local_domains
397 local_parts = ^[.] : ^.*[@%!|]
399 # The second rule applies to all other domains, and is less strict. The line
400 # "domains = !+local_domains" restricts it to domains that are NOT defined by
401 # the "domainlist local_domains" setting above. The exclamation mark is a
402 # negating operator. This rule allows your own users to send outgoing
403 # messages to sites that use slashes and vertical bars in their local parts.
404 # It blocks local parts that begin with a dot, slash, or vertical bar, but
405 # allows these characters within the local part. However, the sequence /../
406 # is barred. The use of @ % and ! is blocked, as before. The motivation here
407 # is to prevent your users (or your users' viruses) from mounting certain
408 # kinds of attack on remote sites.
410 deny message = Restricted characters in address
411 domains = !+local_domains
412 local_parts = ^[.|] : ^.*[@%!] : ^.*/\\.\\./
413 #############################################################################
415 # Accept mail to postmaster in any local domain, regardless of the source,
416 # and without verifying the sender.
418 accept local_parts = postmaster
419 domains = +local_domains
421 # Deny unless the sender address can be verified.
423 require verify = sender
425 # Accept if the message comes from one of the hosts for which we are an
426 # outgoing relay. It is assumed that such hosts are most likely to be MUAs,
427 # so we set control=submission to make Exim treat the message as a
428 # submission. It will fix up various errors in the message, for example, the
429 # lack of a Date: header line. If you are actually relaying out out from
430 # MTAs, you may want to disable this. If you are handling both relaying from
431 # MTAs and submissions from MUAs you should probably split them into two
432 # lists, and handle them differently.
434 # Recipient verification is omitted here, because in many cases the clients
435 # are dumb MUAs that don't cope well with SMTP error responses. If you are
436 # actually relaying out from MTAs, you should probably add recipient
439 # Note that, by putting this test before any DNS black list checks, you will
440 # always accept from these hosts, even if they end up on a black list. The
441 # assumption is that they are your friends, and if they get onto a black
442 # list, it is a mistake.
444 accept hosts = +relay_from_hosts
446 control = dkim_disable_verify
448 # Accept if the message arrived over an authenticated connection, from
449 # any host. Again, these messages are usually from MUAs, so recipient
450 # verification is omitted, and submission mode is set. And again, we do this
451 # check before any black list tests.
453 accept authenticated = *
455 control = dkim_disable_verify
457 # Insist that a HELO/EHLO was accepted.
459 require message = nice hosts say HELO first
460 condition = ${if def:sender_helo_name}
462 # Insist that any other recipient address that we accept is either in one of
463 # our local domains, or is in a domain for which we explicitly allow
464 # relaying. Any other domain is rejected as being unacceptable for relaying.
466 require message = relay not permitted
467 domains = +local_domains : +relay_to_domains
469 # We also require all accepted addresses to be verifiable. This check will
470 # do local part verification for local domains, but only check the domain
471 # for remote domains. The only way to check local parts for the remote
472 # relay domains is to use a callout (add /callout), but please read the
473 # documentation about callouts before doing this.
475 require verify = recipient
477 #############################################################################
478 # There are no default checks on DNS black lists because the domains that
479 # contain these lists are changing all the time. However, here are two
480 # examples of how you can get Exim to perform a DNS black list lookup at this
481 # point. The first one denies, whereas the second just warns.
483 # deny message = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
484 # dnslists = black.list.example
486 # warn dnslists = black.list.example
487 # add_header = X-Warning: $sender_host_address is in a black list at $dnslist_domain
488 # log_message = found in $dnslist_domain
489 #############################################################################
491 #############################################################################
492 # This check is commented out because it is recognized that not every
493 # sysadmin will want to do it. If you enable it, the check performs
494 # Client SMTP Authorization (csa) checks on the sending host. These checks
495 # do DNS lookups for SRV records. The CSA proposal is currently (May 2005)
496 # an Internet draft. You can, of course, add additional conditions to this
497 # ACL statement to restrict the CSA checks to certain hosts only.
499 # require verify = csa
500 #############################################################################
502 # At this point, the address has passed all the checks that have been
503 # configured, so we accept it unconditionally.
508 # This ACL is used after the contents of a message have been received. This
509 # is the ACL in which you can test a message's headers or body, and in
510 # particular, this is where you can invoke external virus or spam scanners.
511 # Some suggested ways of configuring these tests are shown below, commented
512 # out. Without any tests, this ACL accepts all messages. If you want to use
513 # such tests, you must ensure that Exim is compiled with the content-scanning
514 # extension (WITH_CONTENT_SCAN=yes in Local/Makefile).
518 # Deny if the message contains an overlong line. Per the standards
519 # we should never receive one such via SMTP.
521 deny condition = ${if > {$max_received_linelength}{998}}
523 # Deny if the message contains a virus. Before enabling this check, you
524 # must install a virus scanner and set the av_scanner option above.
527 # message = This message contains a virus ($malware_name).
529 # Add headers to a message if it is judged to be spam. Before enabling this,
530 # you must install SpamAssassin. You may also need to set the spamd_address
534 # add_header = X-Spam_score: $spam_score\n\
535 # X-Spam_score_int: $spam_score_int\n\
536 # X-Spam_bar: $spam_bar\n\
537 # X-Spam_report: $spam_report
539 # Accept the message.
545 ######################################################################
546 # ROUTERS CONFIGURATION #
547 # Specifies how addresses are handled #
548 ######################################################################
549 # THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
550 # An address is passed to each router in turn until it is accepted. #
551 ######################################################################
555 # This router routes to remote hosts over SMTP by explicit IP address,
556 # when an email address is given in "domain literal" form, for example,
557 # <user@[192.168.35.64]>. The RFCs require this facility. However, it is
558 # little-known these days, and has been exploited by evil people seeking
559 # to abuse SMTP relays. Consequently it is commented out in the default
560 # configuration. If you uncomment this router, you also need to uncomment
561 # allow_domain_literals above, so that Exim can recognize the syntax of
562 # domain literal addresses.
566 # domains = ! +local_domains
567 # transport = remote_smtp
570 # This router routes addresses that are not in local domains by doing a DNS
571 # lookup on the domain name. The exclamation mark that appears in "domains = !
572 # +local_domains" is a negating operator, that is, it can be read as "not". The
573 # recipient's domain must not be one of those defined by "domainlist
574 # local_domains" above for this router to be used.
576 # If the router is used, any domain that resolves to 0.0.0.0 or to a loopback
577 # interface address (127.0.0.0/8) is treated as if it had no DNS entry. Note
578 # that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated as the
579 # local host inside the network stack. It is not 0.0.0.0/0, the default route.
580 # If the DNS lookup fails, no further routers are tried because of the no_more
581 # setting, and consequently the address is unrouteable.
585 domains = ! +local_domains
586 transport = remote_smtp
587 ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
588 # if ipv6-enabled then instead use:
589 # ignore_target_hosts = <; 0.0.0.0 ; 127.0.0.0/8 ; ::1
593 # This alternative router can be used when you want to send all mail to a
594 # server which handles DNS lookups for you; an ISP will typically run such
595 # a server for their customers. If you uncomment "smarthost" then you
596 # should comment out "dnslookup" above. Setting a real hostname in route_data
597 # wouldn't hurt either.
600 # driver = manualroute
601 # domains = ! +local_domains
602 # transport = remote_smtp
603 # route_data = MAIL.HOSTNAME.FOR.CENTRAL.SERVER.EXAMPLE
604 # ignore_target_hosts = <; 0.0.0.0 ; 127.0.0.0/8 ; ::1
608 # The remaining routers handle addresses in the local domain(s), that is those
609 # domains that are defined by "domainlist local_domains" above.
612 # This router handles aliasing using a linearly searched alias file with the
613 # name /etc/mail/aliases. When this configuration is installed automatically,
614 # the name gets inserted into this file from whatever is set in Exim's
615 # build-time configuration. The default path is the traditional /etc/aliases.
616 # If you install this configuration by hand, you need to specify the correct
617 # path in the "data" setting below.
619 ##### NB You must ensure that the alias file exists. It used to be the case
620 ##### NB that every Unix had that file, because it was the Sendmail default.
621 ##### NB These days, there are systems that don't have it. Your aliases
622 ##### NB file should at least contain an alias for "postmaster".
624 # If any of your aliases expand to pipes or files, you will need to set
625 # up a user and a group for these deliveries to run under. You can do
626 # this by uncommenting the "user" option below (changing the user name
627 # as appropriate) and adding a "group" option if necessary. Alternatively, you
628 # can specify "user" on the transports that are used. Note that the transports
629 # listed below are the same as are used for .forward files; you might want
630 # to set up different ones for pipe and file deliveries from aliases.
636 data = ${lookup{$local_part}lsearch{/etc/mail/aliases}}
638 file_transport = address_file
639 pipe_transport = address_pipe
642 # This router handles forwarding using traditional .forward files in users'
643 # home directories. If you want it also to allow mail filtering when a forward
644 # file starts with the string "# Exim filter" or "# Sieve filter", uncomment
645 # the "allow_filter" option.
647 # The no_verify setting means that this router is skipped when Exim is
648 # verifying addresses. Similarly, no_expn means that this router is skipped if
649 # Exim is processing an EXPN command.
651 # If you want this router to treat local parts with suffixes introduced by "-"
652 # or "+" characters as if the suffixes did not exist, uncomment the two local_
653 # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
654 # in the same way as xxxx@your.domain by this router. Because this router is
655 # not used for verification, if you choose to uncomment those options, then you
656 # will *need* to make the same change to the localuser router. (There are
657 # other approaches, if this is undesirable, but they add complexity).
659 # The check_ancestor option means that if the forward file generates an
660 # address that is an ancestor of the current one, the current one gets
661 # passed on instead. This covers the case where A is aliased to B and B
662 # has a .forward file pointing to A.
664 # The three transports specified at the end are those that are used when
665 # forwarding generates a direct delivery to a file, or to a pipe, or sets
666 # up an auto-reply, respectively.
671 # local_part_suffix = +* : -*
672 # local_part_suffix_optional
673 file = $home/.forward
678 file_transport = address_file
679 pipe_transport = address_pipe
680 reply_transport = address_reply
682 # Procmail. Uncomment following if you want procmail delivery.
687 # local_part_suffix = DSUFFIX*
688 # local_part_suffix_optional
689 # require_files = "${local_part}:+${home}/.procmailrc:\
690 # +/usr/bin/procmail:!${home}/.forward"
691 # transport = procmail_pipe
693 # This router matches local user mailboxes. If the router fails, the error
694 # message is "Unknown user".
696 # If you want this router to treat local parts with suffixes introduced by "-"
697 # or "+" characters as if the suffixes did not exist, uncomment the two local_
698 # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
699 # in the same way as xxxx@your.domain by this router.
704 # local_part_suffix = +* : -*
705 # local_part_suffix_optional
706 transport = local_delivery
707 cannot_route_message = Unknown user
711 ######################################################################
712 # TRANSPORTS CONFIGURATION #
713 ######################################################################
714 # ORDER DOES NOT MATTER #
715 # Only one appropriate transport is called for each delivery. #
716 ######################################################################
718 # A transport is used only when referenced from a router that successfully
719 # handles an address.
724 # This transport is used for delivering messages over SMTP connections.
725 # Refuse to send any message with over-long lines, which could have
726 # been received other than via SMTP. The use of message_size_limit to
727 # enforce this is a red herring.
731 message_size_limit = ${if > {$max_received_linelength}{998} {1}{0}}
734 # This transport is used for local delivery to user mailboxes in traditional
735 # BSD mailbox format. By default it will be run under the uid and gid of the
736 # local user, and requires the sticky bit to be set on the /var/mail directory.
737 # Some systems use the alternative approach of running mail deliveries under a
738 # particular group instead of using the sticky bit. The commented options below
739 # show how this can be done.
743 file = /var/mail/$local_part
751 # This transport is used for handling pipe deliveries generated by alias or
752 # .forward files. If the pipe generates any standard output, it is returned
753 # to the sender of the message as a delivery error. Set return_fail_output
754 # instead of return_output if you want this to happen only when the pipe fails
755 # to complete normally. You can set different transports for aliases and
756 # forwards if you want to - see the references to address_pipe in the routers
764 # This transport is used for handling deliveries directly to files that are
765 # generated by aliasing or forwarding.
774 # This transport is used for handling autoreplies generated by the filtering
775 # option of the userforward router.
782 ######################################################################
783 # RETRY CONFIGURATION #
784 ######################################################################
788 # This single retry rule applies to all domains and all errors. It specifies
789 # retries every 15 minutes for 2 hours, then increasing retry intervals,
790 # starting at 1 hour and increasing each time by a factor of 1.5, up to 16
791 # hours, then retries every 6 hours until 4 days have passed since the first
794 # WARNING: If you do not have any retry rules at all (this section of the
795 # configuration is non-existent or empty), Exim will not do any retries of
796 # messages that fail to get delivered at the first attempt. The effect will
797 # be to treat temporary errors as permanent. Therefore, DO NOT remove this
798 # retry rule unless you really don't want any retries.
800 # Address or Domain Error Retries
801 # ----------------- ----- -------
803 * * F,2h,15m; G,16h,1h,1.5; F,4d,6h
807 ######################################################################
808 # REWRITE CONFIGURATION #
809 ######################################################################
811 # There are no rewriting specifications in this default configuration file.
817 ######################################################################
818 # AUTHENTICATION CONFIGURATION #
819 ######################################################################
821 # The following authenticators support plaintext username/password
822 # authentication using the standard PLAIN mechanism and the traditional
823 # but non-standard LOGIN mechanism, with Exim acting as the server.
824 # PLAIN and LOGIN are enough to support most MUA software.
826 # These authenticators are not complete: you need to change the
827 # server_condition settings to specify how passwords are verified.
828 # They are set up to offer authentication to the client only if the
829 # connection is encrypted with TLS, so you also need to add support
830 # for TLS. See the global configuration options section at the start
831 # of this file for more about TLS.
833 # The default RCPT ACL checks for successful authentication, and will accept
834 # messages from authenticated users from anywhere on the Internet.
838 # PLAIN authentication has no server prompts. The client sends its
839 # credentials in one lump, containing an authorization ID (which we do not
840 # use), an authentication ID, and a password. The latter two appear as
841 # $auth2 and $auth3 in the configuration and should be checked against a
842 # valid username and password. In a real configuration you would typically
843 # use $auth2 as a lookup key, and compare $auth3 against the result of the
844 # lookup, perhaps using the crypteq{}{} condition.
848 # server_set_id = $auth2
850 # server_condition = Authentication is not yet configured
851 # server_advertise_condition = ${if def:tls_in_cipher }
853 # LOGIN authentication has traditional prompts and responses. There is no
854 # authorization ID in this mechanism, so unlike PLAIN the username and
855 # password are $auth1 and $auth2. Apart from that you can use the same
856 # server_condition setting for both authenticators.
860 # server_set_id = $auth1
861 # server_prompts = <| Username: | Password:
862 # server_condition = Authentication is not yet configured
863 # server_advertise_condition = ${if def:tls_in_cipher }
866 ######################################################################
867 # CONFIGURATION FOR local_scan() #
868 ######################################################################
870 # If you have built Exim to include a local_scan() function that contains
871 # tables for private options, you can define those options here. Remember to
872 # uncomment the "begin" line. It is commented by default because it provokes
873 # an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
874 # set in the Local/Makefile.
879 # End of Exim configuration file