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 website.
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 ######################################################################
42 ######################################################################
45 # If you want to use a smarthost instead of sending directly to recipient
46 # domains, uncomment this macro definition and set a real hostname.
47 # An appropriately privileged user can then redirect email on the command-line
48 # in emergencies, via -D.
50 # ROUTER_SMARTHOST=MAIL.HOSTNAME.FOR.CENTRAL.SERVER.EXAMPLE
52 ######################################################################
53 # MAIN CONFIGURATION SETTINGS #
54 ######################################################################
57 # Specify your host's canonical name here. This should normally be the fully
58 # qualified "official" name of your host. If this option is not set, the
59 # uname() function is called to obtain the name. In many cases this does
60 # the right thing and you need not set anything explicitly.
65 # The next three settings create two lists of domains and one list of hosts.
66 # These lists are referred to later in this configuration using the syntax
67 # +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
68 # are all colon-separated lists:
70 domainlist local_domains = @
71 domainlist relay_to_domains =
72 hostlist relay_from_hosts = localhost
73 # (We rely upon hostname resolution working for localhost, because the default
74 # uncommented configuration needs to work in IPv4-only environments.)
76 # Most straightforward access control requirements can be obtained by
77 # appropriate settings of the above options. In more complicated situations,
78 # you may need to modify the Access Control Lists (ACLs) which appear later in
81 # The first setting specifies your local domains, for example:
83 # domainlist local_domains = my.first.domain : my.second.domain
85 # You can use "@" to mean "the name of the local host", as in the default
86 # setting above. This is the name that is specified by primary_hostname,
87 # as specified above (or defaulted). If you do not want to do any local
88 # deliveries, remove the "@" from the setting above. If you want to accept mail
89 # addressed to your host's literal IP address, for example, mail addressed to
90 # "user@[192.168.23.44]", you can add "@[]" as an item in the local domains
91 # list. You also need to uncomment "allow_domain_literals" below. This is not
92 # recommended for today's Internet.
94 # The second setting specifies domains for which your host is an incoming relay.
95 # If you are not doing any relaying, you should leave the list empty. However,
96 # if your host is an MX backup or gateway of some kind for some domains, you
97 # must set relay_to_domains to match those domains. For example:
99 # domainlist relay_to_domains = *.myco.com : my.friend.org
101 # This will allow any host to relay through your host to those domains.
102 # See the section of the manual entitled "Control of relaying" for more
105 # The third setting specifies hosts that can use your host as an outgoing relay
106 # to any other host on the Internet. Such a setting commonly refers to a
107 # complete local network as well as the localhost. For example:
109 # hostlist relay_from_hosts = <; 127.0.0.1 ; ::1 ; 192.168.0.0/16
111 # The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
112 # have to include 127.0.0.1 if you want to allow processes on your host to send
113 # SMTP mail by using the loopback address. A number of MUAs use this method of
114 # sending mail. Often, connections are made to "localhost", which might be ::1
115 # on IPv6-enabled hosts. Do not forget CIDR for your IPv6 networks.
117 # All three of these lists may contain many different kinds of item, including
118 # wildcarded names, regular expressions, and file lookups. See the reference
119 # manual for details. The lists above are used in the access control lists for
120 # checking incoming messages. The names of these ACLs are defined here:
122 acl_smtp_rcpt = acl_check_rcpt
124 acl_smtp_data_prdr = acl_check_prdr
126 acl_smtp_data = acl_check_data
128 # You should not change those settings until you understand how ACLs work.
131 # If you are running a version of Exim that was compiled with the content-
132 # scanning extension, you can cause incoming messages to be automatically
133 # scanned for viruses. You have to modify the configuration in two places to
134 # set this up. The first of them is here, where you define the interface to
135 # your scanner. This example is typical for ClamAV; see the manual for details
136 # of what to set for other virus scanners. The second modification is in the
137 # acl_check_data access control list (see below).
139 # av_scanner = clamd:/tmp/clamd
142 # For spam scanning, there is a similar option that defines the interface to
143 # SpamAssassin. You do not need to set this if you are using the default, which
144 # is shown in this commented example. As for virus scanning, you must also
145 # modify the acl_check_data access control list to enable spam scanning.
147 # spamd_address = 127.0.0.1 783
150 # If Exim is compiled with support for TLS, you may want to enable the
151 # following options so that Exim allows clients to make encrypted
152 # connections. In the authenticators section below, there are template
153 # configurations for plaintext username/password authentication. This kind
154 # of authentication is only safe when used within a TLS connection, so the
155 # authenticators will only work if the following TLS settings are turned on
158 # Allow any client to use TLS.
160 # tls_advertise_hosts = *
162 # Specify the location of the Exim server's TLS certificate and private key.
163 # The private key must not be encrypted (password protected). You can put
164 # the certificate and private key in the same file, in which case you only
165 # need the first setting, or in separate files, in which case you need both
168 # tls_certificate = /etc/ssl/exim.crt
169 # tls_privatekey = /etc/ssl/exim.pem
171 # For OpenSSL, prefer EC- over RSA-authenticated ciphers
172 # tls_require_ciphers = ECDSA:RSA:!COMPLEMENTOFDEFAULT
174 # In order to support roaming users who wish to send email from anywhere,
175 # you may want to make Exim listen on other ports as well as port 25, in
176 # case these users need to send email from a network that blocks port 25.
177 # The standard port for this purpose is port 587, the "message submission"
178 # port. See RFC 4409 for details. Microsoft MUAs cannot be configured to
179 # talk the message submission protocol correctly, so if you need to support
180 # them you should also allow TLS-on-connect on the traditional but
181 # non-standard port 465.
183 # daemon_smtp_ports = 25 : 465 : 587
184 # tls_on_connect_ports = 465
187 # Specify the domain you want to be added to all unqualified addresses
188 # here. An unqualified address is one that does not contain an "@" character
189 # followed by a domain. For example, "caesar@rome.example" is a fully qualified
190 # address, but the string "caesar" (i.e. just a login name) is an unqualified
191 # email address. Unqualified addresses are accepted only from local callers by
192 # default. See the recipient_unqualified_hosts option if you want to permit
193 # unqualified addresses from remote sources. If this option is not set, the
194 # primary_hostname value is used for qualification.
199 # If you want unqualified recipient addresses to be qualified with a different
200 # domain to unqualified sender addresses, specify the recipient domain here.
201 # If this option is not set, the qualify_domain value is used.
203 # qualify_recipient =
206 # The following line must be uncommented if you want Exim to recognize
207 # addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
208 # (an IP address) instead of a named domain. The RFCs still require this form,
209 # but it makes little sense to permit mail to be sent to specific hosts by
210 # their IP address in the modern Internet. This ancient format has been used
211 # by those seeking to abuse hosts by using them for unwanted relaying. If you
212 # really do want to support domain literals, uncomment the following line, and
213 # see also the "domain_literal" router below.
215 # allow_domain_literals
218 # No deliveries will ever be run under the uids of users specified by
219 # never_users (a colon-separated list). An attempt to do so causes a panic
220 # error to be logged, and the delivery to be deferred. This is a paranoic
221 # safety catch. There is an even stronger safety catch in the form of the
222 # FIXED_NEVER_USERS setting in the configuration for building Exim. The list of
223 # users that it specifies is built into the binary, and cannot be changed. The
224 # option below just adds additional users to the list. The default for
225 # FIXED_NEVER_USERS is "root", but just to be absolutely sure, the default here
228 # Note that the default setting means you cannot deliver mail addressed to root
229 # as if it were a normal user. This isn't usually a problem, as most sites have
230 # an alias for root that redirects such mail to a human administrator.
235 # The setting below causes Exim to do a reverse DNS lookup on all incoming
236 # IP calls, in order to get the true host name. If you feel this is too
237 # expensive, you can specify the networks for which a lookup is done, or
238 # remove the setting entirely.
243 # The setting below causes Exim to try to initialize the system resolver
244 # library with DNSSEC support. It has no effect if your library lacks
250 # The settings below cause Exim to make RFC 1413 (ident) callbacks
251 # for all incoming SMTP calls. You can limit the hosts to which these
252 # calls are made, and/or change the timeout that is used. If you set
253 # the timeout to zero, all RFC 1413 calls are disabled. RFC 1413 calls
254 # are cheap and can provide useful information for tracing problem
255 # messages, but some hosts and firewalls have problems with them.
256 # This can result in a timeout instead of an immediate refused
257 # connection, leading to delays on starting up SMTP sessions.
258 # (The default was reduced from 30s to 5s for release 4.61. and to
259 # disabled for release 4.86)
262 #rfc1413_query_timeout = 5s
265 # Enable an efficiency feature. We advertise the feature; clients
266 # may request to use it. For multi-recipient mails we then can
267 # reject or accept per-user after the message is received.
268 # This supports recipient-dependent content filtering; without it
269 # you have to temp-reject any recipients after the first that have
270 # incompatible filtering, and do the filtering in the data ACL.
271 # Even with this enabled, you must support the old style for peers
272 # not flagging support for PRDR (visible via $prdr_requested).
279 # By default, Exim expects all envelope addresses to be fully qualified, that
280 # is, they must contain both a local part and a domain. If you want to accept
281 # unqualified addresses (just a local part) from certain hosts, you can specify
282 # these hosts by setting one or both of
284 # sender_unqualified_hosts =
285 # recipient_unqualified_hosts =
287 # to control sender and recipient addresses, respectively. When this is done,
288 # unqualified addresses are qualified using the settings of qualify_domain
289 # and/or qualify_recipient (see above).
292 # Unless you run a high-volume site you probably want more logging
293 # detail than the default. Adjust to suit.
295 log_selector = +smtp_protocol_error +smtp_syntax_error \
296 +tls_certificate_verified
299 # If you want Exim to support the "percent hack" for certain domains,
300 # uncomment the following line and provide a list of domains. The "percent
301 # hack" is the feature by which mail addressed to x%y@z (where z is one of
302 # the domains listed) is locally rerouted to x@y and sent on. If z is not one
303 # of the "percent hack" domains, x%y is treated as an ordinary local part. This
304 # hack is rarely needed nowadays; you should not enable it unless you are sure
305 # that you really need it.
307 # percent_hack_domains =
309 # As well as setting this option you will also need to remove the test
310 # for local parts containing % in the ACL definition below.
313 # When Exim can neither deliver a message nor return it to sender, it "freezes"
314 # the delivery error message (aka "bounce message"). There are also other
315 # circumstances in which messages get frozen. They will stay on the queue for
316 # ever unless one of the following options is set.
318 # This option unfreezes frozen bounce messages after two days, tries
319 # once more to deliver them, and ignores any delivery failures.
321 ignore_bounce_errors_after = 2d
323 # This option cancels (removes) frozen messages that are older than a week.
325 timeout_frozen_after = 7d
328 # By default, messages that are waiting on Exim's queue are all held in a
329 # single directory called "input" which is itself within Exim's spool
330 # directory. (The default spool directory is specified when Exim is built, and
331 # is often /var/spool/exim/.) Exim works best when its queue is kept short, but
332 # there are circumstances where this is not always possible. If you uncomment
333 # the setting below, messages on the queue are held in 62 subdirectories of
334 # "input" instead of all in the same directory. The subdirectories are called
335 # 0, 1, ... A, B, ... a, b, ... z. This has two benefits: (1) If your file
336 # system degrades with many files in one directory, this is less likely to
337 # happen; (2) Exim can process the queue one subdirectory at a time instead of
338 # all at once, which can give better performance with large queues.
340 # split_spool_directory = true
343 # If you're in a part of the world where ASCII is not sufficient for most
344 # text, then you're probably familiar with RFC2047 message header extensions.
345 # By default, Exim adheres to the specification, including a limit of 76
346 # characters to a line, with encoded words fitting within a line.
347 # If you wish to use decoded headers in message filters in such a way
348 # that successful decoding of malformed messages matters, you may wish to
349 # configure Exim to be more lenient.
351 # check_rfc2047_length = false
353 # In particular, the Exim maintainers have had multiple reports of problems
354 # from Russian administrators of issues until they disable this check,
355 # because of some popular, yet buggy, mail composition software.
358 # If you wish to be strictly RFC compliant, or if you know you'll be
359 # exchanging email with systems that are not 8-bit clean, then you may
360 # wish to disable advertising 8BITMIME. Uncomment this option to do so.
362 # accept_8bitmime = false
365 # Exim does not make use of environment variables itself. However,
366 # libraries that Exim uses (e.g. LDAP) depend on specific environment settings.
367 # There are two lists: keep_environment for the variables we trust, and
368 # add_environment for variables we want to set to a specific value.
369 # Note that TZ is handled separately by the timezone runtime option
370 # and TIMEZONE_DEFAULT buildtime option.
372 # keep_environment = ^LDAP
373 # add_environment = PATH=/usr/bin::/bin
377 ######################################################################
378 # ACL CONFIGURATION #
379 # Specifies access control lists for incoming SMTP mail #
380 ######################################################################
384 # This access control list is used for every RCPT command in an incoming
385 # SMTP message. The tests are run in order until the address is either
386 # accepted or denied.
390 # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
391 # testing for an empty sending host field.
394 control = dkim_disable_verify
396 #############################################################################
397 # The following section of the ACL is concerned with local parts that contain
398 # @ or % or ! or / or | or dots in unusual places.
400 # The characters other than dots are rarely found in genuine local parts, but
401 # are often tried by people looking to circumvent relaying restrictions.
402 # Therefore, although they are valid in local parts, these rules lock them
403 # out, as a precaution.
405 # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
406 # allows them because they have been encountered. (Consider local parts
407 # constructed as "firstinitial.secondinitial.familyname" when applied to
408 # someone like me, who has no second initial.) However, a local part starting
409 # with a dot or containing /../ can cause trouble if it is used as part of a
410 # file name (e.g. for a mailing list). This is also true for local parts that
411 # contain slashes. A pipe symbol can also be troublesome if the local part is
412 # incorporated unthinkingly into a shell command line.
414 # Two different rules are used. The first one is stricter, and is applied to
415 # messages that are addressed to one of the local domains handled by this
416 # host. The line "domains = +local_domains" restricts it to domains that are
417 # defined by the "domainlist local_domains" setting above. The rule blocks
418 # local parts that begin with a dot or contain @ % ! / or |. If you have
419 # local accounts that include these characters, you will have to modify this
422 deny message = Restricted characters in address
423 domains = +local_domains
424 local_parts = ^[.] : ^.*[@%!/|]
426 # The second rule applies to all other domains, and is less strict. The line
427 # "domains = !+local_domains" restricts it to domains that are NOT defined by
428 # the "domainlist local_domains" setting above. The exclamation mark is a
429 # negating operator. This rule allows your own users to send outgoing
430 # messages to sites that use slashes and vertical bars in their local parts.
431 # It blocks local parts that begin with a dot, slash, or vertical bar, but
432 # allows these characters within the local part. However, the sequence /../
433 # is barred. The use of @ % and ! is blocked, as before. The motivation here
434 # is to prevent your users (or your users' viruses) from mounting certain
435 # kinds of attack on remote sites.
437 deny message = Restricted characters in address
438 domains = !+local_domains
439 local_parts = ^[./|] : ^.*[@%!] : ^.*/\\.\\./
440 #############################################################################
442 # Accept mail to postmaster in any local domain, regardless of the source,
443 # and without verifying the sender.
445 accept local_parts = postmaster
446 domains = +local_domains
448 # Deny unless the sender address can be verified.
450 require verify = sender
452 # Reject all RCPT commands after too many bad recipients
453 # This is partly a defense against spam abuse and partly attacker abuse.
454 # Real senders should manage, by the time they get to 10 RCPT directives,
455 # to have had at least half of them be real addresses.
457 # This is a lightweight check and can protect you against repeated
458 # invocations of more heavy-weight checks which would come after it.
460 deny condition = ${if and {\
461 {>{$rcpt_count}{10}}\
462 {<{$recipients_count}{${eval:$rcpt_count/2}}} }}
463 message = Rejected for too many bad recipients
464 logwrite = REJECT [$sender_host_address]: bad recipient count high [${eval:$rcpt_count-$recipients_count}]
466 # Accept if the message comes from one of the hosts for which we are an
467 # outgoing relay. It is assumed that such hosts are most likely to be MUAs,
468 # so we set control=submission to make Exim treat the message as a
469 # submission. It will fix up various errors in the message, for example, the
470 # lack of a Date: header line. If you are actually relaying out out from
471 # MTAs, you may want to disable this. If you are handling both relaying from
472 # MTAs and submissions from MUAs you should probably split them into two
473 # lists, and handle them differently.
475 # Recipient verification is omitted here, because in many cases the clients
476 # are dumb MUAs that don't cope well with SMTP error responses. If you are
477 # actually relaying out from MTAs, you should probably add recipient
480 # Note that, by putting this test before any DNS black list checks, you will
481 # always accept from these hosts, even if they end up on a black list. The
482 # assumption is that they are your friends, and if they get onto a black
483 # list, it is a mistake.
485 accept hosts = +relay_from_hosts
487 control = dkim_disable_verify
489 # Accept if the message arrived over an authenticated connection, from
490 # any host. Again, these messages are usually from MUAs, so recipient
491 # verification is omitted, and submission mode is set. And again, we do this
492 # check before any black list tests.
494 accept authenticated = *
496 control = dkim_disable_verify
498 # Insist that a HELO/EHLO was accepted.
500 require message = nice hosts say HELO first
501 condition = ${if def:sender_helo_name}
503 # Insist that any other recipient address that we accept is either in one of
504 # our local domains, or is in a domain for which we explicitly allow
505 # relaying. Any other domain is rejected as being unacceptable for relaying.
507 require message = relay not permitted
508 domains = +local_domains : +relay_to_domains
510 # We also require all accepted addresses to be verifiable. This check will
511 # do local part verification for local domains, but only check the domain
512 # for remote domains. The only way to check local parts for the remote
513 # relay domains is to use a callout (add /callout), but please read the
514 # documentation about callouts before doing this.
516 require verify = recipient
518 #############################################################################
519 # There are no default checks on DNS black lists because the domains that
520 # contain these lists are changing all the time. However, here are two
521 # examples of how you can get Exim to perform a DNS black list lookup at this
522 # point. The first one denies, whereas the second just warns.
524 # deny dnslists = black.list.example
525 # message = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
527 # warn dnslists = black.list.example
528 # add_header = X-Warning: $sender_host_address is in a black list at $dnslist_domain
529 # log_message = found in $dnslist_domain
530 #############################################################################
532 #############################################################################
533 # This check is commented out because it is recognized that not every
534 # sysadmin will want to do it. If you enable it, the check performs
535 # Client SMTP Authorization (csa) checks on the sending host. These checks
536 # do DNS lookups for SRV records. The CSA proposal is currently (May 2005)
537 # an Internet draft. You can, of course, add additional conditions to this
538 # ACL statement to restrict the CSA checks to certain hosts only.
540 # require verify = csa
541 #############################################################################
543 #############################################################################
544 # If doing per-user content filtering then recipients with filters different
545 # to the first recipient must be deferred unless the sender talks PRDR.
547 # defer !condition = $prdr_requested
548 # condition = ${if > {0}{$receipients_count}}
549 # condition = ${if !eq {$acl_m_content_filter} \
550 # {${lookup PER_RCPT_CONTENT_FILTER}}}
551 # warn !condition = $prdr_requested
552 # condition = ${if > {0}{$receipients_count}}
553 # set acl_m_content_filter = ${lookup PER_RCPT_CONTENT_FILTER}
554 #############################################################################
556 # At this point, the address has passed all the checks that have been
557 # configured, so we accept it unconditionally.
562 # This ACL is used once per recipient, for multi-recipient messages, if
563 # we advertised PRDR. It can be used to perform receipient-dependent
564 # header- and body- based filtering and rejections.
565 # We set a variable to record that PRDR was active used, so that checking
566 # in the data ACL can be skipped.
570 warn set acl_m_did_prdr = y
572 #############################################################################
573 # do lookup on filtering, with $local_part@$domain, deny on filter match
575 # deny set acl_m_content_filter = ${lookup PER_RCPT_CONTENT_FILTER}
577 #############################################################################
582 # This ACL is used after the contents of a message have been received. This
583 # is the ACL in which you can test a message's headers or body, and in
584 # particular, this is where you can invoke external virus or spam scanners.
585 # Some suggested ways of configuring these tests are shown below, commented
586 # out. Without any tests, this ACL accepts all messages. If you want to use
587 # such tests, you must ensure that Exim is compiled with the content-scanning
588 # extension (WITH_CONTENT_SCAN=yes in Local/Makefile).
592 # Deny if the message contains an overlong line. Per the standards
593 # we should never receive one such via SMTP.
595 deny condition = ${if > {$max_received_linelength}{998}}
596 message = maximum allowed line length is 998 octets, \
597 got $max_received_linelength
599 # Deny if the headers contain badly-formed addresses.
601 deny !verify = header_syntax
602 message = header syntax
603 log_message = header syntax ($acl_verify_message)
605 # Deny if the message contains a virus. Before enabling this check, you
606 # must install a virus scanner and set the av_scanner option above.
609 # message = This message contains a virus ($malware_name).
611 # Add headers to a message if it is judged to be spam. Before enabling this,
612 # you must install SpamAssassin. You may also need to set the spamd_address
616 # add_header = X-Spam_score: $spam_score\n\
617 # X-Spam_score_int: $spam_score_int\n\
618 # X-Spam_bar: $spam_bar\n\
619 # X-Spam_report: $spam_report
621 #############################################################################
622 # No more tests if PRDR was actively used.
623 # accept condition = ${if def:acl_m_did_prdr}
625 # To get here, all message recipients must have identical per-user
626 # content filtering (enforced by RCPT ACL). Do lookup for filter
629 # deny set acl_m_content_filter = ${lookup PER_RCPT_CONTENT_FILTER}
631 #############################################################################
634 # Accept the message.
640 ######################################################################
641 # ROUTERS CONFIGURATION #
642 # Specifies how addresses are handled #
643 ######################################################################
644 # THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
645 # An address is passed to each router in turn until it is accepted. #
646 ######################################################################
650 # This router routes to remote hosts over SMTP by explicit IP address,
651 # when an email address is given in "domain literal" form, for example,
652 # <user@[192.168.35.64]>. The RFCs require this facility. However, it is
653 # little-known these days, and has been exploited by evil people seeking
654 # to abuse SMTP relays. Consequently it is commented out in the default
655 # configuration. If you uncomment this router, you also need to uncomment
656 # allow_domain_literals above, so that Exim can recognize the syntax of
657 # domain literal addresses.
661 # domains = ! +local_domains
662 # transport = remote_smtp
665 # This router can be used when you want to send all mail to a
666 # server which handles DNS lookups for you; an ISP will typically run such
667 # a server for their customers. The hostname in route_data comes from the
668 # macro defined at the top of the file. If not defined, then we'll use the
669 # dnslookup router below instead.
670 # Beware that the hostname is specified again in the Transport.
672 .ifdef ROUTER_SMARTHOST
676 domains = ! +local_domains
677 transport = smarthost_smtp
678 route_data = ROUTER_SMARTHOST
679 ignore_target_hosts = <; 0.0.0.0 ; 127.0.0.0/8 ; ::1
684 # This router routes addresses that are not in local domains by doing a DNS
685 # lookup on the domain name. The exclamation mark that appears in "domains = !
686 # +local_domains" is a negating operator, that is, it can be read as "not". The
687 # recipient's domain must not be one of those defined by "domainlist
688 # local_domains" above for this router to be used.
690 # If the router is used, any domain that resolves to 0.0.0.0 or to a loopback
691 # interface address (127.0.0.0/8) is treated as if it had no DNS entry. Note
692 # that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated as the
693 # local host inside the network stack. It is not 0.0.0.0/0, the default route.
694 # If the DNS lookup fails, no further routers are tried because of the no_more
695 # setting, and consequently the address is unrouteable.
699 domains = ! +local_domains
700 transport = remote_smtp
701 ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
702 # if ipv6-enabled then instead use:
703 # ignore_target_hosts = <; 0.0.0.0 ; 127.0.0.0/8 ; ::1
706 # This closes the ROUTER_SMARTHOST ifdef around the choice of routing for
711 # The remaining routers handle addresses in the local domain(s), that is those
712 # domains that are defined by "domainlist local_domains" above.
715 # This router handles aliasing using a linearly searched alias file with the
716 # name SYSTEM_ALIASES_FILE. When this configuration is installed automatically,
717 # the name gets inserted into this file from whatever is set in Exim's
718 # build-time configuration. The default path is the traditional /etc/aliases.
719 # If you install this configuration by hand, you need to specify the correct
720 # path in the "data" setting below.
722 ##### NB You must ensure that the alias file exists. It used to be the case
723 ##### NB that every Unix had that file, because it was the Sendmail default.
724 ##### NB These days, there are systems that don't have it. Your aliases
725 ##### NB file should at least contain an alias for "postmaster".
727 # If any of your aliases expand to pipes or files, you will need to set
728 # up a user and a group for these deliveries to run under. You can do
729 # this by uncommenting the "user" option below (changing the user name
730 # as appropriate) and adding a "group" option if necessary. Alternatively, you
731 # can specify "user" on the transports that are used. Note that the transports
732 # listed below are the same as are used for .forward files; you might want
733 # to set up different ones for pipe and file deliveries from aliases.
739 data = ${lookup{$local_part}lsearch{SYSTEM_ALIASES_FILE}}
741 file_transport = address_file
742 pipe_transport = address_pipe
745 # This router handles forwarding using traditional .forward files in users'
746 # home directories. If you want it also to allow mail filtering when a forward
747 # file starts with the string "# Exim filter" or "# Sieve filter", uncomment
748 # the "allow_filter" option.
750 # The no_verify setting means that this router is skipped when Exim is
751 # verifying addresses. Similarly, no_expn means that this router is skipped if
752 # Exim is processing an EXPN command.
754 # If you want this router to treat local parts with suffixes introduced by "-"
755 # or "+" characters as if the suffixes did not exist, uncomment the two local_
756 # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
757 # in the same way as xxxx@your.domain by this router. Because this router is
758 # not used for verification, if you choose to uncomment those options, then you
759 # will *need* to make the same change to the localuser router. (There are
760 # other approaches, if this is undesirable, but they add complexity).
762 # The check_ancestor option means that if the forward file generates an
763 # address that is an ancestor of the current one, the current one gets
764 # passed on instead. This covers the case where A is aliased to B and B
765 # has a .forward file pointing to A.
767 # The three transports specified at the end are those that are used when
768 # forwarding generates a direct delivery to a file, or to a pipe, or sets
769 # up an auto-reply, respectively.
774 # local_part_suffix = +* : -*
775 # local_part_suffix_optional
776 file = $home/.forward
781 file_transport = address_file
782 pipe_transport = address_pipe
783 reply_transport = address_reply
786 # This router matches local user mailboxes. If the router fails, the error
787 # message is "Unknown user".
789 # If you want this router to treat local parts with suffixes introduced by "-"
790 # or "+" characters as if the suffixes did not exist, uncomment the two local_
791 # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
792 # in the same way as xxxx@your.domain by this router.
797 # local_part_suffix = +* : -*
798 # local_part_suffix_optional
799 transport = local_delivery
800 cannot_route_message = Unknown user
804 ######################################################################
805 # TRANSPORTS CONFIGURATION #
806 ######################################################################
807 # ORDER DOES NOT MATTER #
808 # Only one appropriate transport is called for each delivery. #
809 ######################################################################
811 # A transport is used only when referenced from a router that successfully
812 # handles an address.
817 # This transport is used for delivering messages over SMTP connections.
818 # Refuse to send any message with over-long lines, which could have
819 # been received other than via SMTP. The use of message_size_limit to
820 # enforce this is a red herring.
824 message_size_limit = ${if > {$max_received_linelength}{998} {1}{0}}
827 # This transport is used for delivering messages to a smarthost, if the
828 # smarthost router is enabled. This starts from the same basis as
829 # "remote_smtp" but then turns on various security options, because
830 # we assume that if you're told "use smarthost.example.org as the smarthost"
831 # then there will be TLS available, with a verifiable certificate for that
832 # hostname, using decent TLS.
836 message_size_limit = ${if > {$max_received_linelength}{998} {1}{0}}
840 # Comment out any of these which you have to, then file a Support
841 # request with your smarthost provider to get things fixed:
842 hosts_require_tls = *
844 # As long as tls_verify_hosts is enabled, this won't matter, but if you
845 # have to comment it out then this will at least log whether you succeed
847 tls_try_verify_hosts = *
849 # The SNI name should match the name which we'll expect to verify;
850 # many mail systems don't use SNI and this doesn't matter, but if it does,
851 # we need to send a name which the remote site will recognize.
852 # This _should_ be the name which the smarthost operators specified as
853 # the hostname for sending your mail to.
854 tls_sni = ROUTER_SMARTHOST
857 tls_require_ciphers = HIGH:!aNULL:@STRENGTH
860 tls_require_ciphers = SECURE192:-VERS-SSL3.0:-VERS-TLS1.0:-VERS-TLS1.1
865 # This transport is used for local delivery to user mailboxes in traditional
866 # BSD mailbox format. By default it will be run under the uid and gid of the
867 # local user, and requires the sticky bit to be set on the /var/mail directory.
868 # Some systems use the alternative approach of running mail deliveries under a
869 # particular group instead of using the sticky bit. The commented options below
870 # show how this can be done.
874 file = /var/mail/$local_part_data
882 # This transport is used for handling pipe deliveries generated by alias or
883 # .forward files. If the pipe generates any standard output, it is returned
884 # to the sender of the message as a delivery error. Set return_fail_output
885 # instead of return_output if you want this to happen only when the pipe fails
886 # to complete normally. You can set different transports for aliases and
887 # forwards if you want to - see the references to address_pipe in the routers
895 # This transport is used for handling deliveries directly to files that are
896 # generated by aliasing or forwarding.
905 # This transport is used for handling autoreplies generated by the filtering
906 # option of the userforward router.
913 ######################################################################
914 # RETRY CONFIGURATION #
915 ######################################################################
919 # This single retry rule applies to all domains and all errors. It specifies
920 # retries every 15 minutes for 2 hours, then increasing retry intervals,
921 # starting at 1 hour and increasing each time by a factor of 1.5, up to 16
922 # hours, then retries every 6 hours until 4 days have passed since the first
925 # WARNING: If you do not have any retry rules at all (this section of the
926 # configuration is non-existent or empty), Exim will not do any retries of
927 # messages that fail to get delivered at the first attempt. The effect will
928 # be to treat temporary errors as permanent. Therefore, DO NOT remove this
929 # retry rule unless you really don't want any retries.
931 # Address or Domain Error Retries
932 # ----------------- ----- -------
934 * * F,2h,15m; G,16h,1h,1.5; F,4d,6h
938 ######################################################################
939 # REWRITE CONFIGURATION #
940 ######################################################################
942 # There are no rewriting specifications in this default configuration file.
948 ######################################################################
949 # AUTHENTICATION CONFIGURATION #
950 ######################################################################
952 # The following authenticators support plaintext username/password
953 # authentication using the standard PLAIN mechanism and the traditional
954 # but non-standard LOGIN mechanism, with Exim acting as the server.
955 # PLAIN and LOGIN are enough to support most MUA software.
957 # These authenticators are not complete: you need to change the
958 # server_condition settings to specify how passwords are verified.
959 # They are set up to offer authentication to the client only if the
960 # connection is encrypted with TLS, so you also need to add support
961 # for TLS. See the global configuration options section at the start
962 # of this file for more about TLS.
964 # The default RCPT ACL checks for successful authentication, and will accept
965 # messages from authenticated users from anywhere on the Internet.
969 # PLAIN authentication has no server prompts. The client sends its
970 # credentials in one lump, containing an authorization ID (which we do not
971 # use), an authentication ID, and a password. The latter two appear as
972 # $auth2 and $auth3 in the configuration and should be checked against a
973 # valid username and password. In a real configuration you would typically
974 # use $auth2 as a lookup key, and compare $auth3 against the result of the
975 # lookup, perhaps using the crypteq{}{} condition.
979 # server_set_id = $auth2
981 # server_condition = Authentication is not yet configured
982 # server_advertise_condition = ${if def:tls_in_cipher }
984 # LOGIN authentication has traditional prompts and responses. There is no
985 # authorization ID in this mechanism, so unlike PLAIN the username and
986 # password are $auth1 and $auth2. Apart from that you can use the same
987 # server_condition setting for both authenticators.
991 # server_set_id = $auth1
992 # server_prompts = <| Username: | Password:
993 # server_condition = Authentication is not yet configured
994 # server_advertise_condition = ${if def:tls_in_cipher }
997 ######################################################################
998 # CONFIGURATION FOR local_scan() #
999 ######################################################################
1001 # If you have built Exim to include a local_scan() function that contains
1002 # tables for private options, you can define those options here. Remember to
1003 # uncomment the "begin" line. It is commented by default because it provokes
1004 # an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
1005 # set in the Local/Makefile.
1010 # End of Exim configuration file