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