[Vmail-discuss] Exim 4 anyone???

Jeremy Utley jutley3@xxxxxxxxxxxxx
Tue, 2 Jul 2002 02:17:01 -0700


This is a multi-part message in MIME format.

------=_NextPart_000_0033_01C2216E.8D066180
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Well, Exim 4 has been out a while, and I'd been wanting to play with it,
but it wouldn't work with the vmail setup.  So, I decided to sit down
tonite, and do some hacking away, and see if I could make it work.  The
fruit's of my labor are attached.  The only vmail function which is
missing currently is domain aliases, and I'm sure there's some extra ACL
checking that could be done, and a little hacking to make the SQL
queries a little cleaner, but it does seem to work for everything else.

If any of you have some experience with Exim 4, I'd appreciate any
feedback you could give me on ways this configuration could be made
better.  And for those of you who've been wanting to use Exim 4, but had
not gone to the trouble to convert vmail to it, please feel free to give
this script a try.  Just don't hold me responsible if something doesn't
work!

Jeremy Utley
www.linux-phreak.net
www.jutley.org
www.thedailyspam.org


------=_NextPart_000_0033_01C2216E.8D066180
Content-Type: application/octet-stream;
	name="exim.conf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="exim.conf"

######################################################################=0A=
#                  Runtime configuration file for Exim               #=0A=
######################################################################=0A=
=0A=
hide mysql_servers =3D localhost/vmail/vmail/michelle1=0A=
=0A=
# This is a default configuration file which will operate correctly in=0A=
# uncomplicated installations. Please see the manual for a complete list=0A=
# of all the runtime configuration options that can be included in a=0A=
# configuration file. There are many more than are mentioned here. The=0A=
# manual is in the file doc/spec.txt in the Exim distribution as a plain=0A=
# ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are =
available=0A=
# from the Exim ftp sites. The manual is also online at the Exim web =
sites.=0A=
=0A=
=0A=
# This file is divided into several parts, all but the first of which are=0A=
# headed by a line starting with the word "begin". Only those parts that=0A=
# are required need to be present. Blank lines, and lines starting with #=0A=
# are ignored.=0A=
=0A=
=0A=
########### IMPORTANT ########## IMPORTANT ########### IMPORTANT =
###########=0A=
#                                                                        =
  #=0A=
# Whenever you change Exim's configuration file, you *must* remember to  =
  #=0A=
# HUP the Exim daemon, because it will not pick up the new configuration =
  #=0A=
# until you do. However, any other Exim processes that are started, for  =
  #=0A=
# example, a process started by an MUA in order to send a message, will  =
  #=0A=
# see the new configuration as soon as it is in place.                   =
  #=0A=
#                                                                        =
  #=0A=
# You do not need to HUP the daemon for changes in auxiliary files that  =
  #=0A=
# are referenced from this file. They are read every time they are used. =
  #=0A=
#                                                                        =
  #=0A=
# It is usually a good idea to test a new configuration for syntactic    =
  #=0A=
# correctness before installing it (for example, by running the command  =
  #=0A=
# "exim -C /config/file.new -bV").                                       =
  #=0A=
#                                                                        =
  #=0A=
########### IMPORTANT ########## IMPORTANT ########### IMPORTANT =
###########=0A=
=0A=
=0A=
=0A=
######################################################################=0A=
#                    MAIN CONFIGURATION SETTINGS                     #=0A=
######################################################################=0A=
=0A=
# Specify your host's canonical name here. This should normally be the =
fully=0A=
# qualified "official" name of your host. If this option is not set, the=0A=
# uname() function is called to obtain the name. In many cases this does=0A=
# the right thing and you need not set anything explicitly.=0A=
=0A=
primary_hostname =3D ducati.kk7ic.org=0A=
=0A=
=0A=
# The next three settings create two lists of domains and one list of =
hosts.=0A=
# These lists are referred to later in this configuration using the =
syntax=0A=
# +local_domains, +relay_to_domains, and +relay_from_hosts, =
respectively. They=0A=
# are all colon-separated lists:=0A=
=0A=
domainlist local_domains =3D ${lookup mysql{select domain_name from =
domain \=0A=
                            where '1'}}=0A=
domainlist relay_to_domains =3D=0A=
hostlist   relay_from_hosts =3D 127.0.0.1=0A=
=0A=
# Most straightforward access control requirements can be obtained by=0A=
# appropriate settings of the above options. In more complicated =
situations, you=0A=
# may need to modify the Access Control List (ACL) which appears later =
in this=0A=
# file.=0A=
=0A=
# The first setting specifies your local domains, for example:=0A=
#=0A=
#   domainlist local_domains =3D my.first.domain : my.second.domain=0A=
#=0A=
# You can use "@" to mean "the name of the local host", as in the default=0A=
# setting above. This is the name that is specified by primary_hostname,=0A=
# as specified above (or defaulted). If you do not want to do any local=0A=
# deliveries, remove the "@" from the setting above. If you want to =
accept mail=0A=
# addressed to your host's literal IP address, for example, mail =
addressed to=0A=
# "user@[192.168.23.44]", you can add "@[]" as an item in the local =
domains=0A=
# list. You also need to uncomment "allow_domain_literals" below. This =
is not=0A=
# recommended for today's Internet.=0A=
=0A=
# The second setting specifies domains for which your host is an =
incoming relay.=0A=
# If you are not doing any relaying, you should leave the list empty. =
However,=0A=
# if your host is an MX backup or gateway of some kind for some domains, =
you=0A=
# must set relay_to_domains to match those domains. For example:=0A=
#=0A=
# domainlist relay_to_domains =3D *.myco.com : my.friend.org=0A=
#=0A=
# This will allow any host to relay through your host to those domains.=0A=
# See the section of the manual entitled "Control of relaying" for more=0A=
# information.=0A=
=0A=
# The third setting specifies hosts that can use your host as an =
outgoing relay=0A=
# to any other host on the Internet. Such a setting commonly refers to a=0A=
# complete local network as well as the localhost. For example:=0A=
#=0A=
# hostlist relay_from_hosts =3D 127.0.0.1 : 192.168.0.0/16=0A=
#=0A=
# The "/16" is a bit mask (CIDR notation), not a number of hosts. Note =
that you=0A=
# have to include 127.0.0.1 if you want to allow processes on your host =
to send=0A=
# SMTP mail by using the loopback address. A number of MUAs use this =
method of=0A=
# sending mail.=0A=
=0A=
=0A=
# All three of these lists may contain many different kinds of item, =
including=0A=
# wildcarded names, regular expressions, and file lookups. See the =
reference=0A=
# manual for details. The lists above are used in the access control =
list for=0A=
# incoming messages. The name of this ACL is defined here:=0A=
=0A=
acl_smtp_rcpt =3D acl_check_rcpt=0A=
=0A=
# You should not change that setting until you understand how ACLs work.=0A=
=0A=
=0A=
# Specify the domain you want to be added to all unqualified addresses=0A=
# here. An unqualified address is one that does not contain an "@" =
character=0A=
# followed by a domain. For example, "caesar@rome.example" is a fully =
qualified=0A=
# address, but the string "caesar" (i.e. just a login name) is an =
unqualified=0A=
# email address. Unqualified addresses are accepted only from local =
callers by=0A=
# default. See the recipient_unqualified_hosts option if you want to =
permit=0A=
# unqualified addresses from remote sources. If this option is not set, =
the=0A=
# primary_hostname value is used for qualification.=0A=
=0A=
# qualify_domain =3D=0A=
=0A=
=0A=
# If you want unqualified recipient addresses to be qualified with a =
different=0A=
# domain to unqualified sender addresses, specify the recipient domain =
here.=0A=
# If this option is not set, the qualify_domain value is used.=0A=
=0A=
# qualify_recipient =3D=0A=
=0A=
=0A=
# The following line must be uncommented if you want Exim to recognize=0A=
# addresses of the form "user@[10.11.12.13]" that is, with a "domain =
literal"=0A=
# (an IP address) instead of a named domain. The RFCs still require this =
form,=0A=
# but it makes little sense to permit mail to be sent to specific hosts =
by=0A=
# their IP address in the modern Internet. This ancient format has been =
used=0A=
# by those seeking to abuse hosts by using them for unwanted relaying. =
If you=0A=
# really do want to support domain literals, uncomment the following =
line, and=0A=
# see also the "domain_literal" router below.=0A=
=0A=
# allow_domain_literals=0A=
=0A=
=0A=
# No deliveries will ever be run under the uids of these users (a colon-=0A=
# separated list). An attempt to do so causes a panic error to be =
logged, and=0A=
# the delivery to be deferred. This is a paranoic safety catch. Note =
that the=0A=
# default setting means you cannot deliver mail addressed to root as if =
it=0A=
# were a normal user. This isn't usually a problem, as most sites have =
an alias=0A=
# for root that redirects such mail to a human administrator.=0A=
=0A=
never_users =3D root=0A=
=0A=
=0A=
# The setting below causes Exim to do a reverse DNS lookup on all =
incoming=0A=
# IP calls, in order to get the true host name. If you feel this is too=0A=
# expensive, you can specify the networks for which a lookup is done, or=0A=
# remove the setting entirely.=0A=
=0A=
host_lookup =3D *=0A=
=0A=
=0A=
# The settings below, which are actually the same as the defaults in the=0A=
# code, cause Exim to make RFC 1413 (ident) callbacks for all incoming =
SMTP=0A=
# calls. You can limit the hosts to which these calls are made, and/or =
change=0A=
# the timeout that is used. If you set the timeout to zero, all RFC 1413 =
calls=0A=
# are disabled. RFC 1413 calls are cheap and can provide useful =
information=0A=
# for tracing problem messages, but some hosts and firewalls have =
problems=0A=
# with them. This can result in a timeout instead of an immediate refused=0A=
# connection, leading to delays on starting up an SMTP session.=0A=
=0A=
rfc1413_hosts =3D *=0A=
rfc1413_query_timeout =3D 30s=0A=
=0A=
=0A=
# By default, Exim expects all envelope addresses to be fully qualified, =
that=0A=
# is, they must contain both a local part and a domain. If you want to =
accept=0A=
# unqualified addresses (just a local part) from certain hosts, you can =
specify=0A=
# these hosts by setting one or both of=0A=
#=0A=
# sender_unqualified_hosts =3D=0A=
# recipient_unqualified_hosts =3D=0A=
#=0A=
# to control sender and recipient addresses, respectively. When this is =
done,=0A=
# unqualified addresses are qualified using the settings of =
qualify_domain=0A=
# and/or qualify_recipient (see above).=0A=
=0A=
=0A=
# If you want Exim to support the "percent hack" for certain domains,=0A=
# uncomment the following line and provide a list of domains. The =
"percent=0A=
# hack" is the feature by which mail addressed to x%y@z (where z is one =
of=0A=
# the domains listed) is locally rerouted to x@y and sent on. If z is =
not one=0A=
# of the "percent hack" domains, x%y is treated as an ordinary local =
part. This=0A=
# hack is rarely needed nowadays; you should not enable it unless you =
are sure=0A=
# that you really need it.=0A=
#=0A=
# percent_hack_domains =3D=0A=
#=0A=
# As well as setting this option you will also need to remove the test=0A=
# for local parts containing % in the ACL definition below.=0A=
=0A=
=0A=
# When Exim can neither deliver a message nor return it to sender, it =
"freezes"=0A=
# the delivery error message (aka "bounce message"). There are also other=0A=
# circumstances in which messages get frozen. They will stay on the =
queue for=0A=
# ever unless one of the following options is set.=0A=
=0A=
# This option unfreezes frozen bounce messages after two days, tries=0A=
# once more to deliver them, and ignores any delivery failures.=0A=
=0A=
ignore_bounce_errors_after =3D 2d=0A=
=0A=
# This option cancels (removes) frozen messages that are older than a =
week.=0A=
=0A=
timeout_frozen_after =3D 7d=0A=
=0A=
=0A=
=0A=
######################################################################=0A=
#                       ACL CONFIGURATION                            #=0A=
#         Specifies access control lists for incoming SMTP mail      #=0A=
######################################################################=0A=
=0A=
begin acl=0A=
=0A=
# This access control list is used for every RCPT command in an incoming=0A=
# SMTP message. The tests are run in order until the address is either=0A=
# accepted or denied.=0A=
=0A=
acl_check_rcpt:=0A=
=0A=
  # Accept if the source is local SMTP (i.e. not over TCP/IP). We do =
this by=0A=
  # testing for an empty sending host field.=0A=
=0A=
  accept  hosts =3D :=0A=
=0A=
  # Deny if the local part contains @ or % or / or | or !. These are =
rarely=0A=
  # found in genuine local parts, but are often tried by people looking =
to=0A=
  # circumvent relaying restrictions.=0A=
=0A=
  deny    local_parts   =3D ^.*[@%!/|]=0A=
=0A=
  # Accept mail to postmaster in any local domain, regardless of the =
source,=0A=
  # and without verifying the sender.=0A=
=0A=
  accept  local_parts   =3D postmaster=0A=
          domains       =3D +local_domains=0A=
=0A=
  # Deny unless the sender address can be verified.=0A=
=0A=
  require verify        =3D sender=0A=
=0A=
  =
#########################################################################=
####=0A=
  # There are no checks on DNS "black" lists because the domains that =
contain=0A=
  # these lists are changing all the time. However, here are two =
examples of=0A=
  # how you could get Exim to perform a DNS black list lookup at this =
point.=0A=
  # The first one denies, while the second just warns.=0A=
  #=0A=
  # deny    message       =3D rejected because $sender_host_address is =
in a black list at $dnslist_domain\n$dnslist_text=0A=
  #         dnslists      =3D black.list.example=0A=
  #=0A=
  # warn    message       =3D X-Warning: $sender_host_address is in a =
black list at $dnslist_domain=0A=
  #         log_message   =3D found in $dnslist_domain=0A=
  #         dnslists      =3D black.list.example=0A=
  =
#########################################################################=
####=0A=
=0A=
  # Accept if the address is in a local domain, but only if the =
recipient can=0A=
  # be verified. Otherwise deny. The "endpass" line is the border between=0A=
  # passing on to the next ACL statement (if tests above it fail) or =
denying=0A=
  # access (if tests below it fail).=0A=
=0A=
  accept  domains       =3D +local_domains=0A=
  =0A=
  # Accept if the address is in a domain for which we are relaying, but =
again,=0A=
  # only if the recipient can be verified.=0A=
=0A=
  accept  domains       =3D +relay_to_domains=0A=
  =0A=
  # If control reaches this point, the domain is neither in =
+local_domains=0A=
  # nor in +relay_to_domains.=0A=
=0A=
  # Accept if the message comes from one of the hosts for which we are an=0A=
  # outgoing relay. Recipient verification is omitted here, because in =
many=0A=
  # cases the clients are dumb MUAs that don't cope well with SMTP error=0A=
  # responses. If you are actually relaying out from MTAs, you should =
probably=0A=
  # add recipient verification here.=0A=
=0A=
  accept  hosts         =3D +relay_from_hosts=0A=
=0A=
  # Accept if the message arrived over an authenticated connection, from=0A=
  # any host. Again, these messages are usually from MUAs, so recipient=0A=
  # verification is omitted.=0A=
=0A=
  accept  authenticated =3D *=0A=
=0A=
  # Reaching the end of the ACL causes a "deny", but we might as well =
give=0A=
  # an explicit message.=0A=
=0A=
  deny    message       =3D relay not permitted=0A=
=0A=
=0A=
=0A=
######################################################################=0A=
#                      ROUTERS CONFIGURATION                         #=0A=
#               Specifies how addresses are handled                  #=0A=
######################################################################=0A=
#     THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT!       #=0A=
# An address is passed to each router in turn until it is accepted.  #=0A=
######################################################################=0A=
=0A=
begin routers=0A=
=0A=
# This router routes to remote hosts over SMTP by explicit IP address,=0A=
# when an email address is given in "domain literal" form, for example,=0A=
# <user@[192.168.35.64]>. The RFCs require this facility. However, it is=0A=
# little-known these days, and has been exploited by evil people seeking=0A=
# to abuse SMTP relays. Consequently it is commented out in the default=0A=
# configuration. If you uncomment this router, you also need to uncomment=0A=
# allow_domain_literals above, so that Exim can recognize the syntax of=0A=
# domain literal addresses.=0A=
=0A=
# domain_literal:=0A=
#   driver =3D ipliteral=0A=
#   domains =3D ! +local_domains=0A=
#   transport =3D remote_smtp=0A=
=0A=
=0A=
# This router routes addresses that are not in local domains by doing a =
DNS=0A=
# lookup on the domain name. Any domain that resolves to 0.0.0.0 or to a=0A=
# loopback interface address (127.0.0.0/8) is treated as if it had no DNS=0A=
# entry. Note that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly =
treated=0A=
# as the local host inside the network stack. It is not 0.0.0.0/0, the =
default=0A=
# route. If the DNS lookup fails, no further routers are tried because of=0A=
# the no_more setting, and consequently the address is unrouteable.=0A=
=0A=
dnslookup:=0A=
  driver =3D dnslookup=0A=
  domains =3D ! +local_domains=0A=
  transport =3D remote_smtp=0A=
  ignore_target_hosts =3D 0.0.0.0 : 127.0.0.0/8=0A=
  no_more=0A=
=0A=
=0A=
# The remaining routers handle addresses in the local domain(s).=0A=
=0A=
# The virtualemail database allows local parts to correspond to remote=0A=
# addresses (forwarding), to be aliases for local maildrops, or to be =
local=0A=
# maildrops. These are expressed in tables forwarder and popbox=0A=
# respectively.=0A=
=0A=
# Handle forwarders and aliases (same database table)=0A=
=0A=
virtual_forward:=0A=
  driver =3D redirect=0A=
  data =3D ${lookup mysql{select remote_name from forwarder left join =
domain_alias on domain_alias.domain_name =3D forwarder.domain_name where =
local_part =3D '$local_part' and (forwarder.domain_name =3D '$domain' or =
alias =3D '$domain')}}=0A=
  forbid_file =3D true=0A=
  forbid_pipe =3D true=0A=
=0A=
# Handle delivery; see sample config C009 for what this is based on; it =
only=0A=
# handles things for the virtual domains, which are listed in the =
database.=0A=
=0A=
virtual_localuser:=0A=
  driver =3D accept=0A=
  domains =3D ${lookup mysql{select domain_name from domain \=0A=
                            where domain_name =3D '$domain'}}=0A=
  local_parts =3D ${lookup mysql{select local_part from popbox where =
domain_name =3D '$domain'}}=0A=
  transport =3D virtual_localdelivery=0A=
=0A=
# deliver any undelivered virtual email according to the _default_ =
forwarder=0A=
=0A=
virtual_defaultuser:=0A=
  driver =3D redirect=0A=
  data =3D ${lookup mysql{select remote_name from forwarder left join =
domain_alias on domain_alias.domain_name =3D forwarder.domain_name where =
local_part =3D '_default_' and (forwarder.domain_name =3D '$domain' or =
domain_alias.alias =3D '$domain')}}=0A=
  forbid_file =3D true=0A=
  forbid_pipe =3D true=0A=
=0A=
# This router handles aliasing using a traditional /etc/aliases file.=0A=
#=0A=
##### NB  You must ensure that /etc/aliases exists. It used to be the =
case=0A=
##### NB  that every Unix had that file, because it was the Sendmail =
default.=0A=
##### NB  These days, there are systems that don't have it. Your aliases=0A=
##### NB  file should at least contain an alias for "postmaster".=0A=
#=0A=
# If any of your aliases expand to pipes or files, you will need to set=0A=
# up a user and a group for these deliveries to run under. You can do=0A=
# this by uncommenting the "user" option below (changing the user name=0A=
# as appropriate) and adding a "group" option if necessary. =
Alternatively, you=0A=
# can specify "user" on the transports that are used. Note that the =
transports=0A=
# listed below are the same as are used for .forward files; you might =
want=0A=
# to set up different ones for pipe and file deliveries from aliases.=0A=
=0A=
system_aliases:=0A=
  driver =3D redirect=0A=
  allow_fail=0A=
  allow_defer=0A=
  data =3D ${lookup{$local_part}lsearch{/etc/aliases}}=0A=
# user =3D exim=0A=
  file_transport =3D address_file=0A=
  pipe_transport =3D address_pipe=0A=
=0A=
=0A=
# This router handles forwarding using traditional .forward files in =
users'=0A=
# home directories. If you want it also to allow mail filtering when a =
forward=0A=
# file starts with the string "# Exim filter", uncomment the =
"allow_filter"=0A=
# option.=0A=
=0A=
# The no_verify setting means that this router is skipped when Exim is=0A=
# verifying addresses. Similarly, no_expn means that this router is =
skipped if=0A=
# Exim is processing an EXPN command.=0A=
=0A=
# The check_ancestor option means that if the forward file generates an=0A=
# address that is an ancestor of the current one, the current one gets=0A=
# passed on instead. This covers the case where A is aliased to B and B=0A=
# has a .forward file pointing to A.=0A=
=0A=
# The three transports specified at the end are those that are used when=0A=
# forwarding generates a direct delivery to a file, or to a pipe, or sets=0A=
# up an auto-reply, respectively.=0A=
=0A=
userforward:=0A=
  driver =3D redirect=0A=
  check_local_user=0A=
  file =3D $home/.forward=0A=
  no_verify=0A=
  no_expn=0A=
  check_ancestor=0A=
# allow_filter=0A=
  file_transport =3D address_file=0A=
  pipe_transport =3D address_pipe=0A=
  reply_transport =3D address_reply=0A=
=0A=
=0A=
# This router matches local user mailboxes.=0A=
=0A=
localuser:=0A=
  driver =3D accept=0A=
  check_local_user=0A=
  transport =3D local_delivery=0A=
=0A=
=0A=
=0A=
######################################################################=0A=
#                      TRANSPORTS CONFIGURATION                      #=0A=
######################################################################=0A=
#                       ORDER DOES NOT MATTER                        #=0A=
#     Only one appropriate transport is called for each delivery.    #=0A=
######################################################################=0A=
=0A=
# A transport is used only when referenced from a router that =
successfully=0A=
# handles an address.=0A=
=0A=
begin transports=0A=
=0A=
# This transport is to deliver mail going to virtual domains to user=0A=
# mailspools in directories under /var/mail/foo/bar; this is=0A=
# triggered from a director below.=0A=
=0A=
virtual_localdelivery:=0A=
  driver =3D appendfile=0A=
  file =3D ${lookup mysql{select path from domain left join domain_alias =
on domain_alias.domain_name =3D domain.domain_name where =
domain.domain_name =3D '$domain' or domain_alias.alias =3D =
'$domain'}{$value}fail}/${lookup mysql{select mbox_name from popbox left =
join domain_alias on popbox.domain_name =3D domain_alias.domain_name =
where (popbox.domain_name =3D '$domain' or domain_alias.alias =3D =
'$domain') and local_part =3D '$local_part'}{$value}fail}=0A=
  delivery_date_add=0A=
  envelope_to_add=0A=
  return_path_add=0A=
  user =3D ${lookup mysql{select unix_user from domain left join =
domain_alias on domain_alias.domain_name =3D domain.domain_name where =
domain.domain_name =3D '$domain' or domain_alias.alias =3D =
'$domain'}{$value}fail}=0A=
  group =3D exim=0A=
  mode =3D 0660=0A=
=0A=
# This transport is used for delivering messages over SMTP connections.=0A=
=0A=
remote_smtp:=0A=
  driver =3D smtp=0A=
=0A=
=0A=
# This transport is used for local delivery to user mailboxes in =
traditional=0A=
# BSD mailbox format. By default it will be run under the uid and gid of =
the=0A=
# local user, and requires the sticky bit to be set on the /var/mail =
directory.=0A=
# Some systems use the alternative approach of running mail deliveries =
under a=0A=
# particular group instead of using the sticky bit. The commented =
options below=0A=
# show how this can be done.=0A=
=0A=
local_delivery:=0A=
  driver =3D appendfile=0A=
  file =3D /var/mail/$local_part=0A=
  delivery_date_add=0A=
  envelope_to_add=0A=
  return_path_add=0A=
# group =3D mail=0A=
# mode =3D 0660=0A=
=0A=
=0A=
# This transport is used for handling pipe deliveries generated by alias =
or=0A=
# .forward files. If the pipe generates any standard output, it is =
returned=0A=
# to the sender of the message as a delivery error. Set =
return_fail_output=0A=
# instead of return_output if you want this to happen only when the pipe =
fails=0A=
# to complete normally. You can set different transports for aliases and=0A=
# forwards if you want to - see the references to address_pipe in the =
routers=0A=
# section above.=0A=
=0A=
address_pipe:=0A=
  driver =3D pipe=0A=
  return_output=0A=
=0A=
=0A=
# This transport is used for handling deliveries directly to files that =
are=0A=
# generated by aliasing or forwarding.=0A=
=0A=
address_file:=0A=
  driver =3D appendfile=0A=
  delivery_date_add=0A=
  envelope_to_add=0A=
  return_path_add=0A=
=0A=
=0A=
# This transport is used for handling autoreplies generated by the =
filtering=0A=
# option of the userforward router.=0A=
=0A=
address_reply:=0A=
  driver =3D autoreply=0A=
=0A=
=0A=
=0A=
######################################################################=0A=
#                      RETRY CONFIGURATION                           #=0A=
######################################################################=0A=
=0A=
begin retry=0A=
=0A=
# This single retry rule applies to all domains and all errors. It =
specifies=0A=
# retries every 15 minutes for 2 hours, then increasing retry intervals,=0A=
# starting at 1 hour and increasing each time by a factor of 1.5, up to =
16=0A=
# hours, then retries every 6 hours until 4 days have passed since the =
first=0A=
# failed delivery.=0A=
=0A=
# Domain               Error       Retries=0A=
# ------               -----       -------=0A=
=0A=
*                      *           F,2h,15m; G,16h,1h,1.5; F,4d,6h=0A=
=0A=
=0A=
=0A=
######################################################################=0A=
#                      REWRITE CONFIGURATION                         #=0A=
######################################################################=0A=
=0A=
# There are no rewriting specifications in this default configuration =
file.=0A=
=0A=
begin rewrite=0A=
=0A=
=0A=
=0A=
######################################################################=0A=
#                   AUTHENTICATION CONFIGURATION                     #=0A=
######################################################################=0A=
=0A=
# There are no authenticator specifications in this default =
configuration file.=0A=
=0A=
begin authenticators=0A=
=0A=
=0A=
# End of Exim configuration file=0A=

------=_NextPart_000_0033_01C2216E.8D066180--