Commit | Line | Data |
---|---|---|
8bffe342 | 1 | # $Cambridge: exim/src/src/configure.default,v 1.12 2006/10/25 08:42:57 ph10 Exp $ |
059ec3d9 PH |
2 | |
3 | ###################################################################### | |
4 | # Runtime configuration file for Exim # | |
5 | ###################################################################### | |
6 | ||
7 | ||
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. | |
15 | ||
16 | ||
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 # | |
20 | # are ignored. | |
21 | ||
22 | ||
23 | ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ########### | |
24 | # # | |
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. # | |
30 | # # | |
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. # | |
33 | # # | |
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"). # | |
37 | # # | |
38 | ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ########### | |
39 | ||
40 | ||
41 | ||
42 | ###################################################################### | |
43 | # MAIN CONFIGURATION SETTINGS # | |
44 | ###################################################################### | |
45 | ||
46 | # Specify your host's canonical name here. This should normally be the fully | |
47 | # qualified "official" name of your host. If this option is not set, the | |
48 | # uname() function is called to obtain the name. In many cases this does | |
49 | # the right thing and you need not set anything explicitly. | |
50 | ||
51 | # primary_hostname = | |
52 | ||
53 | ||
54 | # The next three settings create two lists of domains and one list of hosts. | |
55 | # These lists are referred to later in this configuration using the syntax | |
56 | # +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They | |
57 | # are all colon-separated lists: | |
58 | ||
59 | domainlist local_domains = @ | |
60 | domainlist relay_to_domains = | |
61 | hostlist relay_from_hosts = 127.0.0.1 | |
62 | ||
63 | # Most straightforward access control requirements can be obtained by | |
53394084 | 64 | # appropriate settings of the above options. In more complicated situations, |
92db8b2d | 65 | # you may need to modify the Access Control Lists (ACLs) which appear later in |
53394084 | 66 | # this file. |
059ec3d9 PH |
67 | |
68 | # The first setting specifies your local domains, for example: | |
69 | # | |
70 | # domainlist local_domains = my.first.domain : my.second.domain | |
71 | # | |
72 | # You can use "@" to mean "the name of the local host", as in the default | |
73 | # setting above. This is the name that is specified by primary_hostname, | |
74 | # as specified above (or defaulted). If you do not want to do any local | |
75 | # deliveries, remove the "@" from the setting above. If you want to accept mail | |
76 | # addressed to your host's literal IP address, for example, mail addressed to | |
77 | # "user@[192.168.23.44]", you can add "@[]" as an item in the local domains | |
78 | # list. You also need to uncomment "allow_domain_literals" below. This is not | |
79 | # recommended for today's Internet. | |
80 | ||
81 | # The second setting specifies domains for which your host is an incoming relay. | |
82 | # If you are not doing any relaying, you should leave the list empty. However, | |
83 | # if your host is an MX backup or gateway of some kind for some domains, you | |
84 | # must set relay_to_domains to match those domains. For example: | |
85 | # | |
86 | # domainlist relay_to_domains = *.myco.com : my.friend.org | |
87 | # | |
88 | # This will allow any host to relay through your host to those domains. | |
89 | # See the section of the manual entitled "Control of relaying" for more | |
90 | # information. | |
91 | ||
92 | # The third setting specifies hosts that can use your host as an outgoing relay | |
93 | # to any other host on the Internet. Such a setting commonly refers to a | |
94 | # complete local network as well as the localhost. For example: | |
95 | # | |
96 | # hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16 | |
97 | # | |
98 | # The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you | |
99 | # have to include 127.0.0.1 if you want to allow processes on your host to send | |
100 | # SMTP mail by using the loopback address. A number of MUAs use this method of | |
101 | # sending mail. | |
102 | ||
059ec3d9 PH |
103 | # All three of these lists may contain many different kinds of item, including |
104 | # wildcarded names, regular expressions, and file lookups. See the reference | |
74e0617f PH |
105 | # manual for details. The lists above are used in the access control lists for |
106 | # checking incoming messages. The names of these ACLs are defined here: | |
059ec3d9 PH |
107 | |
108 | acl_smtp_rcpt = acl_check_rcpt | |
74e0617f PH |
109 | acl_smtp_data = acl_check_data |
110 | ||
111 | # You should not change those settings until you understand how ACLs work. | |
112 | ||
113 | ||
114 | # If you are running a version of Exim that was compiled with the content- | |
115 | # scanning extension, you can cause incoming messages to be automatically | |
116 | # scanned for viruses. You have to modify the configuration in two places to | |
117 | # set this up. The first of them is here, where you define the interface to | |
118 | # your scanner. This example is typical for ClamAV; see the manual for details | |
119 | # of what to set for other virus scanners. The second modification is in the | |
120 | # acl_check_data access control list (see below). | |
059ec3d9 | 121 | |
74e0617f PH |
122 | # av_scanner = clamd:/tmp/clamd |
123 | ||
124 | ||
125 | # For spam scanning, there is a similar option that defines the interface to | |
126 | # SpamAssassin. You do not need to set this if you are using the default, which | |
127 | # is shown in this commented example. As for virus scanning, you must also | |
128 | # modify the acl_check_data access control list to enable spam scanning. | |
129 | ||
130 | # spamd_address = 127.0.0.1 783 | |
059ec3d9 PH |
131 | |
132 | ||
6083aca0 TF |
133 | # If Exim is compiled with support for TLS, you may want to enable the |
134 | # following options so that Exim allows clients to make encrypted | |
135 | # connections. In the authenticators section below, there are template | |
136 | # configurations for plaintext username/password authentication. This kind | |
137 | # of authentication is only safe when used within a TLS connection, so the | |
138 | # authenticators will only work if the following TLS settings are turned on | |
139 | # as well. | |
140 | ||
141 | # Allow any client to use TLS. | |
142 | ||
143 | # tls_advertise_hosts = * | |
144 | ||
145 | # Specify the location of the Exim server's TLS certificate and private key. | |
146 | # The private key must not be encrypted (password protected). You can put | |
147 | # the certificate and private key in the same file, in which case you only | |
148 | # need the first setting, or in separate files, in which case you need both | |
149 | # options. | |
150 | ||
151 | # tls_certificate = /etc/ssl/exim.crt | |
152 | # tls_privatekey = /etc/ssl/exim.pem | |
153 | ||
154 | # In order to support roaming users who wish to send email from anywhere, | |
155 | # you may want to make Exim listen on other ports as well as port 25, in | |
156 | # case these users need to send email from a network that blocks port 25. | |
157 | # The standard port for this purpose is port 587, the "message submission" | |
158 | # port. See RFC 4409 for details. Microsoft MUAs cannot be configured to | |
159 | # talk the message submission protocol correctly, so if you need to support | |
160 | # them you should also allow TLS-on-connect on the traditional but | |
161 | # non-standard port 465. | |
162 | ||
163 | # daemon_smtp_ports = 25 : 465 : 587 | |
164 | # tls_on_connect_ports = 465 | |
165 | ||
166 | ||
059ec3d9 PH |
167 | # Specify the domain you want to be added to all unqualified addresses |
168 | # here. An unqualified address is one that does not contain an "@" character | |
169 | # followed by a domain. For example, "caesar@rome.example" is a fully qualified | |
170 | # address, but the string "caesar" (i.e. just a login name) is an unqualified | |
171 | # email address. Unqualified addresses are accepted only from local callers by | |
172 | # default. See the recipient_unqualified_hosts option if you want to permit | |
173 | # unqualified addresses from remote sources. If this option is not set, the | |
174 | # primary_hostname value is used for qualification. | |
175 | ||
176 | # qualify_domain = | |
177 | ||
178 | ||
179 | # If you want unqualified recipient addresses to be qualified with a different | |
180 | # domain to unqualified sender addresses, specify the recipient domain here. | |
181 | # If this option is not set, the qualify_domain value is used. | |
182 | ||
183 | # qualify_recipient = | |
184 | ||
185 | ||
186 | # The following line must be uncommented if you want Exim to recognize | |
187 | # addresses of the form "user@[10.11.12.13]" that is, with a "domain literal" | |
188 | # (an IP address) instead of a named domain. The RFCs still require this form, | |
189 | # but it makes little sense to permit mail to be sent to specific hosts by | |
190 | # their IP address in the modern Internet. This ancient format has been used | |
191 | # by those seeking to abuse hosts by using them for unwanted relaying. If you | |
192 | # really do want to support domain literals, uncomment the following line, and | |
193 | # see also the "domain_literal" router below. | |
194 | ||
195 | # allow_domain_literals | |
196 | ||
197 | ||
92db8b2d PH |
198 | # No deliveries will ever be run under the uids of users specified by |
199 | # never_users (a colon-separated list). An attempt to do so causes a panic | |
200 | # error to be logged, and the delivery to be deferred. This is a paranoic | |
201 | # safety catch. There is an even stronger safety catch in the form of the | |
202 | # FIXED_NEVER_USERS setting in the configuration for building Exim. The list of | |
203 | # users that it specifies is built into the binary, and cannot be changed. The | |
204 | # option below just adds additional users to the list. The default for | |
205 | # FIXED_NEVER_USERS is "root", but just to be absolutely sure, the default here | |
206 | # is also "root". | |
059ec3d9 PH |
207 | |
208 | # Note that the default setting means you cannot deliver mail addressed to root | |
209 | # as if it were a normal user. This isn't usually a problem, as most sites have | |
210 | # an alias for root that redirects such mail to a human administrator. | |
211 | ||
212 | never_users = root | |
213 | ||
214 | ||
215 | # The setting below causes Exim to do a reverse DNS lookup on all incoming | |
216 | # IP calls, in order to get the true host name. If you feel this is too | |
217 | # expensive, you can specify the networks for which a lookup is done, or | |
218 | # remove the setting entirely. | |
219 | ||
220 | host_lookup = * | |
221 | ||
222 | ||
223 | # The settings below, which are actually the same as the defaults in the | |
224 | # code, cause Exim to make RFC 1413 (ident) callbacks for all incoming SMTP | |
225 | # calls. You can limit the hosts to which these calls are made, and/or change | |
226 | # the timeout that is used. If you set the timeout to zero, all RFC 1413 calls | |
227 | # are disabled. RFC 1413 calls are cheap and can provide useful information | |
228 | # for tracing problem messages, but some hosts and firewalls have problems | |
229 | # with them. This can result in a timeout instead of an immediate refused | |
8def5aaf PH |
230 | # connection, leading to delays on starting up SMTP sessions. (The default was |
231 | # reduced from 30s to 5s for release 4.61.) | |
059ec3d9 PH |
232 | |
233 | rfc1413_hosts = * | |
8def5aaf | 234 | rfc1413_query_timeout = 5s |
059ec3d9 PH |
235 | |
236 | ||
237 | # By default, Exim expects all envelope addresses to be fully qualified, that | |
238 | # is, they must contain both a local part and a domain. If you want to accept | |
239 | # unqualified addresses (just a local part) from certain hosts, you can specify | |
240 | # these hosts by setting one or both of | |
241 | # | |
242 | # sender_unqualified_hosts = | |
243 | # recipient_unqualified_hosts = | |
244 | # | |
245 | # to control sender and recipient addresses, respectively. When this is done, | |
246 | # unqualified addresses are qualified using the settings of qualify_domain | |
247 | # and/or qualify_recipient (see above). | |
248 | ||
249 | ||
250 | # If you want Exim to support the "percent hack" for certain domains, | |
251 | # uncomment the following line and provide a list of domains. The "percent | |
252 | # hack" is the feature by which mail addressed to x%y@z (where z is one of | |
253 | # the domains listed) is locally rerouted to x@y and sent on. If z is not one | |
254 | # of the "percent hack" domains, x%y is treated as an ordinary local part. This | |
255 | # hack is rarely needed nowadays; you should not enable it unless you are sure | |
256 | # that you really need it. | |
257 | # | |
258 | # percent_hack_domains = | |
259 | # | |
260 | # As well as setting this option you will also need to remove the test | |
261 | # for local parts containing % in the ACL definition below. | |
262 | ||
263 | ||
264 | # When Exim can neither deliver a message nor return it to sender, it "freezes" | |
265 | # the delivery error message (aka "bounce message"). There are also other | |
266 | # circumstances in which messages get frozen. They will stay on the queue for | |
267 | # ever unless one of the following options is set. | |
268 | ||
269 | # This option unfreezes frozen bounce messages after two days, tries | |
270 | # once more to deliver them, and ignores any delivery failures. | |
271 | ||
272 | ignore_bounce_errors_after = 2d | |
273 | ||
274 | # This option cancels (removes) frozen messages that are older than a week. | |
275 | ||
276 | timeout_frozen_after = 7d | |
277 | ||
278 | ||
92db8b2d PH |
279 | # By default, messages that are waiting on Exim's queue are all held in a |
280 | # single directory called "input" which it itself within Exim's spool | |
281 | # directory. (The default spool directory is specified when Exim is built, and | |
282 | # is often /var/spool/exim/.) Exim works best when its queue is kept short, but | |
283 | # there are circumstances where this is not always possible. If you uncomment | |
284 | # the setting below, messages on the queue are held in 62 subdirectories of | |
285 | # "input" instead of all in the same directory. The subdirectories are called | |
286 | # 0, 1, ... A, B, ... a, b, ... z. This has two benefits: (1) If your file | |
287 | # system degrades with many files in one directory, this is less likely to | |
288 | # happen; (2) Exim can process the queue one subdirectory at a time instead of | |
289 | # all at once, which can give better performance with large queues. | |
290 | ||
291 | # split_spool_directory = true | |
292 | ||
293 | ||
059ec3d9 PH |
294 | |
295 | ###################################################################### | |
296 | # ACL CONFIGURATION # | |
297 | # Specifies access control lists for incoming SMTP mail # | |
298 | ###################################################################### | |
299 | ||
300 | begin acl | |
301 | ||
302 | # This access control list is used for every RCPT command in an incoming | |
303 | # SMTP message. The tests are run in order until the address is either | |
304 | # accepted or denied. | |
305 | ||
306 | acl_check_rcpt: | |
307 | ||
308 | # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by | |
309 | # testing for an empty sending host field. | |
310 | ||
311 | accept hosts = : | |
312 | ||
313 | ############################################################################# | |
314 | # The following section of the ACL is concerned with local parts that contain | |
315 | # @ or % or ! or / or | or dots in unusual places. | |
316 | # | |
317 | # The characters other than dots are rarely found in genuine local parts, but | |
318 | # are often tried by people looking to circumvent relaying restrictions. | |
319 | # Therefore, although they are valid in local parts, these rules lock them | |
320 | # out, as a precaution. | |
321 | # | |
322 | # Empty components (two dots in a row) are not valid in RFC 2822, but Exim | |
323 | # allows them because they have been encountered. (Consider local parts | |
324 | # constructed as "firstinitial.secondinitial.familyname" when applied to | |
325 | # someone like me, who has no second initial.) However, a local part starting | |
326 | # with a dot or containing /../ can cause trouble if it is used as part of a | |
327 | # file name (e.g. for a mailing list). This is also true for local parts that | |
328 | # contain slashes. A pipe symbol can also be troublesome if the local part is | |
329 | # incorporated unthinkingly into a shell command line. | |
330 | # | |
331 | # Two different rules are used. The first one is stricter, and is applied to | |
332 | # messages that are addressed to one of the local domains handled by this | |
53394084 PH |
333 | # host. The line "domains = +local_domains" restricts it to domains that are |
334 | # defined by the "domainlist local_domains" setting above. The rule blocks | |
335 | # local parts that begin with a dot or contain @ % ! / or |. If you have | |
336 | # local accounts that include these characters, you will have to modify this | |
337 | # rule. | |
059ec3d9 PH |
338 | |
339 | deny message = Restricted characters in address | |
340 | domains = +local_domains | |
341 | local_parts = ^[.] : ^.*[@%!/|] | |
342 | ||
53394084 PH |
343 | # The second rule applies to all other domains, and is less strict. The line |
344 | # "domains = !+local_domains" restricts it to domains that are NOT defined by | |
345 | # the "domainlist local_domains" setting above. The exclamation mark is a | |
346 | # negating operator. This rule allows your own users to send outgoing | |
347 | # messages to sites that use slashes and vertical bars in their local parts. | |
348 | # It blocks local parts that begin with a dot, slash, or vertical bar, but | |
349 | # allows these characters within the local part. However, the sequence /../ | |
350 | # is barred. The use of @ % and ! is blocked, as before. The motivation here | |
351 | # is to prevent your users (or your users' viruses) from mounting certain | |
352 | # kinds of attack on remote sites. | |
059ec3d9 PH |
353 | |
354 | deny message = Restricted characters in address | |
355 | domains = !+local_domains | |
356 | local_parts = ^[./|] : ^.*[@%!] : ^.*/\\.\\./ | |
357 | ############################################################################# | |
358 | ||
359 | # Accept mail to postmaster in any local domain, regardless of the source, | |
360 | # and without verifying the sender. | |
361 | ||
362 | accept local_parts = postmaster | |
363 | domains = +local_domains | |
364 | ||
365 | # Deny unless the sender address can be verified. | |
366 | ||
367 | require verify = sender | |
368 | ||
5de37277 | 369 | # Accept if the message comes from one of the hosts for which we are an |
cc38ddbf PH |
370 | # outgoing relay. It is assumed that such hosts are most likely to be MUAs, |
371 | # so we set control=submission to make Exim treat the message as a | |
372 | # submission. It will fix up various errors in the message, for example, the | |
373 | # lack of a Date: header line. If you are actually relaying out out from | |
374 | # MTAs, you may want to disable this. If you are handling both relaying from | |
375 | # MTAs and submissions from MUAs you should probably split them into two | |
376 | # lists, and handle them differently. | |
377 | ||
378 | # Recipient verification is omitted here, because in many cases the clients | |
379 | # are dumb MUAs that don't cope well with SMTP error responses. If you are | |
380 | # actually relaying out from MTAs, you should probably add recipient | |
381 | # verification here. | |
382 | ||
383 | # Note that, by putting this test before any DNS black list checks, you will | |
384 | # always accept from these hosts, even if they end up on a black list. The | |
385 | # assumption is that they are your friends, and if they get onto a black | |
386 | # list, it is a mistake. | |
5de37277 PH |
387 | |
388 | accept hosts = +relay_from_hosts | |
cc38ddbf | 389 | control = submission |
5de37277 PH |
390 | |
391 | # Accept if the message arrived over an authenticated connection, from | |
392 | # any host. Again, these messages are usually from MUAs, so recipient | |
cc38ddbf PH |
393 | # verification is omitted, and submission mode is set. And again, we do this |
394 | # check before any black list tests. | |
5de37277 PH |
395 | |
396 | accept authenticated = * | |
cc38ddbf | 397 | control = submission |
5de37277 | 398 | |
9ecb03f3 PH |
399 | # Insist that any other recipient address that we accept is either in one of |
400 | # our local domains, or is in a domain for which we explicitly allow | |
401 | # relaying. Any other domain is rejected as being unacceptable for relaying. | |
402 | ||
403 | require message = relay not permitted | |
8bffe342 | 404 | domains = +local_domains : +relay_to_domains |
9ecb03f3 PH |
405 | |
406 | # We also require all accepted addresses to be verifiable. This check will | |
407 | # do local part verification for local domains, but only check the domain | |
408 | # for remote domains. The only way to check local parts for the remote | |
409 | # relay domains is to use a callout (add /callout), but please read the | |
410 | # documentation about callouts before doing this. | |
411 | ||
412 | require verify = recipient | |
413 | ||
059ec3d9 | 414 | ############################################################################# |
5de37277 PH |
415 | # There are no default checks on DNS black lists because the domains that |
416 | # contain these lists are changing all the time. However, here are two | |
417 | # examples of how you can get Exim to perform a DNS black list lookup at this | |
418 | # point. The first one denies, whereas the second just warns. | |
059ec3d9 PH |
419 | # |
420 | # deny message = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text | |
421 | # dnslists = black.list.example | |
422 | # | |
42119b09 PH |
423 | # warn dnslists = black.list.example |
424 | # add_header = X-Warning: $sender_host_address is in a black list at $dnslist_domain | |
059ec3d9 | 425 | # log_message = found in $dnslist_domain |
059ec3d9 PH |
426 | ############################################################################# |
427 | ||
a4e3111f PH |
428 | ############################################################################# |
429 | # This check is commented out because it is recognized that not every | |
430 | # sysadmin will want to do it. If you enable it, the check performs | |
431 | # Client SMTP Authorization (csa) checks on the sending host. These checks | |
432 | # do DNS lookups for SRV records. The CSA proposal is currently (May 2005) | |
433 | # an Internet draft. You can, of course, add additional conditions to this | |
434 | # ACL statement to restrict the CSA checks to certain hosts only. | |
435 | # | |
436 | # require verify = csa | |
437 | ############################################################################# | |
438 | ||
9ecb03f3 PH |
439 | # At this point, the address has passed all the checks that have been |
440 | # configured, so we accept it unconditionally. | |
059ec3d9 | 441 | |
9ecb03f3 | 442 | accept |
059ec3d9 PH |
443 | |
444 | ||
74e0617f PH |
445 | # This ACL is used after the contents of a message have been received. This |
446 | # is the ACL in which you can test a message's headers or body, and in | |
447 | # particular, this is where you can invoke external virus or spam scanners. | |
448 | # Some suggested ways of configuring these tests are shown below, commented | |
449 | # out. Without any tests, this ACL accepts all messages. If you want to use | |
450 | # such tests, you must ensure that Exim is compiled with the content-scanning | |
451 | # extension (WITH_CONTENT_SCAN=yes in Local/Makefile). | |
452 | ||
453 | acl_check_data: | |
454 | ||
455 | # Deny if the message contains a virus. Before enabling this check, you | |
456 | # must install a virus scanner and set the av_scanner option above. | |
457 | # | |
42119b09 PH |
458 | # deny malware = * |
459 | # message = This message contains a virus ($malware_name). | |
74e0617f PH |
460 | |
461 | # Add headers to a message if it is judged to be spam. Before enabling this, | |
462 | # you must install SpamAssassin. You may also need to set the spamd_address | |
463 | # option above. | |
464 | # | |
42119b09 PH |
465 | # warn spam = nobody |
466 | # add_header = X-Spam_score: $spam_score\n\ | |
467 | # X-Spam_score_int: $spam_score_int\n\ | |
468 | # X-Spam_bar: $spam_bar\n\ | |
469 | # X-Spam_report: $spam_report | |
74e0617f PH |
470 | |
471 | # Accept the message. | |
472 | ||
473 | accept | |
474 | ||
475 | ||
059ec3d9 PH |
476 | |
477 | ###################################################################### | |
478 | # ROUTERS CONFIGURATION # | |
479 | # Specifies how addresses are handled # | |
480 | ###################################################################### | |
481 | # THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! # | |
482 | # An address is passed to each router in turn until it is accepted. # | |
483 | ###################################################################### | |
484 | ||
485 | begin routers | |
486 | ||
487 | # This router routes to remote hosts over SMTP by explicit IP address, | |
488 | # when an email address is given in "domain literal" form, for example, | |
489 | # <user@[192.168.35.64]>. The RFCs require this facility. However, it is | |
490 | # little-known these days, and has been exploited by evil people seeking | |
491 | # to abuse SMTP relays. Consequently it is commented out in the default | |
492 | # configuration. If you uncomment this router, you also need to uncomment | |
493 | # allow_domain_literals above, so that Exim can recognize the syntax of | |
494 | # domain literal addresses. | |
495 | ||
496 | # domain_literal: | |
497 | # driver = ipliteral | |
498 | # domains = ! +local_domains | |
499 | # transport = remote_smtp | |
500 | ||
501 | ||
502 | # This router routes addresses that are not in local domains by doing a DNS | |
53394084 PH |
503 | # lookup on the domain name. The exclamation mark that appears in "domains = ! |
504 | # +local_domains" is a negating operator, that is, it can be read as "not". The | |
505 | # recipient's domain must not be one of those defined by "domainlist | |
506 | # local_domains" above for this router to be used. | |
507 | # | |
508 | # If the router is used, any domain that resolves to 0.0.0.0 or to a loopback | |
509 | # interface address (127.0.0.0/8) is treated as if it had no DNS entry. Note | |
510 | # that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated as the | |
511 | # local host inside the network stack. It is not 0.0.0.0/0, the default route. | |
512 | # If the DNS lookup fails, no further routers are tried because of the no_more | |
513 | # setting, and consequently the address is unrouteable. | |
059ec3d9 PH |
514 | |
515 | dnslookup: | |
516 | driver = dnslookup | |
517 | domains = ! +local_domains | |
518 | transport = remote_smtp | |
519 | ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 | |
520 | no_more | |
521 | ||
522 | ||
53394084 PH |
523 | # The remaining routers handle addresses in the local domain(s), that is those |
524 | # domains that are defined by "domainlist local_domains" above. | |
059ec3d9 PH |
525 | |
526 | ||
527 | # This router handles aliasing using a linearly searched alias file with the | |
528 | # name SYSTEM_ALIASES_FILE. When this configuration is installed automatically, | |
529 | # the name gets inserted into this file from whatever is set in Exim's | |
530 | # build-time configuration. The default path is the traditional /etc/aliases. | |
531 | # If you install this configuration by hand, you need to specify the correct | |
532 | # path in the "data" setting below. | |
533 | # | |
534 | ##### NB You must ensure that the alias file exists. It used to be the case | |
535 | ##### NB that every Unix had that file, because it was the Sendmail default. | |
536 | ##### NB These days, there are systems that don't have it. Your aliases | |
537 | ##### NB file should at least contain an alias for "postmaster". | |
538 | # | |
539 | # If any of your aliases expand to pipes or files, you will need to set | |
540 | # up a user and a group for these deliveries to run under. You can do | |
541 | # this by uncommenting the "user" option below (changing the user name | |
542 | # as appropriate) and adding a "group" option if necessary. Alternatively, you | |
543 | # can specify "user" on the transports that are used. Note that the transports | |
544 | # listed below are the same as are used for .forward files; you might want | |
545 | # to set up different ones for pipe and file deliveries from aliases. | |
546 | ||
547 | system_aliases: | |
548 | driver = redirect | |
549 | allow_fail | |
550 | allow_defer | |
551 | data = ${lookup{$local_part}lsearch{SYSTEM_ALIASES_FILE}} | |
552 | # user = exim | |
553 | file_transport = address_file | |
554 | pipe_transport = address_pipe | |
555 | ||
556 | ||
557 | # This router handles forwarding using traditional .forward files in users' | |
558 | # home directories. If you want it also to allow mail filtering when a forward | |
559 | # file starts with the string "# Exim filter" or "# Sieve filter", uncomment | |
560 | # the "allow_filter" option. | |
561 | ||
562 | # If you want this router to treat local parts with suffixes introduced by "-" | |
563 | # or "+" characters as if the suffixes did not exist, uncomment the two local_ | |
564 | # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated | |
565 | # in the same way as xxxx@your.domain by this router. You probably want to make | |
566 | # the same change to the localuser router. | |
567 | ||
568 | # The no_verify setting means that this router is skipped when Exim is | |
569 | # verifying addresses. Similarly, no_expn means that this router is skipped if | |
570 | # Exim is processing an EXPN command. | |
571 | ||
572 | # The check_ancestor option means that if the forward file generates an | |
573 | # address that is an ancestor of the current one, the current one gets | |
574 | # passed on instead. This covers the case where A is aliased to B and B | |
575 | # has a .forward file pointing to A. | |
576 | ||
577 | # The three transports specified at the end are those that are used when | |
578 | # forwarding generates a direct delivery to a file, or to a pipe, or sets | |
579 | # up an auto-reply, respectively. | |
580 | ||
581 | userforward: | |
582 | driver = redirect | |
583 | check_local_user | |
584 | # local_part_suffix = +* : -* | |
585 | # local_part_suffix_optional | |
586 | file = $home/.forward | |
587 | # allow_filter | |
588 | no_verify | |
589 | no_expn | |
590 | check_ancestor | |
591 | file_transport = address_file | |
592 | pipe_transport = address_pipe | |
593 | reply_transport = address_reply | |
594 | ||
595 | ||
596 | # This router matches local user mailboxes. If the router fails, the error | |
597 | # message is "Unknown user". | |
598 | ||
599 | # If you want this router to treat local parts with suffixes introduced by "-" | |
600 | # or "+" characters as if the suffixes did not exist, uncomment the two local_ | |
601 | # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated | |
602 | # in the same way as xxxx@your.domain by this router. | |
603 | ||
604 | localuser: | |
605 | driver = accept | |
606 | check_local_user | |
607 | # local_part_suffix = +* : -* | |
608 | # local_part_suffix_optional | |
609 | transport = local_delivery | |
610 | cannot_route_message = Unknown user | |
611 | ||
612 | ||
613 | ||
614 | ###################################################################### | |
615 | # TRANSPORTS CONFIGURATION # | |
616 | ###################################################################### | |
617 | # ORDER DOES NOT MATTER # | |
618 | # Only one appropriate transport is called for each delivery. # | |
619 | ###################################################################### | |
620 | ||
621 | # A transport is used only when referenced from a router that successfully | |
622 | # handles an address. | |
623 | ||
624 | begin transports | |
625 | ||
626 | ||
627 | # This transport is used for delivering messages over SMTP connections. | |
628 | ||
629 | remote_smtp: | |
630 | driver = smtp | |
631 | ||
632 | ||
633 | # This transport is used for local delivery to user mailboxes in traditional | |
634 | # BSD mailbox format. By default it will be run under the uid and gid of the | |
635 | # local user, and requires the sticky bit to be set on the /var/mail directory. | |
636 | # Some systems use the alternative approach of running mail deliveries under a | |
637 | # particular group instead of using the sticky bit. The commented options below | |
638 | # show how this can be done. | |
639 | ||
640 | local_delivery: | |
641 | driver = appendfile | |
642 | file = /var/mail/$local_part | |
643 | delivery_date_add | |
644 | envelope_to_add | |
645 | return_path_add | |
646 | # group = mail | |
647 | # mode = 0660 | |
648 | ||
649 | ||
650 | # This transport is used for handling pipe deliveries generated by alias or | |
651 | # .forward files. If the pipe generates any standard output, it is returned | |
652 | # to the sender of the message as a delivery error. Set return_fail_output | |
653 | # instead of return_output if you want this to happen only when the pipe fails | |
654 | # to complete normally. You can set different transports for aliases and | |
655 | # forwards if you want to - see the references to address_pipe in the routers | |
656 | # section above. | |
657 | ||
658 | address_pipe: | |
659 | driver = pipe | |
660 | return_output | |
661 | ||
662 | ||
663 | # This transport is used for handling deliveries directly to files that are | |
664 | # generated by aliasing or forwarding. | |
665 | ||
666 | address_file: | |
667 | driver = appendfile | |
668 | delivery_date_add | |
669 | envelope_to_add | |
670 | return_path_add | |
671 | ||
672 | ||
673 | # This transport is used for handling autoreplies generated by the filtering | |
674 | # option of the userforward router. | |
675 | ||
676 | address_reply: | |
677 | driver = autoreply | |
678 | ||
679 | ||
680 | ||
681 | ###################################################################### | |
682 | # RETRY CONFIGURATION # | |
683 | ###################################################################### | |
684 | ||
685 | begin retry | |
686 | ||
687 | # This single retry rule applies to all domains and all errors. It specifies | |
688 | # retries every 15 minutes for 2 hours, then increasing retry intervals, | |
689 | # starting at 1 hour and increasing each time by a factor of 1.5, up to 16 | |
690 | # hours, then retries every 6 hours until 4 days have passed since the first | |
691 | # failed delivery. | |
692 | ||
693 | # Address or Domain Error Retries | |
694 | # ----------------- ----- ------- | |
695 | ||
696 | * * F,2h,15m; G,16h,1h,1.5; F,4d,6h | |
697 | ||
698 | ||
699 | ||
700 | ###################################################################### | |
701 | # REWRITE CONFIGURATION # | |
702 | ###################################################################### | |
703 | ||
704 | # There are no rewriting specifications in this default configuration file. | |
705 | ||
706 | begin rewrite | |
707 | ||
708 | ||
709 | ||
710 | ###################################################################### | |
711 | # AUTHENTICATION CONFIGURATION # | |
712 | ###################################################################### | |
713 | ||
6083aca0 TF |
714 | # The following authenticators support plaintext username/password |
715 | # authentication using the standard PLAIN mechanism and the traditional | |
716 | # but non-standard LOGIN mechanism, with Exim acting as the server. | |
717 | # PLAIN and LOGIN are enough to support most MUA software. | |
718 | # | |
719 | # These authenticators are not complete: you need to change the | |
720 | # server_condition settings to specify how passwords are verified. | |
721 | # They are set up to offer authentication to the client only if the | |
722 | # connection is encrypted with TLS, so you also need to add support | |
723 | # for TLS. See the global configuration options section at the start | |
724 | # of this file for more about TLS. | |
725 | # | |
726 | # The default RCPT ACL checks for successful authentication, and will accept | |
727 | # messages from authenticated users from anywhere on the Internet. | |
059ec3d9 PH |
728 | |
729 | begin authenticators | |
730 | ||
6083aca0 TF |
731 | # PLAIN authentication has no server prompts. The client sends its |
732 | # credentials in one lump, containing an authorization ID (which we do not | |
733 | # use), an authentication ID, and a password. The latter two appear as | |
734 | # $auth2 and $auth3 in the configuration and should be checked against a | |
735 | # valid username and password. In a real configuration you would typically | |
736 | # use $auth2 as a lookup key, and compare $auth3 against the result of the | |
737 | # lookup, perhaps using the crypteq{}{} condition. | |
738 | ||
739 | #PLAIN: | |
740 | # driver = plaintext | |
741 | # server_set_id = $auth2 | |
742 | # server_prompts = : | |
743 | # server_condition = Authentication is not yet configured | |
744 | # server_advertise_condition = ${if def:tls_cipher } | |
745 | ||
746 | # LOGIN authentication has traditional prompts and responses. There is no | |
747 | # authorization ID in this mechanism, so unlike PLAIN the username and | |
748 | # password are $auth1 and $auth2. Apart from that you can use the same | |
749 | # server_condition setting for both authenticators. | |
750 | ||
751 | #LOGIN: | |
752 | # driver = plaintext | |
753 | # server_set_id = $auth1 | |
754 | # server_prompts = <| Username: | Password: | |
755 | # server_condition = Authentication is not yet configured | |
756 | # server_advertise_condition = ${if def:tls_cipher } | |
059ec3d9 PH |
757 | |
758 | ||
759 | ###################################################################### | |
760 | # CONFIGURATION FOR local_scan() # | |
761 | ###################################################################### | |
762 | ||
763 | # If you have built Exim to include a local_scan() function that contains | |
764 | # tables for private options, you can define those options here. Remember to | |
765 | # uncomment the "begin" line. It is commented by default because it provokes | |
766 | # an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS | |
767 | # set in the Local/Makefile. | |
768 | ||
769 | # begin local_scan | |
770 | ||
771 | ||
772 | # End of Exim configuration file |