]>
Commit | Line | Data |
---|---|---|
a59efb33 AM |
1 | ###################################################################### |
2 | # Runtime configuration file for Exim # | |
3 | ###################################################################### | |
4 | ||
5 | ||
6 | # This is a default configuration file which will operate correctly in | |
7 | # uncomplicated installations. Please see the manual for a complete list | |
8 | # of all the runtime configuration options that can be included in a | |
9 | # configuration file. There are many more than are mentioned here. The | |
10 | # manual is in the file doc/spec.txt in the Exim distribution as a plain | |
11 | # ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are available | |
12 | # from the Exim ftp sites. The manual is also online at the Exim web sites. | |
13 | ||
14 | ||
15 | # This file is divided into several parts, all but the first of which are | |
16 | # headed by a line starting with the word "begin". Only those parts that | |
17 | # are required need to be present. Blank lines, and lines starting with # | |
18 | # are ignored. | |
19 | ||
20 | ||
21 | ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ########### | |
22 | # # | |
23 | # Whenever you change Exim's configuration file, you *must* remember to # | |
24 | # HUP the Exim daemon, because it will not pick up the new configuration # | |
25 | # until you do. However, any other Exim processes that are started, for # | |
26 | # example, a process started by an MUA in order to send a message, will # | |
27 | # see the new configuration as soon as it is in place. # | |
28 | # # | |
29 | # You do not need to HUP the daemon for changes in auxiliary files that # | |
30 | # are referenced from this file. They are read every time they are used. # | |
31 | # # | |
32 | # It is usually a good idea to test a new configuration for syntactic # | |
33 | # correctness before installing it (for example, by running the command # | |
34 | # "exim -C /config/file.new -bV"). # | |
35 | # # | |
36 | ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ########### | |
37 | ||
38 | ||
39 | ||
40 | ###################################################################### | |
41 | # MAIN CONFIGURATION SETTINGS # | |
42 | ###################################################################### | |
43 | ||
688a0e74 AM |
44 | # Log more information |
45 | log_selector = +all -arguments | |
46 | ||
a59efb33 AM |
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. | |
51 | ||
52 | # primary_hostname = | |
53 | ||
fd371bbf | 54 | # daemon_smtp_ports = 25 : 465 |
d1989dea | 55 | # tls_on_connect_ports = 465 |
a59efb33 AM |
56 | |
57 | # The next three settings create two lists of domains and one list of hosts. | |
58 | # These lists are referred to later in this configuration using the syntax | |
59 | # +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They | |
60 | # are all colon-separated lists: | |
61 | ||
62 | domainlist local_domains = @ | |
63 | domainlist relay_to_domains = | |
64 | hostlist relay_from_hosts = 127.0.0.1 | |
65 | ||
26d60792 | 66 | # If You wish to enable support for STARTTLS, uncomment folowing lines: |
42952ff9 | 67 | |
26d60792 ŁJM |
68 | # tls_certificate = /etc/openssl/mail.crt |
69 | # tls_privatekey = /etc/openssl/mail.key | |
70 | # tls_advertise_hosts = * | |
42952ff9 | 71 | |
4fd05b1b ŁJM |
72 | # You can use self-signed cerficates (you will need openssl-tools package): |
73 | ||
74 | # openssl genrsa -out /etc/openssl/mail.key 1024 | |
75 | # openssl req -new -x509 -days 365 -key /etc/openssl/mail.key -out /etc/openssl/mail.crt | |
76 | ||
a59efb33 AM |
77 | # Most straightforward access control requirements can be obtained by |
78 | # appropriate settings of the above options. In more complicated situations, you | |
79 | # may need to modify the Access Control List (ACL) which appears later in this | |
80 | # file. | |
81 | ||
82 | # The first setting specifies your local domains, for example: | |
83 | # | |
84 | # domainlist local_domains = my.first.domain : my.second.domain | |
85 | # | |
86 | # You can use "@" to mean "the name of the local host", as in the default | |
87 | # setting above. This is the name that is specified by primary_hostname, | |
88 | # as specified above (or defaulted). If you do not want to do any local | |
26d60792 | 89 | # deliveries, remove the "@" from the setting above. If you want to accept mail |
a59efb33 AM |
90 | # addressed to your host's literal IP address, for example, mail addressed to |
91 | # "user@[192.168.23.44]", you can add "@[]" as an item in the local domains | |
92 | # list. You also need to uncomment "allow_domain_literals" below. This is not | |
93 | # recommended for today's Internet. | |
94 | ||
95 | # The second setting specifies domains for which your host is an incoming relay. | |
96 | # If you are not doing any relaying, you should leave the list empty. However, | |
97 | # if your host is an MX backup or gateway of some kind for some domains, you | |
98 | # must set relay_to_domains to match those domains. For example: | |
99 | # | |
100 | # domainlist relay_to_domains = *.myco.com : my.friend.org | |
101 | # | |
102 | # This will allow any host to relay through your host to those domains. | |
103 | # See the section of the manual entitled "Control of relaying" for more | |
104 | # information. | |
105 | ||
106 | # The third setting specifies hosts that can use your host as an outgoing relay | |
107 | # to any other host on the Internet. Such a setting commonly refers to a | |
108 | # complete local network as well as the localhost. For example: | |
109 | # | |
110 | # hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16 | |
111 | # | |
112 | # The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you | |
113 | # have to include 127.0.0.1 if you want to allow processes on your host to send | |
114 | # SMTP mail by using the loopback address. A number of MUAs use this method of | |
115 | # sending mail. | |
116 | ||
117 | ||
118 | # All three of these lists may contain many different kinds of item, including | |
119 | # wildcarded names, regular expressions, and file lookups. See the reference | |
120 | # manual for details. The lists above are used in the access control list for | |
121 | # incoming messages. The name of this ACL is defined here: | |
122 | ||
123 | acl_smtp_rcpt = acl_check_rcpt | |
124 | ||
125 | # You should not change that setting until you understand how ACLs work. | |
126 | ||
26d60792 ŁJM |
127 | # The following ACL entries are used if you want to do content scanning with |
128 | # the exiscan-acl patch. When you uncomment one of these lines, you must also | |
129 | # review the respective entries in the ACL section further below. | |
130 | ||
131 | # acl_smtp_mime = acl_check_mime | |
132 | # acl_smtp_data = acl_check_content | |
133 | ||
134 | # This configuration variable defines the virus scanner that is used with | |
135 | # the 'malware' ACL condition of the exiscan acl-patch. If you do not use | |
136 | # virus scanning, leave it commented. Please read doc/exiscan-acl-readme.txt | |
137 | # for a list of supported scanners. | |
138 | ||
139 | # av_scanner = sophie:/var/run/sophie | |
140 | ||
141 | # The following setting is only needed if you use the 'spam' ACL condition | |
142 | # of the exiscan-acl patch. It specifies on which host and port the SpamAssassin | |
143 | # "spamd" daemon is listening. If you do not use this condition, or you use | |
144 | # the default of "127.0.0.1 783", you can omit this option. | |
145 | ||
146 | # spamd_address = 127.0.0.1 783 | |
a59efb33 AM |
147 | |
148 | # Specify the domain you want to be added to all unqualified addresses | |
149 | # here. An unqualified address is one that does not contain an "@" character | |
26d60792 | 150 | # followed by a domain. For example, "caesar@rome.example" is a fully qualified |
a59efb33 AM |
151 | # address, but the string "caesar" (i.e. just a login name) is an unqualified |
152 | # email address. Unqualified addresses are accepted only from local callers by | |
153 | # default. See the recipient_unqualified_hosts option if you want to permit | |
154 | # unqualified addresses from remote sources. If this option is not set, the | |
155 | # primary_hostname value is used for qualification. | |
156 | ||
157 | # qualify_domain = | |
158 | ||
159 | ||
160 | # If you want unqualified recipient addresses to be qualified with a different | |
161 | # domain to unqualified sender addresses, specify the recipient domain here. | |
162 | # If this option is not set, the qualify_domain value is used. | |
163 | ||
164 | # qualify_recipient = | |
165 | ||
166 | ||
167 | # The following line must be uncommented if you want Exim to recognize | |
168 | # addresses of the form "user@[10.11.12.13]" that is, with a "domain literal" | |
169 | # (an IP address) instead of a named domain. The RFCs still require this form, | |
170 | # but it makes little sense to permit mail to be sent to specific hosts by | |
171 | # their IP address in the modern Internet. This ancient format has been used | |
172 | # by those seeking to abuse hosts by using them for unwanted relaying. If you | |
173 | # really do want to support domain literals, uncomment the following line, and | |
174 | # see also the "domain_literal" router below. | |
175 | ||
176 | # allow_domain_literals | |
177 | ||
178 | ||
179 | # No deliveries will ever be run under the uids of these users (a colon- | |
180 | # separated list). An attempt to do so causes a panic error to be logged, and | |
26d60792 ŁJM |
181 | # the delivery to be deferred. This is a paranoic safety catch. There is an |
182 | # even stronger safety catch in the form of the FIXED_NEVER_USERS setting | |
183 | # in the configuration for building Exim. The list of users that it specifies | |
184 | # is built into the binary, and cannot be changed. The option below just adds | |
185 | # additional users to the list. The default for FIXED_NEVER_USERS is "root", | |
186 | # but just to be absolutely sure, the default here is also "root". | |
187 | ||
188 | # Note that the default setting means you cannot deliver mail addressed to root | |
189 | # as if it were a normal user. This isn't usually a problem, as most sites have | |
190 | # an alias for root that redirects such mail to a human administrator. | |
191 | ||
a59efb33 AM |
192 | never_users = root |
193 | ||
194 | ||
195 | # The setting below causes Exim to do a reverse DNS lookup on all incoming | |
196 | # IP calls, in order to get the true host name. If you feel this is too | |
197 | # expensive, you can specify the networks for which a lookup is done, or | |
198 | # remove the setting entirely. | |
199 | ||
200 | host_lookup = * | |
201 | ||
202 | ||
203 | # The settings below, which are actually the same as the defaults in the | |
204 | # code, cause Exim to make RFC 1413 (ident) callbacks for all incoming SMTP | |
205 | # calls. You can limit the hosts to which these calls are made, and/or change | |
206 | # the timeout that is used. If you set the timeout to zero, all RFC 1413 calls | |
207 | # are disabled. RFC 1413 calls are cheap and can provide useful information | |
208 | # for tracing problem messages, but some hosts and firewalls have problems | |
209 | # with them. This can result in a timeout instead of an immediate refused | |
210 | # connection, leading to delays on starting up an SMTP session. | |
211 | ||
212 | rfc1413_hosts = * | |
213 | rfc1413_query_timeout = 30s | |
214 | ||
215 | ||
216 | # By default, Exim expects all envelope addresses to be fully qualified, that | |
217 | # is, they must contain both a local part and a domain. If you want to accept | |
218 | # unqualified addresses (just a local part) from certain hosts, you can specify | |
219 | # these hosts by setting one or both of | |
220 | # | |
221 | # sender_unqualified_hosts = | |
222 | # recipient_unqualified_hosts = | |
223 | # | |
224 | # to control sender and recipient addresses, respectively. When this is done, | |
225 | # unqualified addresses are qualified using the settings of qualify_domain | |
226 | # and/or qualify_recipient (see above). | |
227 | ||
228 | ||
229 | # If you want Exim to support the "percent hack" for certain domains, | |
230 | # uncomment the following line and provide a list of domains. The "percent | |
231 | # hack" is the feature by which mail addressed to x%y@z (where z is one of | |
232 | # the domains listed) is locally rerouted to x@y and sent on. If z is not one | |
233 | # of the "percent hack" domains, x%y is treated as an ordinary local part. This | |
234 | # hack is rarely needed nowadays; you should not enable it unless you are sure | |
235 | # that you really need it. | |
236 | # | |
237 | # percent_hack_domains = | |
238 | # | |
239 | # As well as setting this option you will also need to remove the test | |
240 | # for local parts containing % in the ACL definition below. | |
241 | ||
242 | ||
243 | # When Exim can neither deliver a message nor return it to sender, it "freezes" | |
244 | # the delivery error message (aka "bounce message"). There are also other | |
245 | # circumstances in which messages get frozen. They will stay on the queue for | |
246 | # ever unless one of the following options is set. | |
247 | ||
248 | # This option unfreezes frozen bounce messages after two days, tries | |
249 | # once more to deliver them, and ignores any delivery failures. | |
250 | ||
251 | ignore_bounce_errors_after = 2d | |
252 | ||
253 | # This option cancels (removes) frozen messages that are older than a week. | |
254 | ||
255 | timeout_frozen_after = 7d | |
256 | ||
257 | ||
258 | ||
259 | ###################################################################### | |
260 | # ACL CONFIGURATION # | |
261 | # Specifies access control lists for incoming SMTP mail # | |
262 | ###################################################################### | |
263 | ||
264 | begin acl | |
265 | ||
266 | # This access control list is used for every RCPT command in an incoming | |
267 | # SMTP message. The tests are run in order until the address is either | |
268 | # accepted or denied. | |
269 | ||
270 | acl_check_rcpt: | |
271 | ||
272 | # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by | |
273 | # testing for an empty sending host field. | |
274 | ||
275 | accept hosts = : | |
276 | ||
26d60792 ŁJM |
277 | ############################################################################# |
278 | # The following section of the ACL is concerned with local parts that contain | |
279 | # @ or % or ! or / or | or dots in unusual places. | |
280 | # | |
281 | # The characters other than dots are rarely found in genuine local parts, but | |
282 | # are often tried by people looking to circumvent relaying restrictions. | |
283 | # Therefore, although they are valid in local parts, these rules lock them | |
284 | # out, as a precaution. | |
285 | # | |
286 | # Empty components (two dots in a row) are not valid in RFC 2822, but Exim | |
287 | # allows them because they have been encountered. (Consider local parts | |
288 | # constructed as "firstinitial.secondinitial.familyname" when applied to | |
289 | # someone like me, who has no second initial.) However, a local part starting | |
290 | # with a dot or containing /../ can cause trouble if it is used as part of a | |
291 | # file name (e.g. for a mailing list). This is also true for local parts that | |
292 | # contain slashes. A pipe symbol can also be troublesome if the local part is | |
293 | # incorporated unthinkingly into a shell command line. | |
294 | # | |
295 | # Two different rules are used. The first one is stricter, and is applied to | |
296 | # messages that are addressed to one of the local domains handled by this | |
297 | # host. It blocks local parts that begin with a dot or contain @ % ! / or |. | |
298 | # If you have local accounts that include these characters, you will have to | |
299 | # modify this rule. | |
300 | ||
301 | deny message = Restricted characters in address | |
302 | domains = +local_domains | |
303 | local_parts = ^[.] : ^.*[@%!/|] | |
304 | ||
305 | # The second rule applies to all other domains, and is less strict. This | |
306 | # allows your own users to send outgoing messages to sites that use slashes | |
307 | # and vertical bars in their local parts. It blocks local parts that begin | |
308 | # with a dot, slash, or vertical bar, but allows these characters within the | |
309 | # local part. However, the sequence /../ is barred. The use of @ % and ! is | |
310 | # blocked, as before. The motivation here is to prevent your users (or | |
311 | # your users' viruses) from mounting certain kinds of attack on remote sites. | |
312 | ||
a59efb33 | 313 | |
26d60792 ŁJM |
314 | deny message = Restricted characters in address |
315 | domains = !+local_domains | |
316 | local_parts = ^[./|] : ^.*[@%!] : ^.*/\\.\\./ | |
317 | ############################################################################# | |
a59efb33 AM |
318 | |
319 | # Accept mail to postmaster in any local domain, regardless of the source, | |
320 | # and without verifying the sender. | |
321 | ||
322 | accept local_parts = postmaster | |
323 | domains = +local_domains | |
324 | ||
325 | # Deny unless the sender address can be verified. | |
326 | ||
327 | require verify = sender | |
328 | ||
329 | ############################################################################# | |
330 | # There are no checks on DNS "black" lists because the domains that contain | |
331 | # these lists are changing all the time. However, here are two examples of | |
332 | # how you could get Exim to perform a DNS black list lookup at this point. | |
333 | # The first one denies, while the second just warns. | |
334 | # | |
335 | # deny message = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text | |
336 | # dnslists = black.list.example | |
337 | # | |
338 | # warn message = X-Warning: $sender_host_address is in a black list at $dnslist_domain | |
339 | # log_message = found in $dnslist_domain | |
340 | # dnslists = black.list.example | |
341 | ############################################################################# | |
342 | ||
343 | # Accept if the address is in a local domain, but only if the recipient can | |
344 | # be verified. Otherwise deny. The "endpass" line is the border between | |
345 | # passing on to the next ACL statement (if tests above it fail) or denying | |
346 | # access (if tests below it fail). | |
347 | ||
348 | accept domains = +local_domains | |
349 | endpass | |
a59efb33 AM |
350 | verify = recipient |
351 | ||
352 | # Accept if the address is in a domain for which we are relaying, but again, | |
353 | # only if the recipient can be verified. | |
354 | ||
355 | accept domains = +relay_to_domains | |
356 | endpass | |
a59efb33 | 357 | verify = recipient |
a59efb33 AM |
358 | # If control reaches this point, the domain is neither in +local_domains |
359 | # nor in +relay_to_domains. | |
360 | ||
361 | # Accept if the message comes from one of the hosts for which we are an | |
362 | # outgoing relay. Recipient verification is omitted here, because in many | |
363 | # cases the clients are dumb MUAs that don't cope well with SMTP error | |
364 | # responses. If you are actually relaying out from MTAs, you should probably | |
365 | # add recipient verification here. | |
366 | ||
367 | accept hosts = +relay_from_hosts | |
368 | ||
369 | # Accept if the message arrived over an authenticated connection, from | |
370 | # any host. Again, these messages are usually from MUAs, so recipient | |
371 | # verification is omitted. | |
372 | ||
373 | accept authenticated = * | |
374 | ||
375 | # Reaching the end of the ACL causes a "deny", but we might as well give | |
376 | # an explicit message. | |
377 | ||
378 | deny message = relay not permitted | |
379 | ||
26d60792 ŁJM |
380 | # These access control lists are used for content scanning with the exiscan-acl |
381 | # patch. You must also uncomment the entries for acl_smtp_data and acl_smtp_mime | |
382 | # (scroll up), otherwise the ACLs will not be used. IMPORTANT: the default entries here | |
383 | # should be treated as EXAMPLES. You MUST read the file doc/exiscan-acl-spec.txt | |
384 | # to fully understand what you are doing ... | |
385 | ||
386 | acl_check_mime: | |
387 | ||
388 | # Decode MIME parts to disk. This will support virus scanners later. | |
389 | warn decode = default | |
390 | ||
391 | # File extension filtering. | |
392 | deny message = Blacklisted file extension detected | |
393 | condition = ${if match \ | |
394 | {${lc:$mime_filename}} \ | |
395 | {\N(\.exe|\.pif|\.bat|\.scr|\.lnk|\.com)$\N} \ | |
396 | {1}{0}} | |
397 | ||
398 | # Reject messages that carry chinese character sets. | |
399 | # WARNING: This is an EXAMPLE. | |
400 | deny message = Sorry, noone speaks chinese here | |
401 | condition = ${if eq{$mime_charset}{gb2312}{1}{0}} | |
402 | ||
403 | accept | |
404 | ||
405 | acl_check_content: | |
406 | ||
407 | # Reject virus infested messages. | |
408 | deny message = This message contains malware ($malware_name) | |
409 | malware = * | |
410 | ||
411 | # Always add X-Spam-Score and X-Spam-Report headers, using SA system-wide settings | |
412 | # (user "nobody"), no matter if over threshold or not. | |
413 | warn message = X-Spam-Score: $spam_score ($spam_bar) | |
414 | spam = nobody:true | |
415 | warn message = X-Spam-Report: $spam_report | |
416 | spam = nobody:true | |
417 | ||
418 | # Add X-Spam-Flag if spam is over system-wide threshold | |
419 | warn message = X-Spam-Flag: YES | |
420 | spam = nobody | |
421 | ||
422 | # Reject spam messages with score over 10, using an extra condition. | |
423 | deny message = This message scored $spam_score points. Congratulations! | |
424 | spam = nobody:true | |
425 | condition = ${if >{$spam_score_int}{100}{1}{0}} | |
426 | ||
427 | # finally accept all the rest | |
428 | accept | |
a59efb33 AM |
429 | |
430 | ||
431 | ###################################################################### | |
432 | # ROUTERS CONFIGURATION # | |
433 | # Specifies how addresses are handled # | |
434 | ###################################################################### | |
435 | # THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! # | |
436 | # An address is passed to each router in turn until it is accepted. # | |
437 | ###################################################################### | |
438 | ||
439 | begin routers | |
440 | ||
441 | # This router routes to remote hosts over SMTP by explicit IP address, | |
442 | # when an email address is given in "domain literal" form, for example, | |
443 | # <user@[192.168.35.64]>. The RFCs require this facility. However, it is | |
444 | # little-known these days, and has been exploited by evil people seeking | |
445 | # to abuse SMTP relays. Consequently it is commented out in the default | |
446 | # configuration. If you uncomment this router, you also need to uncomment | |
447 | # allow_domain_literals above, so that Exim can recognize the syntax of | |
448 | # domain literal addresses. | |
449 | ||
450 | # domain_literal: | |
451 | # driver = ipliteral | |
26d60792 | 452 | # domains = ! +local_domains |
a59efb33 AM |
453 | # transport = remote_smtp |
454 | ||
455 | ||
456 | # This router routes addresses that are not in local domains by doing a DNS | |
26d60792 ŁJM |
457 | # lookup on the domain name. Any domain that resolves to 0.0.0.0 or to a |
458 | # loopback interface address (127.0.0.0/8) is treated as if it had no DNS | |
459 | # entry. Note that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated | |
460 | # as the local host inside the network stack. It is not 0.0.0.0/0, the default | |
461 | # route. If the DNS lookup fails, no further routers are tried because of | |
462 | # the no_more setting, and consequently the address is unrouteable. | |
a59efb33 AM |
463 | |
464 | dnslookup: | |
465 | driver = dnslookup | |
466 | domains = ! +local_domains | |
467 | transport = remote_smtp | |
26d60792 | 468 | ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 |
a59efb33 AM |
469 | no_more |
470 | ||
471 | ||
472 | # The remaining routers handle addresses in the local domain(s). | |
473 | ||
474 | ||
26d60792 ŁJM |
475 | # This router handles aliasing using a linearly searched alias file with the |
476 | # name /etc/mail/aliases. When this configuration is installed automatically, | |
477 | # the name gets inserted into this file from whatever is set in Exim's | |
478 | # build-time configuration. The default path is the traditional /etc/aliases. | |
479 | # If you install this configuration by hand, you need to specify the correct | |
480 | # path in the "data" setting below. | |
a59efb33 | 481 | # |
26d60792 | 482 | ##### NB You must ensure that the alias file exists. It used to be the case |
a59efb33 AM |
483 | ##### NB that every Unix had that file, because it was the Sendmail default. |
484 | ##### NB These days, there are systems that don't have it. Your aliases | |
485 | ##### NB file should at least contain an alias for "postmaster". | |
486 | # | |
487 | # If any of your aliases expand to pipes or files, you will need to set | |
488 | # up a user and a group for these deliveries to run under. You can do | |
489 | # this by uncommenting the "user" option below (changing the user name | |
490 | # as appropriate) and adding a "group" option if necessary. Alternatively, you | |
491 | # can specify "user" on the transports that are used. Note that the transports | |
492 | # listed below are the same as are used for .forward files; you might want | |
493 | # to set up different ones for pipe and file deliveries from aliases. | |
494 | ||
495 | system_aliases: | |
496 | driver = redirect | |
497 | allow_fail | |
498 | allow_defer | |
0e9140df | 499 | data = ${lookup{$local_part}lsearch{/etc/mail/aliases}} |
a59efb33 AM |
500 | # user = exim |
501 | file_transport = address_file | |
502 | pipe_transport = address_pipe | |
503 | ||
504 | ||
505 | # This router handles forwarding using traditional .forward files in users' | |
506 | # home directories. If you want it also to allow mail filtering when a forward | |
2d7a5845 ŁJM |
507 | # file starts with the string "# Exim filter" or "# Sieve filter", uncomment |
508 | # the "allow_filter" option. | |
509 | ||
510 | # If you want this router to treat local parts with suffixes introduced by "-" | |
511 | # or "+" characters as if the suffixes did not exist, uncomment the two local_ | |
512 | # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated | |
513 | # in the same way as xxxx@your.domain by this router. You probably want to make | |
514 | # the same change to the localuser router. | |
a59efb33 AM |
515 | |
516 | # The no_verify setting means that this router is skipped when Exim is | |
517 | # verifying addresses. Similarly, no_expn means that this router is skipped if | |
518 | # Exim is processing an EXPN command. | |
519 | ||
520 | # The check_ancestor option means that if the forward file generates an | |
521 | # address that is an ancestor of the current one, the current one gets | |
522 | # passed on instead. This covers the case where A is aliased to B and B | |
523 | # has a .forward file pointing to A. | |
524 | ||
525 | # The three transports specified at the end are those that are used when | |
526 | # forwarding generates a direct delivery to a file, or to a pipe, or sets | |
527 | # up an auto-reply, respectively. | |
528 | ||
529 | userforward: | |
530 | driver = redirect | |
531 | check_local_user | |
2d7a5845 ŁJM |
532 | # local_part_suffix = +* : -* |
533 | # local_part_suffix_optional | |
a59efb33 | 534 | file = $home/.forward |
2d7a5845 | 535 | # allow_filter |
a59efb33 AM |
536 | no_verify |
537 | no_expn | |
538 | check_ancestor | |
a59efb33 AM |
539 | file_transport = address_file |
540 | pipe_transport = address_pipe | |
541 | reply_transport = address_reply | |
542 | ||
3d67b043 | 543 | # Procmail. Uncomment following if you want procmail delivery. |
544 | ||
545 | #procmail: | |
546 | # driver = accept | |
547 | # check_local_user | |
548 | # local_part_suffix = DSUFFIX* | |
549 | # local_part_suffix_optional | |
550 | # require_files = "${local_part}:+${home}/.procmailrc:\ | |
551 | # +/usr/bin/procmail:!${home}/.forward" | |
552 | # transport = procmail_pipe | |
a59efb33 | 553 | |
26d60792 ŁJM |
554 | # This router matches local user mailboxes. If the router fails, the error |
555 | # message is "Unknown user". | |
a59efb33 | 556 | |
2d7a5845 ŁJM |
557 | # If you want this router to treat local parts with suffixes introduced by "-" |
558 | # or "+" characters as if the suffixes did not exist, uncomment the two local_ | |
559 | # part_suffix options. Then, for example, xxxx-foo@your.domain will be treated | |
560 | # in the same way as xxxx@your.domain by this router. | |
561 | ||
a59efb33 AM |
562 | localuser: |
563 | driver = accept | |
564 | check_local_user | |
2d7a5845 ŁJM |
565 | # local_part_suffix = +* : -* |
566 | # local_part_suffix_optional | |
a59efb33 | 567 | transport = local_delivery |
26d60792 ŁJM |
568 | cannot_route_message = Unknown user |
569 | ||
a59efb33 AM |
570 | |
571 | ###################################################################### | |
572 | # TRANSPORTS CONFIGURATION # | |
573 | ###################################################################### | |
574 | # ORDER DOES NOT MATTER # | |
575 | # Only one appropriate transport is called for each delivery. # | |
576 | ###################################################################### | |
577 | ||
578 | # A transport is used only when referenced from a router that successfully | |
579 | # handles an address. | |
580 | ||
581 | begin transports | |
582 | ||
583 | ||
584 | # This transport is used for delivering messages over SMTP connections. | |
585 | ||
586 | remote_smtp: | |
587 | driver = smtp | |
588 | ||
589 | ||
590 | # This transport is used for local delivery to user mailboxes in traditional | |
591 | # BSD mailbox format. By default it will be run under the uid and gid of the | |
592 | # local user, and requires the sticky bit to be set on the /var/mail directory. | |
593 | # Some systems use the alternative approach of running mail deliveries under a | |
594 | # particular group instead of using the sticky bit. The commented options below | |
595 | # show how this can be done. | |
596 | ||
597 | local_delivery: | |
598 | driver = appendfile | |
599 | file = /var/mail/$local_part | |
600 | delivery_date_add | |
601 | envelope_to_add | |
602 | return_path_add | |
29a901ea | 603 | group = mail |
a59efb33 AM |
604 | # mode = 0660 |
605 | ||
3d67b043 | 606 | # Procmail transport. Uncomment following if you want procmail delivery |
607 | ||
608 | #procmail_pipe: | |
609 | # driver = pipe | |
610 | # command = "procmail -f-" | |
611 | # delivery_date_add | |
612 | # envelope_to_add | |
613 | # path = "/usr/local/bin:/usr/bin:/bin" | |
614 | # return_path_add | |
615 | # user = ${local_part} | |
616 | # temp_errors= 75 : 75 : 256 | |
617 | # log_defer_output | |
618 | # log_fail_output | |
619 | ||
a59efb33 AM |
620 | |
621 | # This transport is used for handling pipe deliveries generated by alias or | |
622 | # .forward files. If the pipe generates any standard output, it is returned | |
623 | # to the sender of the message as a delivery error. Set return_fail_output | |
624 | # instead of return_output if you want this to happen only when the pipe fails | |
625 | # to complete normally. You can set different transports for aliases and | |
626 | # forwards if you want to - see the references to address_pipe in the routers | |
627 | # section above. | |
628 | ||
629 | address_pipe: | |
630 | driver = pipe | |
631 | return_output | |
632 | ||
633 | ||
634 | # This transport is used for handling deliveries directly to files that are | |
635 | # generated by aliasing or forwarding. | |
636 | ||
637 | address_file: | |
638 | driver = appendfile | |
639 | delivery_date_add | |
640 | envelope_to_add | |
641 | return_path_add | |
642 | ||
643 | ||
644 | # This transport is used for handling autoreplies generated by the filtering | |
645 | # option of the userforward router. | |
646 | ||
647 | address_reply: | |
648 | driver = autoreply | |
649 | ||
650 | ||
651 | ||
652 | ###################################################################### | |
653 | # RETRY CONFIGURATION # | |
654 | ###################################################################### | |
655 | ||
656 | begin retry | |
657 | ||
658 | # This single retry rule applies to all domains and all errors. It specifies | |
659 | # retries every 15 minutes for 2 hours, then increasing retry intervals, | |
660 | # starting at 1 hour and increasing each time by a factor of 1.5, up to 16 | |
661 | # hours, then retries every 6 hours until 4 days have passed since the first | |
662 | # failed delivery. | |
663 | ||
664 | # Domain Error Retries | |
665 | # ------ ----- ------- | |
666 | ||
667 | * * F,2h,15m; G,16h,1h,1.5; F,4d,6h | |
668 | ||
669 | ||
670 | ||
671 | ###################################################################### | |
672 | # REWRITE CONFIGURATION # | |
673 | ###################################################################### | |
674 | ||
675 | # There are no rewriting specifications in this default configuration file. | |
676 | ||
677 | begin rewrite | |
678 | ||
679 | ||
680 | ||
681 | ###################################################################### | |
682 | # AUTHENTICATION CONFIGURATION # | |
683 | ###################################################################### | |
684 | ||
685 | # There are no authenticator specifications in this default configuration file. | |
686 | ||
687 | begin authenticators | |
688 | ||
42952ff9 ŁJM |
689 | # Uncomment lines below to enable SMTP AUTH support. Be aware that this |
690 | # requires cyrus-sasl-saslauthd package to be installed. | |
691 | ||
692 | # plain: | |
693 | # driver = plaintext | |
694 | # public_name = PLAIN | |
e794809d | 695 | # server_prompts = : |
1c679d11 | 696 | # server_condition = ${if saslauthd{{$2}{$3}{smtp}}{1}{0}} |
42952ff9 ŁJM |
697 | # server_set_id = $2 |
698 | # | |
699 | # login: | |
700 | # driver = plaintext | |
701 | # public_name = LOGIN | |
702 | # server_prompts = "Username:: : Password::" | |
703 | # server_condition = ${if saslauthd{{$1}{$2}{smtp}}{1}{0}} | |
704 | # server_set_id = $1 | |
a59efb33 AM |
705 | |
706 | # End of Exim configuration file |