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 ######################################################################
44 # Log more information
45 # log_selector = +all -arguments
46 log_selector = +smtp_confirmation +queue_time
48 # Specify your host's canonical name here. This should normally be the fully
49 # qualified "official" name of your host. If this option is not set, the
50 # uname() function is called to obtain the name. In many cases this does
51 # the right thing and you need not set anything explicitly.
55 # daemon_smtp_ports = 25 : 465
56 # tls_on_connect_ports = 465
58 # The next three settings create two lists of domains and one list of hosts.
59 # These lists are referred to later in this configuration using the syntax
60 # +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
61 # are all colon-separated lists:
63 domainlist local_domains = @
64 domainlist relay_to_domains =
65 hostlist relay_from_hosts = 127.0.0.1
67 # If You wish to enable support for STARTTLS, uncomment folowing lines:
69 # tls_certificate = /etc/openssl/mail.crt
70 # tls_privatekey = /etc/openssl/mail.key
71 # tls_advertise_hosts = *
73 # You can use self-signed cerficates (you will need openssl-tools package):
75 # openssl genrsa -out /etc/openssl/mail.key 1024
76 # openssl req -new -x509 -days 365 -key /etc/openssl/mail.key -out /etc/openssl/mail.crt
78 # Most straightforward access control requirements can be obtained by
79 # appropriate settings of the above options. In more complicated situations, you
80 # may need to modify the Access Control List (ACL) which appears later in this
83 # The first setting specifies your local domains, for example:
85 # domainlist local_domains = my.first.domain : my.second.domain
87 # You can use "@" to mean "the name of the local host", as in the default
88 # setting above. This is the name that is specified by primary_hostname,
89 # as specified above (or defaulted). If you do not want to do any local
90 # deliveries, remove the "@" from the setting above. If you want to accept mail
91 # addressed to your host's literal IP address, for example, mail addressed to
92 # "user@[192.168.23.44]", you can add "@[]" as an item in the local domains
93 # list. You also need to uncomment "allow_domain_literals" below. This is not
94 # recommended for today's Internet.
96 # The second setting specifies domains for which your host is an incoming relay.
97 # If you are not doing any relaying, you should leave the list empty. However,
98 # if your host is an MX backup or gateway of some kind for some domains, you
99 # must set relay_to_domains to match those domains. For example:
101 # domainlist relay_to_domains = *.myco.com : my.friend.org
103 # This will allow any host to relay through your host to those domains.
104 # See the section of the manual entitled "Control of relaying" for more
107 # The third setting specifies hosts that can use your host as an outgoing relay
108 # to any other host on the Internet. Such a setting commonly refers to a
109 # complete local network as well as the localhost. For example:
111 # hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16
113 # The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
114 # have to include 127.0.0.1 if you want to allow processes on your host to send
115 # SMTP mail by using the loopback address. A number of MUAs use this method of
119 # All three of these lists may contain many different kinds of item, including
120 # wildcarded names, regular expressions, and file lookups. See the reference
121 # manual for details. The lists above are used in the access control list for
122 # incoming messages. The name of this ACL is defined here:
124 acl_smtp_rcpt = acl_check_rcpt
126 # You should not change that setting until you understand how ACLs work.
128 # The following ACL entries are used if you want to do content scanning with
129 # the exiscan-acl patch. When you uncomment one of these lines, you must also
130 # review the respective entries in the ACL section further below.
132 # acl_smtp_mime = acl_check_mime
133 # acl_smtp_data = acl_check_content
135 # This configuration variable defines the virus scanner that is used with
136 # the 'malware' ACL condition of the exiscan acl-patch. If you do not use
137 # virus scanning, leave it commented. Please read doc/exiscan-acl-readme.txt
138 # for a list of supported scanners.
140 # av_scanner = sophie:/var/run/sophie
142 # The following setting is only needed if you use the 'spam' ACL condition
143 # of the exiscan-acl patch. It specifies on which host and port the SpamAssassin
144 # "spamd" daemon is listening. If you do not use this condition, or you use
145 # the default of "127.0.0.1 783", you can omit this option.
147 # spamd_address = 127.0.0.1 783
149 # Specify the domain you want to be added to all unqualified addresses
150 # here. An unqualified address is one that does not contain an "@" character
151 # followed by a domain. For example, "caesar@rome.example" is a fully qualified
152 # address, but the string "caesar" (i.e. just a login name) is an unqualified
153 # email address. Unqualified addresses are accepted only from local callers by
154 # default. See the recipient_unqualified_hosts option if you want to permit
155 # unqualified addresses from remote sources. If this option is not set, the
156 # primary_hostname value is used for qualification.
161 # If you want unqualified recipient addresses to be qualified with a different
162 # domain to unqualified sender addresses, specify the recipient domain here.
163 # If this option is not set, the qualify_domain value is used.
165 # qualify_recipient =
168 # The following line must be uncommented if you want Exim to recognize
169 # addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
170 # (an IP address) instead of a named domain. The RFCs still require this form,
171 # but it makes little sense to permit mail to be sent to specific hosts by
172 # their IP address in the modern Internet. This ancient format has been used
173 # by those seeking to abuse hosts by using them for unwanted relaying. If you
174 # really do want to support domain literals, uncomment the following line, and
175 # see also the "domain_literal" router below.
177 # allow_domain_literals
180 # No deliveries will ever be run under the uids of these users (a colon-
181 # separated list). An attempt to do so causes a panic error to be logged, and
182 # the delivery to be deferred. This is a paranoic safety catch. There is an
183 # even stronger safety catch in the form of the FIXED_NEVER_USERS setting
184 # in the configuration for building Exim. The list of users that it specifies
185 # is built into the binary, and cannot be changed. The option below just adds
186 # additional users to the list. The default for FIXED_NEVER_USERS is "root",
187 # but just to be absolutely sure, the default here is also "root".
189 # Note that the default setting means you cannot deliver mail addressed to root
190 # as if it were a normal user. This isn't usually a problem, as most sites have
191 # an alias for root that redirects such mail to a human administrator.
196 # The setting below causes Exim to do a reverse DNS lookup on all incoming
197 # IP calls, in order to get the true host name. If you feel this is too
198 # expensive, you can specify the networks for which a lookup is done, or
199 # remove the setting entirely.
203 # Advertise DSN for these hosts
205 dsn_advertise_hosts = *
207 # The settings below (default is 30s) cause Exim to make RFC 1413 (ident)
208 # callbacks for all incoming SMTP calls. You can limit the hosts to which
209 # these calls are made, and/or change # the timeout that is used.
210 # If you set the timeout to zero, all RFC 1413 calls
211 # are disabled. RFC 1413 calls are cheap and can provide useful information
212 # for tracing problem messages, but some hosts and firewalls have problems
213 # with them. This can result in a timeout instead of an immediate refused
214 # connection, leading to delays on starting up an SMTP session.
217 rfc1413_query_timeout = 3s
220 # By default, Exim expects all envelope addresses to be fully qualified, that
221 # is, they must contain both a local part and a domain. If you want to accept
222 # unqualified addresses (just a local part) from certain hosts, you can specify
223 # these hosts by setting one or both of
225 # sender_unqualified_hosts =
226 # recipient_unqualified_hosts =
228 # to control sender and recipient addresses, respectively. When this is done,
229 # unqualified addresses are qualified using the settings of qualify_domain
230 # and/or qualify_recipient (see above).
233 # If you want Exim to support the "percent hack" for certain domains,
234 # uncomment the following line and provide a list of domains. The "percent
235 # hack" is the feature by which mail addressed to x%y@z (where z is one of
236 # the domains listed) is locally rerouted to x@y and sent on. If z is not one
237 # of the "percent hack" domains, x%y is treated as an ordinary local part. This
238 # hack is rarely needed nowadays; you should not enable it unless you are sure
239 # that you really need it.
241 # percent_hack_domains =
243 # As well as setting this option you will also need to remove the test
244 # for local parts containing % in the ACL definition below.
247 # When Exim can neither deliver a message nor return it to sender, it "freezes"
248 # the delivery error message (aka "bounce message"). There are also other
249 # circumstances in which messages get frozen. They will stay on the queue for
250 # ever unless one of the following options is set.
252 # This option unfreezes frozen bounce messages after two days, tries
253 # once more to deliver them, and ignores any delivery failures.
255 ignore_bounce_errors_after = 2d
257 # This option cancels (removes) frozen messages that are older than a week.
259 timeout_frozen_after = 7d
263 ######################################################################
264 # ACL CONFIGURATION #
265 # Specifies access control lists for incoming SMTP mail #
266 ######################################################################
270 # This access control list is used for every RCPT command in an incoming
271 # SMTP message. The tests are run in order until the address is either
272 # accepted or denied.
276 # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
277 # testing for an empty sending host field.
281 #############################################################################
282 # The following section of the ACL is concerned with local parts that contain
283 # @ or % or ! or / or | or dots in unusual places.
285 # The characters other than dots are rarely found in genuine local parts, but
286 # are often tried by people looking to circumvent relaying restrictions.
287 # Therefore, although they are valid in local parts, these rules lock them
288 # out, as a precaution.
290 # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
291 # allows them because they have been encountered. (Consider local parts
292 # constructed as "firstinitial.secondinitial.familyname" when applied to
293 # someone like me, who has no second initial.) However, a local part starting
294 # with a dot or containing /../ can cause trouble if it is used as part of a
295 # file name (e.g. for a mailing list). This is also true for local parts that
296 # contain slashes. A pipe symbol can also be troublesome if the local part is
297 # incorporated unthinkingly into a shell command line.
299 # Two different rules are used. The first one is stricter, and is applied to
300 # messages that are addressed to one of the local domains handled by this
301 # host. It blocks local parts that begin with a dot or contain @ % ! / or |.
302 # If you have local accounts that include these characters, you will have to
305 deny message = Restricted characters in address
306 domains = +local_domains
307 local_parts = ^[.] : ^.*[@%!|]
309 # The second rule applies to all other domains, and is less strict. This
310 # allows your own users to send outgoing messages to sites that use slashes
311 # and vertical bars in their local parts. It blocks local parts that begin
312 # with a dot, slash, or vertical bar, but allows these characters within the
313 # local part. However, the sequence /../ is barred. The use of @ % and ! is
314 # blocked, as before. The motivation here is to prevent your users (or
315 # your users' viruses) from mounting certain kinds of attack on remote sites.
318 deny message = Restricted characters in address
319 domains = !+local_domains
320 local_parts = ^[.|] : ^.*[@%!] : ^.*/\\.\\./
321 #############################################################################
323 # Accept mail to postmaster in any local domain, regardless of the source,
324 # and without verifying the sender.
326 accept local_parts = postmaster
327 domains = +local_domains
329 # Deny unless the sender address can be verified.
331 require verify = sender
333 #############################################################################
334 # There are no checks on DNS "black" lists because the domains that contain
335 # these lists are changing all the time. However, here are two examples of
336 # how you could get Exim to perform a DNS black list lookup at this point.
337 # The first one denies, while the second just warns.
339 # deny message = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
340 # dnslists = black.list.example
342 # warn message = X-Warning: $sender_host_address is in a black list at $dnslist_domain
343 # log_message = found in $dnslist_domain
344 # dnslists = black.list.example
345 #############################################################################
347 # Accept if the address is in a local domain, but only if the recipient can
348 # be verified. Otherwise deny. The "endpass" line is the border between
349 # passing on to the next ACL statement (if tests above it fail) or denying
350 # access (if tests below it fail).
352 accept domains = +local_domains
356 # Accept if the address is in a domain for which we are relaying, but again,
357 # only if the recipient can be verified.
359 accept domains = +relay_to_domains
362 # If control reaches this point, the domain is neither in +local_domains
363 # nor in +relay_to_domains.
365 # Accept if the message comes from one of the hosts for which we are an
366 # outgoing relay. Recipient verification is omitted here, because in many
367 # cases the clients are dumb MUAs that don't cope well with SMTP error
368 # responses. If you are actually relaying out from MTAs, you should probably
369 # add recipient verification here.
371 accept hosts = +relay_from_hosts
373 # Accept if the message arrived over an authenticated connection, from
374 # any host. Again, these messages are usually from MUAs, so recipient
375 # verification is omitted.
377 accept authenticated = *
379 # Reaching the end of the ACL causes a "deny", but we might as well give
380 # an explicit message.
382 deny message = relay not permitted
384 # These access control lists are used for content scanning with the exiscan-acl
385 # patch. You must also uncomment the entries for acl_smtp_data and acl_smtp_mime
386 # (scroll up), otherwise the ACLs will not be used. IMPORTANT: the default entries here
387 # should be treated as EXAMPLES. You MUST read the file doc/exiscan-acl-spec.txt
388 # to fully understand what you are doing ...
392 # Decode MIME parts to disk. This will support virus scanners later.
393 warn decode = default
395 # File extension filtering.
396 deny message = Blacklisted file extension detected
397 condition = ${if match \
398 {${lc:$mime_filename}} \
399 {\N(\.exe|\.pif|\.bat|\.scr|\.lnk|\.com)$\N} \
402 # Reject messages that carry chinese character sets.
403 # WARNING: This is an EXAMPLE.
404 deny message = Sorry, noone speaks chinese here
405 condition = ${if eq{$mime_charset}{gb2312}{1}{0}}
411 # Reject virus infested messages.
412 deny message = This message contains malware ($malware_name)
415 # Always add X-Spam-Score and X-Spam-Report headers, using SA system-wide settings
416 # (user "nobody"), no matter if over threshold or not.
417 warn message = X-Spam-Score: $spam_score ($spam_bar)
419 warn message = X-Spam-Report: $spam_report
422 # Add X-Spam-Flag if spam is over system-wide threshold
423 warn message = X-Spam-Flag: YES
426 # Reject spam messages with score over 10, using an extra condition.
427 deny message = This message scored $spam_score points. Congratulations!
429 condition = ${if >{$spam_score_int}{100}{1}{0}}
431 # finally accept all the rest
435 ######################################################################
436 # ROUTERS CONFIGURATION #
437 # Specifies how addresses are handled #
438 ######################################################################
439 # THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
440 # An address is passed to each router in turn until it is accepted. #
441 ######################################################################
445 # This router routes to remote hosts over SMTP by explicit IP address,
446 # when an email address is given in "domain literal" form, for example,
447 # <user@[192.168.35.64]>. The RFCs require this facility. However, it is
448 # little-known these days, and has been exploited by evil people seeking
449 # to abuse SMTP relays. Consequently it is commented out in the default
450 # configuration. If you uncomment this router, you also need to uncomment
451 # allow_domain_literals above, so that Exim can recognize the syntax of
452 # domain literal addresses.
456 # domains = ! +local_domains
457 # transport = remote_smtp
460 # This router routes addresses that are not in local domains by doing a DNS
461 # lookup on the domain name. Any domain that resolves to 0.0.0.0 or to a
462 # loopback interface address (127.0.0.0/8) is treated as if it had no DNS
463 # entry. Note that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated
464 # as the local host inside the network stack. It is not 0.0.0.0/0, the default
465 # route. If the DNS lookup fails, no further routers are tried because of
466 # the no_more setting, and consequently the address is unrouteable.
470 domains = ! +local_domains
471 transport = remote_smtp
472 ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
476 # The remaining routers handle addresses in the local domain(s).
479 # This router handles aliasing using a linearly searched alias file with the
480 # name /etc/mail/aliases. When this configuration is installed automatically,
481 # the name gets inserted into this file from whatever is set in Exim's
482 # build-time configuration. The default path is the traditional /etc/aliases.
483 # If you install this configuration by hand, you need to specify the correct
484 # path in the "data" setting below.
486 ##### NB You must ensure that the alias file exists. It used to be the case
487 ##### NB that every Unix had that file, because it was the Sendmail default.
488 ##### NB These days, there are systems that don't have it. Your aliases
489 ##### NB file should at least contain an alias for "postmaster".
491 # If any of your aliases expand to pipes or files, you will need to set
492 # up a user and a group for these deliveries to run under. You can do
493 # this by uncommenting the "user" option below (changing the user name
494 # as appropriate) and adding a "group" option if necessary. Alternatively, you
495 # can specify "user" on the transports that are used. Note that the transports
496 # listed below are the same as are used for .forward files; you might want
497 # to set up different ones for pipe and file deliveries from aliases.
503 data = ${lookup{$local_part}lsearch{/etc/mail/aliases}}
505 file_transport = address_file
506 pipe_transport = address_pipe
509 # This router handles forwarding using traditional .forward files in users'
510 # home directories. If you want it also to allow mail filtering when a forward
511 # file starts with the string "# Exim filter" or "# Sieve filter", uncomment
512 # the "allow_filter" option.
514 # If you want this router to treat local parts with suffixes introduced by "-"
515 # or "+" characters as if the suffixes did not exist, uncomment the two local_
516 # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
517 # in the same way as xxxx@your.domain by this router. You probably want to make
518 # the same change to the localuser router.
520 # The no_verify setting means that this router is skipped when Exim is
521 # verifying addresses. Similarly, no_expn means that this router is skipped if
522 # Exim is processing an EXPN command.
524 # The check_ancestor option means that if the forward file generates an
525 # address that is an ancestor of the current one, the current one gets
526 # passed on instead. This covers the case where A is aliased to B and B
527 # has a .forward file pointing to A.
529 # The three transports specified at the end are those that are used when
530 # forwarding generates a direct delivery to a file, or to a pipe, or sets
531 # up an auto-reply, respectively.
536 # local_part_suffix = +* : -*
537 # local_part_suffix_optional
538 file = $home/.forward
543 file_transport = address_file
544 pipe_transport = address_pipe
545 reply_transport = address_reply
547 # Procmail. Uncomment following if you want procmail delivery.
552 # local_part_suffix = DSUFFIX*
553 # local_part_suffix_optional
554 # require_files = "${local_part}:+${home}/.procmailrc:\
555 # +/usr/bin/procmail:!${home}/.forward"
556 # transport = procmail_pipe
558 # This router matches local user mailboxes. If the router fails, the error
559 # message is "Unknown user".
561 # If you want this router to treat local parts with suffixes introduced by "-"
562 # or "+" characters as if the suffixes did not exist, uncomment the two local_
563 # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
564 # in the same way as xxxx@your.domain by this router.
569 # local_part_suffix = +* : -*
570 # local_part_suffix_optional
571 transport = local_delivery
572 cannot_route_message = Unknown user
575 ######################################################################
576 # TRANSPORTS CONFIGURATION #
577 ######################################################################
578 # ORDER DOES NOT MATTER #
579 # Only one appropriate transport is called for each delivery. #
580 ######################################################################
582 # A transport is used only when referenced from a router that successfully
583 # handles an address.
588 # This transport is used for delivering messages over SMTP connections.
594 # This transport is used for local delivery to user mailboxes in traditional
595 # BSD mailbox format. By default it will be run under the uid and gid of the
596 # local user, and requires the sticky bit to be set on the /var/mail directory.
597 # Some systems use the alternative approach of running mail deliveries under a
598 # particular group instead of using the sticky bit. The commented options below
599 # show how this can be done.
603 file = /var/mail/$local_part
610 # Procmail transport. Uncomment following if you want procmail delivery
614 # command = "procmail -f-"
617 # path = "/usr/local/bin:/usr/bin:/bin"
619 # user = ${local_part}
620 # temp_errors= 75 : 75 : 256
625 # This transport is used for handling pipe deliveries generated by alias or
626 # .forward files. If the pipe generates any standard output, it is returned
627 # to the sender of the message as a delivery error. Set return_fail_output
628 # instead of return_output if you want this to happen only when the pipe fails
629 # to complete normally. You can set different transports for aliases and
630 # forwards if you want to - see the references to address_pipe in the routers
638 # This transport is used for handling deliveries directly to files that are
639 # generated by aliasing or forwarding.
648 # This transport is used for handling autoreplies generated by the filtering
649 # option of the userforward router.
656 ######################################################################
657 # RETRY CONFIGURATION #
658 ######################################################################
662 # This single retry rule applies to all domains and all errors. It specifies
663 # retries every 15 minutes for 2 hours, then increasing retry intervals,
664 # starting at 1 hour and increasing each time by a factor of 1.5, up to 16
665 # hours, then retries every 6 hours until 4 days have passed since the first
668 # Domain Error Retries
669 # ------ ----- -------
671 * * F,2h,15m; G,16h,1h,1.5; F,4d,6h
675 ######################################################################
676 # REWRITE CONFIGURATION #
677 ######################################################################
679 # There are no rewriting specifications in this default configuration file.
685 ######################################################################
686 # AUTHENTICATION CONFIGURATION #
687 ######################################################################
689 # There are no authenticator specifications in this default configuration file.
693 # Uncomment lines below to enable SMTP AUTH support. Be aware that this
694 # requires cyrus-sasl-saslauthd package to be installed.
698 # public_name = PLAIN
700 # server_condition = ${if saslauthd{{$2}{$3}{smtp}}{1}{0}}
705 # public_name = LOGIN
706 # server_prompts = "Username:: : Password::"
707 # server_condition = ${if saslauthd{{$1}{$2}{smtp}}{1}{0}}
710 # End of Exim configuration file