1 # DO NOT EDIT - This file is being maintained by Chef
3 ######################################################################
4 # Runtime configuration file for Exim #
5 ######################################################################
8 # This is a default configuration file which will operate correctly in
9 # uncomplicated installations. Please see the manual for a complete list
10 # of all the runtime configuration options that can be included in a
11 # configuration file. There are many more than are mentioned here. The
12 # manual is in the file doc/spec.txt in the Exim distribution as a plain
13 # ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are available
14 # from the Exim ftp sites. The manual is also online at the Exim web sites.
17 # This file is divided into several parts, all but the first of which are
18 # headed by a line starting with the word "begin". Only those parts that
19 # are required need to be present. Blank lines, and lines starting with #
23 ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
25 # Whenever you change Exim's configuration file, you *must* remember to #
26 # HUP the Exim daemon, because it will not pick up the new configuration #
27 # until you do. However, any other Exim processes that are started, for #
28 # example, a process started by an MUA in order to send a message, will #
29 # see the new configuration as soon as it is in place. #
31 # You do not need to HUP the daemon for changes in auxiliary files that #
32 # are referenced from this file. They are read every time they are used. #
34 # It is usually a good idea to test a new configuration for syntactic #
35 # correctness before installing it (for example, by running the command #
36 # "exim -C /config/file.new -bV"). #
38 ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
42 ######################################################################
43 # MAIN CONFIGURATION SETTINGS #
44 ######################################################################
47 # Specify your host's canonical name here. This should normally be the fully
48 # qualified "official" name of your host. If this option is not set, the
49 # uname() function is called to obtain the name. In many cases this does
50 # the right thing and you need not set anything explicitly.
52 primary_hostname = <%= node[:fqdn] %>
55 # The next three settings create two lists of domains and one list of hosts.
56 # These lists are referred to later in this configuration using the syntax
57 # +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
58 # are all colon-separated lists:
60 domainlist local_domains = <%= node[:exim][:local_domains].join(" : ") %>
61 domainlist relay_to_domains = <%= @relay_to_domains.join(" : ") %>
62 hostlist relay_from_hosts = <; <%= @relay_from_hosts.join(" ; ") %>
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 File.exist?("/var/run/clamav/clamd.ctl") -%>
117 # If you are running a version of Exim that was compiled with the content-
118 # scanning extension, you can cause incoming messages to be automatically
119 # scanned for viruses. You have to modify the configuration in two places to
120 # set this up. The first of them is here, where you define the interface to
121 # your scanner. This example is typical for ClamAV; see the manual for details
122 # of what to set for other virus scanners. The second modification is in the
123 # acl_check_data access control list (see below).
125 av_scanner = clamd:/var/run/clamav/clamd.ctl
129 <% if File.exist?("/var/run/spamd.pid") -%>
130 # For spam scanning, there is a similar option that defines the interface to
131 # SpamAssassin. You do not need to set this if you are using the default, which
132 # is shown in this commented example. As for virus scanning, you must also
133 # modify the acl_check_data access control list to enable spam scanning.
135 spamd_address = 127.0.0.1 783
139 # If Exim is compiled with support for TLS, you may want to enable the
140 # following options so that Exim allows clients to make encrypted
141 # connections. In the authenticators section below, there are template
142 # configurations for plaintext username/password authentication. This kind
143 # of authentication is only safe when used within a TLS connection, so the
144 # authenticators will only work if the following TLS settings are turned on
147 # Allow any client to use TLS.
149 tls_advertise_hosts = *
151 # Specify the location of the Exim server's TLS certificate and private key.
152 # The private key must not be encrypted (password protected). You can put
153 # the certificate and private key in the same file, in which case you only
154 # need the first setting, or in separate files, in which case you need both
157 <% if node[:exim][:certificate_names] -%>
158 tls_certificate = /etc/ssl/certs/<%= node[:exim][:certificate_names].first %>.pem
159 tls_privatekey = /etc/ssl/private/<%= node[:exim][:certificate_names].first %>.key
161 tls_certificate = /etc/ssl/certs/exim.pem
162 tls_privatekey = /etc/ssl/private/exim.key
165 # Configure TLS cipher selection.
167 tls_require_ciphers = <%= node[:ssl][:gnutls_ciphers] %>:%SERVER_PRECEDENCE
169 # In order to support roaming users who wish to send email from anywhere,
170 # you may want to make Exim listen on other ports as well as port 25, in
171 # case these users need to send email from a network that blocks port 25.
172 # The standard port for this purpose is port 587, the "message submission"
173 # port. See RFC 4409 for details. Microsoft MUAs cannot be configured to
174 # talk the message submission protocol correctly, so if you need to support
175 # them you should also allow TLS-on-connect on the traditional but
176 # non-standard port 465.
178 daemon_smtp_ports = <%= node[:exim][:daemon_smtp_ports].join(" : ") %>
179 # tls_on_connect_ports = 465
182 # Specify the domain you want to be added to all unqualified addresses
183 # here. An unqualified address is one that does not contain an "@" character
184 # followed by a domain. For example, "caesar@rome.example" is a fully qualified
185 # address, but the string "caesar" (i.e. just a login name) is an unqualified
186 # email address. Unqualified addresses are accepted only from local callers by
187 # default. See the recipient_unqualified_hosts option if you want to permit
188 # unqualified addresses from remote sources. If this option is not set, the
189 # primary_hostname value is used for qualification.
191 qualify_domain = openstreetmap.org
194 # If you want unqualified recipient addresses to be qualified with a different
195 # domain to unqualified sender addresses, specify the recipient domain here.
196 # If this option is not set, the qualify_domain value is used.
198 qualify_recipient = <%= node[:fqdn] %>
201 # The following line must be uncommented if you want Exim to recognize
202 # addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
203 # (an IP address) instead of a named domain. The RFCs still require this form,
204 # but it makes little sense to permit mail to be sent to specific hosts by
205 # their IP address in the modern Internet. This ancient format has been used
206 # by those seeking to abuse hosts by using them for unwanted relaying. If you
207 # really do want to support domain literals, uncomment the following line, and
208 # see also the "domain_literal" router below.
210 # allow_domain_literals
213 # No deliveries will ever be run under the uids of users specified by
214 # never_users (a colon-separated list). An attempt to do so causes a panic
215 # error to be logged, and the delivery to be deferred. This is a paranoic
216 # safety catch. There is an even stronger safety catch in the form of the
217 # FIXED_NEVER_USERS setting in the configuration for building Exim. The list of
218 # users that it specifies is built into the binary, and cannot be changed. The
219 # option below just adds additional users to the list. The default for
220 # FIXED_NEVER_USERS is "root", but just to be absolutely sure, the default here
223 # Note that the default setting means you cannot deliver mail addressed to root
224 # as if it were a normal user. This isn't usually a problem, as most sites have
225 # an alias for root that redirects such mail to a human administrator.
230 # The setting below causes Exim to do a reverse DNS lookup on all incoming
231 # IP calls, in order to get the true host name. If you feel this is too
232 # expensive, you can specify the networks for which a lookup is done, or
233 # remove the setting entirely.
238 # The settings below cause Exim to make RFC 1413 (ident) callbacks
239 # for all incoming SMTP calls. You can limit the hosts to which these
240 # calls are made, and/or change the timeout that is used. If you set
241 # the timeout to zero, all RFC 1413 calls are disabled. RFC 1413 calls
242 # are cheap and can provide useful information for tracing problem
243 # messages, but some hosts and firewalls have problems with them.
244 # This can result in a timeout instead of an immediate refused
245 # connection, leading to delays on starting up SMTP sessions.
246 # (The default was reduced from 30s to 5s for release 4.61. and to
247 # disabled for release 4.86)
250 #rfc1413_query_timeout = 5s
253 # Enable an efficiency feature. We advertise the feature; clients
254 # may request to use it. For multi-recipient mails we then can
255 # reject or accept per-user after the message is received.
260 # By default, Exim expects all envelope addresses to be fully qualified, that
261 # is, they must contain both a local part and a domain. If you want to accept
262 # unqualified addresses (just a local part) from certain hosts, you can specify
263 # these hosts by setting one or both of
265 # sender_unqualified_hosts =
266 # recipient_unqualified_hosts =
268 # to control sender and recipient addresses, respectively. When this is done,
269 # unqualified addresses are qualified using the settings of qualify_domain
270 # and/or qualify_recipient (see above).
273 # Unless you run a high-volume site you probably want more logging
274 # detail than the default. Adjust to suit.
276 log_selector = +all -skip_delivery
279 # If you want Exim to support the "percent hack" for certain domains,
280 # uncomment the following line and provide a list of domains. The "percent
281 # hack" is the feature by which mail addressed to x%y@z (where z is one of
282 # the domains listed) is locally rerouted to x@y and sent on. If z is not one
283 # of the "percent hack" domains, x%y is treated as an ordinary local part. This
284 # hack is rarely needed nowadays; you should not enable it unless you are sure
285 # that you really need it.
287 # percent_hack_domains =
289 # As well as setting this option you will also need to remove the test
290 # for local parts containing % in the ACL definition below.
293 # When Exim can neither deliver a message nor return it to sender, it "freezes"
294 # the delivery error message (aka "bounce message"). There are also other
295 # circumstances in which messages get frozen. They will stay on the queue for
296 # ever unless one of the following options is set.
298 # This option unfreezes frozen bounce messages after two days, tries
299 # once more to deliver them, and ignores any delivery failures.
301 ignore_bounce_errors_after = 2d
303 # This option cancels (removes) frozen messages that are older than a week.
305 timeout_frozen_after = 7d
308 # By default, messages that are waiting on Exim's queue are all held in a
309 # single directory called "input" which it itself within Exim's spool
310 # directory. (The default spool directory is specified when Exim is built, and
311 # is often /var/spool/exim/.) Exim works best when its queue is kept short, but
312 # there are circumstances where this is not always possible. If you uncomment
313 # the setting below, messages on the queue are held in 62 subdirectories of
314 # "input" instead of all in the same directory. The subdirectories are called
315 # 0, 1, ... A, B, ... a, b, ... z. This has two benefits: (1) If your file
316 # system degrades with many files in one directory, this is less likely to
317 # happen; (2) Exim can process the queue one subdirectory at a time instead of
318 # all at once, which can give better performance with large queues.
320 # split_spool_directory = true
323 # If you're in a part of the world where ASCII is not sufficient for most
324 # text, then you're probably familiar with RFC2047 message header extensions.
325 # By default, Exim adheres to the specification, including a limit of 76
326 # characters to a line, with encoded words fitting within a line.
327 # If you wish to use decoded headers in message filters in such a way
328 # that successful decoding of malformed messages matters, you may wish to
329 # configure Exim to be more lenient.
331 # check_rfc2047_length = false
333 # In particular, the Exim maintainers have had multiple reports of problems
334 # from Russian administrators of issues until they disable this check,
335 # because of some popular, yet buggy, mail composition software.
338 # If you wish to be strictly RFC compliant, or if you know you'll be
339 # exchanging email with systems that are not 8-bit clean, then you may
340 # wish to disable advertising 8BITMIME. Uncomment this option to do so.
342 # accept_8bitmime = false
345 # Exim does not make use of environment variables itself. However,
346 # libraries that Exim uses (e.g. LDAP) depend on specific environment settings.
347 # There are two lists: keep_environment for the variables we trust, and
348 # add_environment for variables we want to set to a specific value.
349 # Note that TZ is handled separately by the timezone runtime option
350 # and TIMEZONE_DEFAULT buildtime option.
352 # keep_environment = ^LDAP
353 # add_environment = PATH=/usr/bin::/bin
356 # Define trusted users.
358 trusted_users = <%= node[:exim][:trusted_users].join(" : ") %>
362 ######################################################################
363 # ACL CONFIGURATION #
364 # Specifies access control lists for incoming SMTP mail #
365 ######################################################################
369 # This access control list is used for every RCPT command in an incoming
370 # SMTP message. The tests are run in order until the address is either
371 # accepted or denied.
375 # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
376 # testing for an empty sending host field.
379 control = dkim_disable_verify
381 #############################################################################
382 # The following section of the ACL is concerned with local parts that contain
383 # @ or % or ! or / or | or dots in unusual places.
385 # The characters other than dots are rarely found in genuine local parts, but
386 # are often tried by people looking to circumvent relaying restrictions.
387 # Therefore, although they are valid in local parts, these rules lock them
388 # out, as a precaution.
390 # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
391 # allows them because they have been encountered. (Consider local parts
392 # constructed as "firstinitial.secondinitial.familyname" when applied to
393 # someone like me, who has no second initial.) However, a local part starting
394 # with a dot or containing /../ can cause trouble if it is used as part of a
395 # file name (e.g. for a mailing list). This is also true for local parts that
396 # contain slashes. A pipe symbol can also be troublesome if the local part is
397 # incorporated unthinkingly into a shell command line.
399 # Two different rules are used. The first one is stricter, and is applied to
400 # messages that are addressed to one of the local domains handled by this
401 # host. The line "domains = +local_domains" restricts it to domains that are
402 # defined by the "domainlist local_domains" setting above. The rule blocks
403 # local parts that begin with a dot or contain @ % ! / or |. If you have
404 # local accounts that include these characters, you will have to modify this
407 deny message = Restricted characters in address
408 domains = +local_domains
409 local_parts = ^[.] : ^.*[@%!/|]
411 # The second rule applies to all other domains, and is less strict. The line
412 # "domains = !+local_domains" restricts it to domains that are NOT defined by
413 # the "domainlist local_domains" setting above. The exclamation mark is a
414 # negating operator. This rule allows your own users to send outgoing
415 # messages to sites that use slashes and vertical bars in their local parts.
416 # It blocks local parts that begin with a dot, slash, or vertical bar, but
417 # allows these characters within the local part. However, the sequence /../
418 # is barred. The use of @ % and ! is blocked, as before. The motivation here
419 # is to prevent your users (or your users' viruses) from mounting certain
420 # kinds of attack on remote sites.
422 deny message = Restricted characters in address
423 domains = !+local_domains
424 local_parts = ^[./|] : ^.*[@%!] : ^.*/\\.\\./
425 #############################################################################
427 # Block bounces to selected addresses
429 deny local_parts = root:postmaster:webmaster:abuse:support
432 # Block blacklisted senders
434 deny senders = lsearch*@;/etc/exim4/blocked-senders
435 message = Rejected because $sender_address is blacklisted\nQueries to postmaster@$qualify_domain
436 !hosts = +relay_from_hosts
438 # Accept mail to postmaster in any local domain, regardless of the source,
439 # and without verifying the sender.
441 accept local_parts = postmaster
442 domains = +local_domains
444 # Deny incoming mail unless the sender address can be verified.
446 deny !hosts = +relay_from_hosts
449 # Accept if the message comes from one of the hosts for which we are an
450 # outgoing relay. It is assumed that such hosts are most likely to be MUAs,
451 # so we set control=submission to make Exim treat the message as a
452 # submission. It will fix up various errors in the message, for example, the
453 # lack of a Date: header line. If you are actually relaying out out from
454 # MTAs, you may want to disable this. If you are handling both relaying from
455 # MTAs and submissions from MUAs you should probably split them into two
456 # lists, and handle them differently.
458 # Recipient verification is omitted here, because in many cases the clients
459 # are dumb MUAs that don't cope well with SMTP error responses. If you are
460 # actually relaying out from MTAs, you should probably add recipient
463 # Note that, by putting this test before any DNS black list checks, you will
464 # always accept from these hosts, even if they end up on a black list. The
465 # assumption is that they are your friends, and if they get onto a black
466 # list, it is a mistake.
468 accept hosts = +relay_from_hosts
470 control = dkim_disable_verify
472 # Accept if the message arrived over an authenticated connection, from
473 # any host. Again, these messages are usually from MUAs, so recipient
474 # verification is omitted, and submission mode is set. And again, we do this
475 # check before any black list tests.
477 accept authenticated = *
479 control = dkim_disable_verify
481 # Insist that any other recipient address that we accept is either in one of
482 # our local domains, or is in a domain for which we explicitly allow
483 # relaying. Any other domain is rejected as being unacceptable for relaying.
485 require message = relay not permitted
486 domains = +local_domains : +relay_to_domains
488 # We also require all accepted addresses to be verifiable. This check will
489 # do local part verification for local domains, but only check the domain
490 # for remote domains. The only way to check local parts for the remote
491 # relay domains is to use a callout (add /callout), but please read the
492 # documentation about callouts before doing this.
494 require verify = recipient
496 <% if node[:exim][:dns_blacklists] -%>
497 # Deny any messages from hosts in certain blacklists.
499 deny message = Rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
500 dnslists = <%= node[:exim][:dns_blacklists].join(" : ") %>
503 #############################################################################
504 # This check is commented out because it is recognized that not every
505 # sysadmin will want to do it. If you enable it, the check performs
506 # Client SMTP Authorization (csa) checks on the sending host. These checks
507 # do DNS lookups for SRV records. The CSA proposal is currently (May 2005)
508 # an Internet draft. You can, of course, add additional conditions to this
509 # ACL statement to restrict the CSA checks to certain hosts only.
511 # require verify = csa
512 #############################################################################
514 # At this point, the address has passed all the checks that have been
515 # configured, so we accept it unconditionally.
520 # This ACL is used after the contents of a message have been received. This
521 # is the ACL in which you can test a message's headers or body, and in
522 # particular, this is where you can invoke external virus or spam scanners.
523 # Some suggested ways of configuring these tests are shown below, commented
524 # out. Without any tests, this ACL accepts all messages. If you want to use
525 # such tests, you must ensure that Exim is compiled with the content-scanning
526 # extension (WITH_CONTENT_SCAN=yes in Local/Makefile).
530 <% if File.exist?("/var/run/clamav/clamd.ctl") -%>
531 # Deny if the message contains a virus. Before enabling this check, you
532 # must install a virus scanner and set the av_scanner option above.
535 message = This message was detected as possible malware ($malware_name).
538 <% if File.exist?("/var/run/spamd.pid") -%>
539 # Deny if the message looks like spam. Before enabling this check, you
540 # must install spamassassin and set the spamd_address option above.
542 deny spam = nobody/deferok
543 message = This message scored $spam_score SpamAssassin points.
546 # Deny spammy messages with headers of the form:
547 # X-PHP-Originating-Script: <digits>:<name>.php
548 # X-PHP-Originating-Script: <digits>:<name>.class.php
549 deny condition = ${if match {$h_X-PHP-Originating-Script:}{^[0-9]+:[A-Za-z]+(\\.class)?\\.php\$}}
550 !hosts = +relay_from_hosts
551 message = This message failed local spam checks.
553 # Accept messages from relay hosts without modification.
555 accept hosts = +relay_from_hosts
557 # Accept messages from external hosts and add authentication results.
559 accept add_header = :at_start:${authresults {$primary_hostname}}
563 ######################################################################
564 # ROUTERS CONFIGURATION #
565 # Specifies how addresses are handled #
566 ######################################################################
567 # THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
568 # An address is passed to each router in turn until it is accepted. #
569 ######################################################################
573 # This router handles aliasing using a linearly searched alias file with the
574 # name /etc/aliases. When this configuration is installed automatically,
575 # the name gets inserted into this file from whatever is set in Exim's
576 # build-time configuration. The default path is the traditional /etc/aliases.
577 # If you install this configuration by hand, you need to specify the correct
578 # path in the "data" setting below.
580 ##### NB You must ensure that the alias file exists. It used to be the case
581 ##### NB that every Unix had that file, because it was the Sendmail default.
582 ##### NB These days, there are systems that don't have it. Your aliases
583 ##### NB file should at least contain an alias for "postmaster".
585 # If any of your aliases expand to pipes or files, you will need to set
586 # up a user and a group for these deliveries to run under. You can do
587 # this by uncommenting the "user" option below (changing the user name
588 # as appropriate) and adding a "group" option if necessary. Alternatively, you
589 # can specify "user" on the transports that are used. Note that the transports
590 # listed below are the same as are used for .forward files; you might want
591 # to set up different ones for pipe and file deliveries from aliases.
595 domains = !noreply.openstreetmap.org : +local_domains
598 data = ${lookup{$local_part}lsearch{/etc/aliases}}
600 file_transport = address_file
601 pipe_transport = address_pipe
603 <% if File.directory?("/var/lib/mailman") -%>
604 # This router handles mail for mailman mailing lists.
608 domains = +local_domains
609 condition = ${lookup{$local_part@$domain}lsearch{/var/lib/mailman/data/virtual-mailman}{1}{0}}
610 require_files = /var/lib/mailman/lists/$local_part/config.pck
611 local_part_suffix = -bounces : -bounces+* : \
612 -confirm+* : -join : -leave : \
613 -subscribe : -unsubscribe : \
614 -owner : -request : -admin
615 local_part_suffix_optional
619 # This router handles mail for noreply.openstreetmap.org
623 domains = noreply.openstreetmap.org
624 require_files = /etc/exim4/noreply/$local_part
627 <% node[:exim][:routes].each do |name,details| -%>
628 # This router handles mail for <%= details[:comment] -%>.
631 <% if details[:host] -%>
636 <% if details[:domains] -%>
637 domains = <%= details[:domains].join(" : ") %>
639 <% if details[:local_parts] -%>
640 local_parts = <%= details[:local_parts].join(" : ") %>
641 local_part_suffix = +*
642 local_part_suffix_optional
644 <% if details[:host] -%>
645 <% if details[:host].kind_of?(Array) -%>
646 route_data = <%= details[:host].join(":") %> byname
648 route_data = <%= details[:host] %> byname
650 transport = remote_smtp
652 transport = <%= name %>
657 <% if node[:exim][:smarthost_via] -%>
658 # This router routes addresses that are not in local domains by
659 # forwarding them to a smarthost.
663 domains = ! +local_domains
664 transport = remote_smtp
665 route_data = <%= node[:exim][:smarthost_via].gsub(":", "::") -%> byname
666 same_domain_copy_routing = yes
669 # This router routes addresses that are not in local domains by doing a DNS
670 # lookup on the domain name. The exclamation mark that appears in "domains = !
671 # +local_domains" is a negating operator, that is, it can be read as "not". The
672 # recipient's domain must not be one of those defined by "domainlist
673 # local_domains" above for this router to be used.
675 # If the router is used, any domain that resolves to 0.0.0.0 or to a loopback
676 # interface address (127.0.0.0/8) is treated as if it had no DNS entry. Note
677 # that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated as the
678 # local host inside the network stack. It is not 0.0.0.0/0, the default route.
679 # If the DNS lookup fails, no further routers are tried because of the no_more
680 # setting, and consequently the address is unrouteable.
684 domains = ! +local_domains
685 transport = signed_smtp
686 same_domain_copy_routing = yes
687 ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
692 ######################################################################
693 # TRANSPORTS CONFIGURATION #
694 ######################################################################
695 # ORDER DOES NOT MATTER #
696 # Only one appropriate transport is called for each delivery. #
697 ######################################################################
699 # A transport is used only when referenced from a router that successfully
700 # handles an address.
705 # This transport is used for delivering messages over SMTP connections.
710 tls_require_ciphers = <%= node[:ssl][:gnutls_ciphers] %>:%LATEST_RECORD_VERSION
713 # This transport is used for delivering DKIM signed messages over SMTP connections.
717 dkim_domain = ${lookup{${domain:$h_from:}}partial-lsearch{/etc/exim4/dkim-domains}{$value}}
718 dkim_selector = ${lookup{$dkim_domain}lsearch{/etc/exim4/dkim-selectors}{$value}}
719 dkim_private_key = /etc/exim4/dkim-keys/${dkim_domain}
720 dkim_identity = ${lc:${address:$h_from:}}
721 dkim_timestamps = 1209600
724 tls_require_ciphers = <%= node[:ssl][:gnutls_ciphers] %>:%LATEST_RECORD_VERSION
727 # This transport is used for handling pipe deliveries generated by alias or
728 # .forward files. If the pipe generates any standard output, it is returned
729 # to the sender of the message as a delivery error. Set return_fail_output
730 # instead of return_output if you want this to happen only when the pipe fails
731 # to complete normally. You can set different transports for aliases and
732 # forwards if you want to - see the references to address_pipe in the routers
740 # This transport is used for handling deliveries directly to files that are
741 # generated by aliasing or forwarding.
750 <% if File.directory?("/var/lib/mailman") -%>
751 # This transport is used for handling deliveries to mailman mailing lists.
755 command = /var/lib/mailman/mail/mailman \
756 '${if def:local_part_suffix \
757 {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
760 current_directory = /var/lib/mailman
761 home_directory = /var/lib/mailman
764 freeze_exec_fail = true
768 # This transport handles mail for noreply.openstreetmap.org
772 from = OpenStreetMap <noreply@openstreetmap.org>
774 subject = Re: $header_subject:
775 headers = MIME-Version: 1.0\nContent-Type: text/plain; charset=utf-8
776 file = /etc/exim4/noreply/$local_part_data
780 <% node[:exim][:routes].each do |name,details| -%>
781 <% if details[:command] or details[:file] or details[:maildir] -%>
782 # This transport handles mail for <%= details[:comment] -%>.
785 <% if details[:command] -%>
787 command = <%= details[:command] %>
788 home_directory = <%= details[:home_directory] %>
789 path = <%= details[:path] || "/bin:/usr/bin" %>
790 <% if details[:environment] -%>
791 environment = <%= details[:environment].map { |k,v| "#{k}=#{v}" }.join(":") %>
796 <% if details[:file] -%>
797 file = <%= details[:file] %>
798 <% elsif details[:maildir] -%>
799 directory = <%= details[:maildir] %>
806 user = <%= details[:user] %>
807 <% if details[:group] -%>
808 group = <%= details[:group] %>
814 ######################################################################
815 # RETRY CONFIGURATION #
816 ######################################################################
820 # This single retry rule applies to all domains and all errors. It specifies
821 # retries every 15 minutes for 2 hours, then increasing retry intervals,
822 # starting at 1 hour and increasing each time by a factor of 1.5, up to 16
823 # hours, then retries every 6 hours until 4 days have passed since the first
826 # WARNING: If you do not have any retry rules at all (this section of the
827 # configuration is non-existent or empty), Exim will not do any retries of
828 # messages that fail to get delivered at the first attempt. The effect will
829 # be to treat temporary errors as permanent. Therefore, DO NOT remove this
830 # retry rule unless you really don't want any retries.
832 # Address or Domain Error Retries
833 # ----------------- ----- -------
835 * * F,2h,15m; G,16h,1h,1.5; F,4d,6h
839 ######################################################################
840 # REWRITE CONFIGURATION #
841 ######################################################################
843 # There are no rewriting specifications in this default configuration file.
846 *@<%= node[:fqdn] %> "${if !match {${lookup{$1}lsearch{/etc/aliases}{$value}}}{@} {$1@openstreetmap.org}fail}" Eh
847 <% node[:exim][:rewrites].each do |rewrite| -%>
848 <%= rewrite[:pattern] %> <%= rewrite[:replacement] %> <%= rewrite[:flags] %>
853 ######################################################################
854 # AUTHENTICATION CONFIGURATION #
855 ######################################################################
857 # The following authenticators support plaintext username/password
858 # authentication using the standard PLAIN mechanism and the traditional
859 # but non-standard LOGIN mechanism, with Exim acting as the server.
860 # PLAIN and LOGIN are enough to support most MUA software.
862 # These authenticators are not complete: you need to change the
863 # server_condition settings to specify how passwords are verified.
864 # They are set up to offer authentication to the client only if the
865 # connection is encrypted with TLS, so you also need to add support
866 # for TLS. See the global configuration options section at the start
867 # of this file for more about TLS.
869 # The default RCPT ACL checks for successful authentication, and will accept
870 # messages from authenticated users from anywhere on the Internet.
874 # PLAIN authentication has no server prompts. The client sends its
875 # credentials in one lump, containing an authorization ID (which we do not
876 # use), an authentication ID, and a password. The latter two appear as
877 # $auth2 and $auth3 in the configuration and should be checked against a
878 # valid username and password. In a real configuration you would typically
879 # use $auth2 as a lookup key, and compare $auth3 against the result of the
880 # lookup, perhaps using the crypteq{}{} condition.
884 # server_set_id = $auth2
886 # server_condition = Authentication is not yet configured
887 # server_advertise_condition = ${if def:tls_cipher }
889 # LOGIN authentication has traditional prompts and responses. There is no
890 # authorization ID in this mechanism, so unlike PLAIN the username and
891 # password are $auth1 and $auth2. Apart from that you can use the same
892 # server_condition setting for both authenticators.
896 # server_set_id = $auth1
897 # server_prompts = <| Username: | Password:
898 # server_condition = Authentication is not yet configured
899 # server_advertise_condition = ${if def:tls_cipher }
902 ######################################################################
903 # CONFIGURATION FOR local_scan() #
904 ######################################################################
906 # If you have built Exim to include a local_scan() function that contains
907 # tables for private options, you can define those options here. Remember to
908 # uncomment the "begin" line. It is commented by default because it provokes
909 # an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
910 # set in the Local/Makefile.
915 # End of Exim configuration file