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_mail = acl_check_mail
111 acl_smtp_rcpt = acl_check_rcpt
112 acl_smtp_data = acl_check_data
114 # You should not change those settings until you understand how ACLs work.
117 <% if File.exist?("/var/run/clamav/clamd.ctl") -%>
118 # If you are running a version of Exim that was compiled with the content-
119 # scanning extension, you can cause incoming messages to be automatically
120 # scanned for viruses. You have to modify the configuration in two places to
121 # set this up. The first of them is here, where you define the interface to
122 # your scanner. This example is typical for ClamAV; see the manual for details
123 # of what to set for other virus scanners. The second modification is in the
124 # acl_check_data access control list (see below).
126 av_scanner = clamd:/var/run/clamav/clamd.ctl
130 <% if File.exist?("/var/run/spamd.pid") -%>
131 # For spam scanning, there is a similar option that defines the interface to
132 # SpamAssassin. You do not need to set this if you are using the default, which
133 # is shown in this commented example. As for virus scanning, you must also
134 # modify the acl_check_data access control list to enable spam scanning.
136 spamd_address = 127.0.0.1 783
140 # If Exim is compiled with support for TLS, you may want to enable the
141 # following options so that Exim allows clients to make encrypted
142 # connections. In the authenticators section below, there are template
143 # configurations for plaintext username/password authentication. This kind
144 # of authentication is only safe when used within a TLS connection, so the
145 # authenticators will only work if the following TLS settings are turned on
148 # Allow any client to use TLS.
150 tls_advertise_hosts = *
152 # Specify the location of the Exim server's TLS certificate and private key.
153 # The private key must not be encrypted (password protected). You can put
154 # the certificate and private key in the same file, in which case you only
155 # need the first setting, or in separate files, in which case you need both
158 <% if node[:exim][:certificate_names] -%>
159 tls_certificate = /etc/ssl/certs/<%= node[:exim][:certificate_names].first %>.pem
160 tls_privatekey = /etc/ssl/private/<%= node[:exim][:certificate_names].first %>.key
162 tls_certificate = /etc/ssl/certs/exim.pem
163 tls_privatekey = /etc/ssl/private/exim.key
166 # Configure TLS cipher selection.
168 tls_require_ciphers = <%= node[:ssl][:gnutls_ciphers] %>:%SERVER_PRECEDENCE
170 # In order to support roaming users who wish to send email from anywhere,
171 # you may want to make Exim listen on other ports as well as port 25, in
172 # case these users need to send email from a network that blocks port 25.
173 # The standard port for this purpose is port 587, the "message submission"
174 # port. See RFC 4409 for details. Microsoft MUAs cannot be configured to
175 # talk the message submission protocol correctly, so if you need to support
176 # them you should also allow TLS-on-connect on the traditional but
177 # non-standard port 465.
179 daemon_smtp_ports = <%= node[:exim][:daemon_smtp_ports].join(" : ") %>
180 # tls_on_connect_ports = 465
183 # Specify the domain you want to be added to all unqualified addresses
184 # here. An unqualified address is one that does not contain an "@" character
185 # followed by a domain. For example, "caesar@rome.example" is a fully qualified
186 # address, but the string "caesar" (i.e. just a login name) is an unqualified
187 # email address. Unqualified addresses are accepted only from local callers by
188 # default. See the recipient_unqualified_hosts option if you want to permit
189 # unqualified addresses from remote sources. If this option is not set, the
190 # primary_hostname value is used for qualification.
192 qualify_domain = openstreetmap.org
195 # If you want unqualified recipient addresses to be qualified with a different
196 # domain to unqualified sender addresses, specify the recipient domain here.
197 # If this option is not set, the qualify_domain value is used.
199 qualify_recipient = <%= node[:fqdn] %>
202 # The following line must be uncommented if you want Exim to recognize
203 # addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
204 # (an IP address) instead of a named domain. The RFCs still require this form,
205 # but it makes little sense to permit mail to be sent to specific hosts by
206 # their IP address in the modern Internet. This ancient format has been used
207 # by those seeking to abuse hosts by using them for unwanted relaying. If you
208 # really do want to support domain literals, uncomment the following line, and
209 # see also the "domain_literal" router below.
211 # allow_domain_literals
214 # No deliveries will ever be run under the uids of users specified by
215 # never_users (a colon-separated list). An attempt to do so causes a panic
216 # error to be logged, and the delivery to be deferred. This is a paranoic
217 # safety catch. There is an even stronger safety catch in the form of the
218 # FIXED_NEVER_USERS setting in the configuration for building Exim. The list of
219 # users that it specifies is built into the binary, and cannot be changed. The
220 # option below just adds additional users to the list. The default for
221 # FIXED_NEVER_USERS is "root", but just to be absolutely sure, the default here
224 # Note that the default setting means you cannot deliver mail addressed to root
225 # as if it were a normal user. This isn't usually a problem, as most sites have
226 # an alias for root that redirects such mail to a human administrator.
231 # The setting below causes Exim to do a reverse DNS lookup on all incoming
232 # IP calls, in order to get the true host name. If you feel this is too
233 # expensive, you can specify the networks for which a lookup is done, or
234 # remove the setting entirely.
239 # The settings below cause Exim to make RFC 1413 (ident) callbacks
240 # for all incoming SMTP calls. You can limit the hosts to which these
241 # calls are made, and/or change the timeout that is used. If you set
242 # the timeout to zero, all RFC 1413 calls are disabled. RFC 1413 calls
243 # are cheap and can provide useful information for tracing problem
244 # messages, but some hosts and firewalls have problems with them.
245 # This can result in a timeout instead of an immediate refused
246 # connection, leading to delays on starting up SMTP sessions.
247 # (The default was reduced from 30s to 5s for release 4.61. and to
248 # disabled for release 4.86)
251 #rfc1413_query_timeout = 5s
254 # Enable an efficiency feature. We advertise the feature; clients
255 # may request to use it. For multi-recipient mails we then can
256 # reject or accept per-user after the message is received.
261 # By default, Exim expects all envelope addresses to be fully qualified, that
262 # is, they must contain both a local part and a domain. If you want to accept
263 # unqualified addresses (just a local part) from certain hosts, you can specify
264 # these hosts by setting one or both of
266 # sender_unqualified_hosts =
267 # recipient_unqualified_hosts =
269 # to control sender and recipient addresses, respectively. When this is done,
270 # unqualified addresses are qualified using the settings of qualify_domain
271 # and/or qualify_recipient (see above).
274 # Unless you run a high-volume site you probably want more logging
275 # detail than the default. Adjust to suit.
277 log_selector = +all -skip_delivery
280 # If you want Exim to support the "percent hack" for certain domains,
281 # uncomment the following line and provide a list of domains. The "percent
282 # hack" is the feature by which mail addressed to x%y@z (where z is one of
283 # the domains listed) is locally rerouted to x@y and sent on. If z is not one
284 # of the "percent hack" domains, x%y is treated as an ordinary local part. This
285 # hack is rarely needed nowadays; you should not enable it unless you are sure
286 # that you really need it.
288 # percent_hack_domains =
290 # As well as setting this option you will also need to remove the test
291 # for local parts containing % in the ACL definition below.
294 # When Exim can neither deliver a message nor return it to sender, it "freezes"
295 # the delivery error message (aka "bounce message"). There are also other
296 # circumstances in which messages get frozen. They will stay on the queue for
297 # ever unless one of the following options is set.
299 # This option unfreezes frozen bounce messages after two days, tries
300 # once more to deliver them, and ignores any delivery failures.
302 ignore_bounce_errors_after = 2d
304 # This option cancels (removes) frozen messages that are older than a week.
306 timeout_frozen_after = 7d
309 # By default, messages that are waiting on Exim's queue are all held in a
310 # single directory called "input" which it itself within Exim's spool
311 # directory. (The default spool directory is specified when Exim is built, and
312 # is often /var/spool/exim/.) Exim works best when its queue is kept short, but
313 # there are circumstances where this is not always possible. If you uncomment
314 # the setting below, messages on the queue are held in 62 subdirectories of
315 # "input" instead of all in the same directory. The subdirectories are called
316 # 0, 1, ... A, B, ... a, b, ... z. This has two benefits: (1) If your file
317 # system degrades with many files in one directory, this is less likely to
318 # happen; (2) Exim can process the queue one subdirectory at a time instead of
319 # all at once, which can give better performance with large queues.
321 # split_spool_directory = true
324 # If you're in a part of the world where ASCII is not sufficient for most
325 # text, then you're probably familiar with RFC2047 message header extensions.
326 # By default, Exim adheres to the specification, including a limit of 76
327 # characters to a line, with encoded words fitting within a line.
328 # If you wish to use decoded headers in message filters in such a way
329 # that successful decoding of malformed messages matters, you may wish to
330 # configure Exim to be more lenient.
332 # check_rfc2047_length = false
334 # In particular, the Exim maintainers have had multiple reports of problems
335 # from Russian administrators of issues until they disable this check,
336 # because of some popular, yet buggy, mail composition software.
339 # If you wish to be strictly RFC compliant, or if you know you'll be
340 # exchanging email with systems that are not 8-bit clean, then you may
341 # wish to disable advertising 8BITMIME. Uncomment this option to do so.
343 # accept_8bitmime = false
346 # Exim does not make use of environment variables itself. However,
347 # libraries that Exim uses (e.g. LDAP) depend on specific environment settings.
348 # There are two lists: keep_environment for the variables we trust, and
349 # add_environment for variables we want to set to a specific value.
350 # Note that TZ is handled separately by the timezone runtime option
351 # and TIMEZONE_DEFAULT buildtime option.
353 # keep_environment = ^LDAP
354 # add_environment = PATH=/usr/bin::/bin
357 # Define trusted users.
359 trusted_users = <%= node[:exim][:trusted_users].join(" : ") %>
362 # Do all deliveries via a limited set of queues.
365 queue_run_max = <%= node[:exim][:queue_run_max] %>
368 # Maximum number of simultaneous SMTP connections
370 smtp_accept_max = <%= node[:exim][:smtp_accept_max] %>
374 ######################################################################
375 # ACL CONFIGURATION #
376 # Specifies access control lists for incoming SMTP mail #
377 ######################################################################
381 # This access control list is used for the MAIL command in an incoming
388 # This access control list is used for every RCPT command in an incoming
389 # SMTP message. The tests are run in order until the address is either
390 # accepted or denied.
394 # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
395 # testing for an empty sending host field.
398 control = dkim_disable_verify
400 #############################################################################
401 # The following section of the ACL is concerned with local parts that contain
402 # @ or % or ! or / or | or dots in unusual places.
404 # The characters other than dots are rarely found in genuine local parts, but
405 # are often tried by people looking to circumvent relaying restrictions.
406 # Therefore, although they are valid in local parts, these rules lock them
407 # out, as a precaution.
409 # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
410 # allows them because they have been encountered. (Consider local parts
411 # constructed as "firstinitial.secondinitial.familyname" when applied to
412 # someone like me, who has no second initial.) However, a local part starting
413 # with a dot or containing /../ can cause trouble if it is used as part of a
414 # file name (e.g. for a mailing list). This is also true for local parts that
415 # contain slashes. A pipe symbol can also be troublesome if the local part is
416 # incorporated unthinkingly into a shell command line.
418 # Two different rules are used. The first one is stricter, and is applied to
419 # messages that are addressed to one of the local domains handled by this
420 # host. The line "domains = +local_domains" restricts it to domains that are
421 # defined by the "domainlist local_domains" setting above. The rule blocks
422 # local parts that begin with a dot or contain @ % ! / or |. If you have
423 # local accounts that include these characters, you will have to modify this
426 deny message = Restricted characters in address
427 domains = +local_domains
428 local_parts = ^[.] : ^.*[@%!/|]
430 # The second rule applies to all other domains, and is less strict. The line
431 # "domains = !+local_domains" restricts it to domains that are NOT defined by
432 # the "domainlist local_domains" setting above. The exclamation mark is a
433 # negating operator. This rule allows your own users to send outgoing
434 # messages to sites that use slashes and vertical bars in their local parts.
435 # It blocks local parts that begin with a dot, slash, or vertical bar, but
436 # allows these characters within the local part. However, the sequence /../
437 # is barred. The use of @ % and ! is blocked, as before. The motivation here
438 # is to prevent your users (or your users' viruses) from mounting certain
439 # kinds of attack on remote sites.
441 deny message = Restricted characters in address
442 domains = !+local_domains
443 local_parts = ^[./|] : ^.*[@%!] : ^.*/\\.\\./
444 #############################################################################
446 # Block bounces to selected addresses
448 deny local_parts = root:postmaster:webmaster:abuse:support
451 # Block blacklisted senders
453 deny senders = lsearch*@;/etc/exim4/blocked-senders
454 message = Rejected because $sender_address is blacklisted\nQueries to postmaster@$qualify_domain
455 !hosts = +relay_from_hosts
457 deny sender_domains= partial-lsearch;/etc/exim4/blocked-sender-domains
458 message = Rejected because $sender_address is blacklisted\nQueries to postmaster@$qualify_domain
459 !hosts = +relay_from_hosts
461 # Accept mail to postmaster in any local domain, regardless of the source,
462 # and without verifying the sender.
464 accept local_parts = postmaster
465 domains = +local_domains
467 # Deny incoming mail unless the sender address can be verified.
469 deny !hosts = +relay_from_hosts
472 # Accept if the message comes from one of the hosts for which we are an
473 # outgoing relay. It is assumed that such hosts are most likely to be MUAs,
474 # so we set control=submission to make Exim treat the message as a
475 # submission. It will fix up various errors in the message, for example, the
476 # lack of a Date: header line. If you are actually relaying out out from
477 # MTAs, you may want to disable this. If you are handling both relaying from
478 # MTAs and submissions from MUAs you should probably split them into two
479 # lists, and handle them differently.
481 # Recipient verification is omitted here, because in many cases the clients
482 # are dumb MUAs that don't cope well with SMTP error responses. If you are
483 # actually relaying out from MTAs, you should probably add recipient
486 # Note that, by putting this test before any DNS black list checks, you will
487 # always accept from these hosts, even if they end up on a black list. The
488 # assumption is that they are your friends, and if they get onto a black
489 # list, it is a mistake.
491 accept hosts = +relay_from_hosts
493 control = dkim_disable_verify
495 # Accept if the message arrived over an authenticated connection, from
496 # any host. Again, these messages are usually from MUAs, so recipient
497 # verification is omitted, and submission mode is set. And again, we do this
498 # check before any black list tests.
500 accept authenticated = *
502 control = dkim_disable_verify
504 # Insist that any other recipient address that we accept is either in one of
505 # our local domains, or is in a domain for which we explicitly allow
506 # relaying. Any other domain is rejected as being unacceptable for relaying.
508 require message = relay not permitted
509 domains = +local_domains : +relay_to_domains
511 # We also require all accepted addresses to be verifiable. This check will
512 # do local part verification for local domains, but only check the domain
513 # for remote domains. The only way to check local parts for the remote
514 # relay domains is to use a callout (add /callout), but please read the
515 # documentation about callouts before doing this.
517 deny domains = +relay_to_domains
518 !verify = recipient/callout=use_sender
520 deny domains = !+relay_to_domains
523 <% if node[:exim][:dns_blacklists] -%>
524 # Deny any messages from hosts in certain blacklists.
526 deny message = Rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
527 dnslists = <%= node[:exim][:dns_blacklists].join(" : ") %>
530 #############################################################################
531 # This check is commented out because it is recognized that not every
532 # sysadmin will want to do it. If you enable it, the check performs
533 # Client SMTP Authorization (csa) checks on the sending host. These checks
534 # do DNS lookups for SRV records. The CSA proposal is currently (May 2005)
535 # an Internet draft. You can, of course, add additional conditions to this
536 # ACL statement to restrict the CSA checks to certain hosts only.
538 # require verify = csa
539 #############################################################################
541 # At this point, the address has passed all the checks that have been
542 # configured, so we accept it unconditionally.
547 # This ACL is used after the contents of a message have been received. This
548 # is the ACL in which you can test a message's headers or body, and in
549 # particular, this is where you can invoke external virus or spam scanners.
550 # Some suggested ways of configuring these tests are shown below, commented
551 # out. Without any tests, this ACL accepts all messages. If you want to use
552 # such tests, you must ensure that Exim is compiled with the content-scanning
553 # extension (WITH_CONTENT_SCAN=yes in Local/Makefile).
557 <% if File.exist?("/var/run/clamav/clamd.ctl") -%>
558 # Deny if the message contains a virus. Before enabling this check, you
559 # must install a virus scanner and set the av_scanner option above.
562 message = This message was detected as possible malware ($malware_name).
565 <% if File.exist?("/var/run/spamd.pid") -%>
566 # Deny if the message looks like spam. Before enabling this check, you
567 # must install spamassassin and set the spamd_address option above.
569 deny spam = nobody/deferok
570 message = This message scored $spam_score SpamAssassin points.
573 # Deny spammy messages with headers of the form:
574 # X-PHP-Originating-Script: <digits>:<name>.php
575 # X-PHP-Originating-Script: <digits>:<name>.class.php
576 deny condition = ${if match {$h_X-PHP-Originating-Script:}{^[0-9]+:[A-Za-z]+(\\.class)?\\.php\$}}
577 !hosts = +relay_from_hosts
578 message = This message failed local spam checks.
580 # Accept messages from relay hosts without modification.
582 accept hosts = +relay_from_hosts
584 # Accept messages from external hosts and add authentication results.
586 accept add_header = :at_start:${authresults {$primary_hostname}}
590 ######################################################################
591 # ROUTERS CONFIGURATION #
592 # Specifies how addresses are handled #
593 ######################################################################
594 # THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
595 # An address is passed to each router in turn until it is accepted. #
596 ######################################################################
600 # This router handles aliasing using a linearly searched alias file with the
601 # name /etc/aliases. When this configuration is installed automatically,
602 # the name gets inserted into this file from whatever is set in Exim's
603 # build-time configuration. The default path is the traditional /etc/aliases.
604 # If you install this configuration by hand, you need to specify the correct
605 # path in the "data" setting below.
607 ##### NB You must ensure that the alias file exists. It used to be the case
608 ##### NB that every Unix had that file, because it was the Sendmail default.
609 ##### NB These days, there are systems that don't have it. Your aliases
610 ##### NB file should at least contain an alias for "postmaster".
612 # If any of your aliases expand to pipes or files, you will need to set
613 # up a user and a group for these deliveries to run under. You can do
614 # this by uncommenting the "user" option below (changing the user name
615 # as appropriate) and adding a "group" option if necessary. Alternatively, you
616 # can specify "user" on the transports that are used. Note that the transports
617 # listed below are the same as are used for .forward files; you might want
618 # to set up different ones for pipe and file deliveries from aliases.
622 domains = !noreply.openstreetmap.org : +local_domains
625 data = ${lookup{$local_part}lsearch{/etc/aliases}}
627 file_transport = address_file
628 pipe_transport = address_pipe
630 <% if File.directory?("/var/lib/mailman") -%>
631 # This router handles mail for mailman mailing lists.
635 domains = +local_domains
636 condition = ${lookup{$local_part@$domain}lsearch{/var/lib/mailman/data/virtual-mailman}{1}{0}}
637 require_files = /var/lib/mailman/lists/$local_part/config.pck
638 local_part_suffix = -bounces : -bounces+* : \
639 -confirm+* : -join : -leave : \
640 -subscribe : -unsubscribe : \
641 -owner : -request : -admin
642 local_part_suffix_optional
646 # This router handles mail for noreply.openstreetmap.org
650 domains = noreply.openstreetmap.org
651 require_files = /etc/exim4/noreply/$local_part
654 <% node[:exim][:routes].each do |name,details| -%>
655 # This router handles mail for <%= details[:comment] -%>.
658 <% if details[:host] -%>
663 <% if details[:domains] -%>
664 domains = <%= details[:domains].join(" : ") %>
666 <% if details[:local_parts] -%>
667 local_parts = <%= details[:local_parts].join(" : ") %>
668 local_part_suffix = +*
669 local_part_suffix_optional
671 <% if details[:host] -%>
672 <% if details[:host].kind_of?(Array) -%>
673 route_data = <%= details[:host].join(":") %> byname
675 route_data = <%= details[:host] %> byname
677 transport = remote_smtp
679 transport = <%= name %>
681 <% if details[:case_sensitive] -%>
687 <% if node[:exim][:smarthost_via] -%>
688 # This router routes addresses that are not in local domains by
689 # forwarding them to a smarthost.
693 domains = ! +local_domains
694 transport = remote_smtp
695 route_data = <%= node[:exim][:smarthost_via].gsub(":", "::") -%> byname
696 same_domain_copy_routing = yes
699 # This router routes addresses that are not in local domains by doing a DNS
700 # lookup on the domain name. The exclamation mark that appears in "domains = !
701 # +local_domains" is a negating operator, that is, it can be read as "not". The
702 # recipient's domain must not be one of those defined by "domainlist
703 # local_domains" above for this router to be used.
705 # If the router is used, any domain that resolves to 0.0.0.0 or to a loopback
706 # interface address (127.0.0.0/8) is treated as if it had no DNS entry. Note
707 # that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated as the
708 # local host inside the network stack. It is not 0.0.0.0/0, the default route.
709 # If the DNS lookup fails, no further routers are tried because of the no_more
710 # setting, and consequently the address is unrouteable.
714 domains = ! +local_domains
715 transport = signed_smtp
716 same_domain_copy_routing = yes
717 ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
722 ######################################################################
723 # TRANSPORTS CONFIGURATION #
724 ######################################################################
725 # ORDER DOES NOT MATTER #
726 # Only one appropriate transport is called for each delivery. #
727 ######################################################################
729 # A transport is used only when referenced from a router that successfully
730 # handles an address.
735 # This transport is used for delivering messages over SMTP connections.
740 tls_require_ciphers = <%= node[:ssl][:gnutls_ciphers] %>:%LATEST_RECORD_VERSION
743 # This transport is used for delivering DKIM signed messages over SMTP connections.
748 dkim_domain = ${lookup{${domain:$h_from:}}partial-lsearch{/etc/exim4/dkim-domains}{$value}}
749 dkim_selector = ${lookup{$dkim_domain}lsearch{/etc/exim4/dkim-selectors}{$value}}
750 dkim_private_key = /etc/exim4/dkim-keys/${dkim_domain}
751 dkim_identity = ${lc:${address:$h_from:}}
752 dkim_timestamps = 1209600
755 tls_require_ciphers = <%= node[:ssl][:gnutls_ciphers] %>:%LATEST_RECORD_VERSION
758 # This transport is used for handling pipe deliveries generated by alias or
759 # .forward files. If the pipe generates any standard output, it is returned
760 # to the sender of the message as a delivery error. Set return_fail_output
761 # instead of return_output if you want this to happen only when the pipe fails
762 # to complete normally. You can set different transports for aliases and
763 # forwards if you want to - see the references to address_pipe in the routers
771 # This transport is used for handling deliveries directly to files that are
772 # generated by aliasing or forwarding.
781 <% if File.directory?("/var/lib/mailman") -%>
782 # This transport is used for handling deliveries to mailman mailing lists.
786 command = /var/lib/mailman/mail/mailman \
787 '${if def:local_part_suffix \
788 {${sg{$local_part_suffix}{-(\\w+)(\\+.*)?}{\$1}}} \
791 current_directory = /var/lib/mailman
792 home_directory = /var/lib/mailman
795 freeze_exec_fail = true
799 # This transport handles mail for noreply.openstreetmap.org
803 from = OpenStreetMap <noreply@openstreetmap.org>
805 subject = Re: $header_subject:
806 headers = MIME-Version: 1.0\nContent-Type: text/plain; charset=utf-8
807 file = ${lookup{$local_part}dsearch,filter=file,ret=full{/etc/exim4/noreply}}
811 <% node[:exim][:routes].each do |name,details| -%>
812 <% if details[:command] or details[:file] or details[:maildir] -%>
813 # This transport handles mail for <%= details[:comment] -%>.
816 <% if details[:command] -%>
818 command = <%= details[:command] %>
819 home_directory = <%= details[:home_directory] %>
820 path = <%= details[:path] || "/bin:/usr/bin" %>
821 <% if details[:environment] -%>
822 environment = <%= details[:environment].map { |k,v| "#{k}=#{v}" }.join(":") %>
827 <% if details[:file] -%>
828 file = <%= details[:file] %>
829 <% elsif details[:maildir] -%>
830 directory = <%= details[:maildir] %>
837 user = <%= details[:user] %>
838 <% if details[:group] -%>
839 group = <%= details[:group] %>
845 ######################################################################
846 # RETRY CONFIGURATION #
847 ######################################################################
851 # This single retry rule applies to all domains and all errors. It specifies
852 # retries every 15 minutes for 2 hours, then increasing retry intervals,
853 # starting at 1 hour and increasing each time by a factor of 1.5, up to 16
854 # hours, then retries every 6 hours until 4 days have passed since the first
857 # WARNING: If you do not have any retry rules at all (this section of the
858 # configuration is non-existent or empty), Exim will not do any retries of
859 # messages that fail to get delivered at the first attempt. The effect will
860 # be to treat temporary errors as permanent. Therefore, DO NOT remove this
861 # retry rule unless you really don't want any retries.
863 # Address or Domain Error Retries
864 # ----------------- ----- -------
866 * * F,2h,15m; G,16h,1h,1.5; F,4d,6h
870 ######################################################################
871 # REWRITE CONFIGURATION #
872 ######################################################################
874 # There are no rewriting specifications in this default configuration file.
877 *@<%= node[:fqdn] %> "${if !match {${lookup{$1}lsearch{/etc/aliases}{$value}}}{@} {$1@openstreetmap.org}fail}" Eh
878 <% node[:exim][:rewrites].each do |rewrite| -%>
879 <%= rewrite[:pattern] %> <%= rewrite[:replacement] %> <%= rewrite[:flags] %>
884 ######################################################################
885 # AUTHENTICATION CONFIGURATION #
886 ######################################################################
888 # The following authenticators support plaintext username/password
889 # authentication using the standard PLAIN mechanism and the traditional
890 # but non-standard LOGIN mechanism, with Exim acting as the server.
891 # PLAIN and LOGIN are enough to support most MUA software.
893 # These authenticators are not complete: you need to change the
894 # server_condition settings to specify how passwords are verified.
895 # They are set up to offer authentication to the client only if the
896 # connection is encrypted with TLS, so you also need to add support
897 # for TLS. See the global configuration options section at the start
898 # of this file for more about TLS.
900 # The default RCPT ACL checks for successful authentication, and will accept
901 # messages from authenticated users from anywhere on the Internet.
905 # PLAIN authentication has no server prompts. The client sends its
906 # credentials in one lump, containing an authorization ID (which we do not
907 # use), an authentication ID, and a password. The latter two appear as
908 # $auth2 and $auth3 in the configuration and should be checked against a
909 # valid username and password. In a real configuration you would typically
910 # use $auth2 as a lookup key, and compare $auth3 against the result of the
911 # lookup, perhaps using the crypteq{}{} condition.
915 # server_set_id = $auth2
917 # server_condition = Authentication is not yet configured
918 # server_advertise_condition = ${if def:tls_cipher }
920 # LOGIN authentication has traditional prompts and responses. There is no
921 # authorization ID in this mechanism, so unlike PLAIN the username and
922 # password are $auth1 and $auth2. Apart from that you can use the same
923 # server_condition setting for both authenticators.
927 # server_set_id = $auth1
928 # server_prompts = <| Username: | Password:
929 # server_condition = Authentication is not yet configured
930 # server_advertise_condition = ${if def:tls_cipher }
933 ######################################################################
934 # CONFIGURATION FOR local_scan() #
935 ######################################################################
937 # If you have built Exim to include a local_scan() function that contains
938 # tables for private options, you can define those options here. Remember to
939 # uncomment the "begin" line. It is commented by default because it provokes
940 # an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
941 # set in the Local/Makefile.
946 # End of Exim configuration file