Well, I see some things;
domainlist local_domains = toto.com:localhost
domainlist relay_to_domains = toto.com
A domain should be either local or remote, but clearly not both.
relay_to_domains generally are non locally stored domains (but you can
use any name you wish however). While local_domains are stored on the
same machine (or on a mount, but are handled by the local machine anyway).
Using amavis is generally not a good idea, because you have already
accepted the mail to be able to pass it through amavis. Exim is able to
check out spam and viruses through its ACL. If you use amavis, you may
generate bounces for mails that are spam and/or contains viruses.
What is the machine with IP 192.168.102.12? Is it an internal mail
server? And if yes, what is it running as SMTP?
Sorry if I replied with your config attached, but you forgot to forward
it to the whole list. So it should now be done :)
Jean-Paul BALOCHE wrote:
> Tks for your answer.
>
> here is the conf
>
> You know, i'm a beginner with exim, how can I make the amavis part
> running into an acl ?
>
> TKS
> JPB
>
> 2006/6/27, Renaud Allard <renaud@???>:
>> Excuse me, but didn't you forget to attach the conf?
>>
>> Jean-Paul BALOCHE wrote:
>> > Hi,
>> >
>> > another thing, if I don't put the bounce_return_message = false I'm
>> > not considered anymore as spam by gmail.
>> > But I don't wan't to send a bounce message when the destination user
>> > doesn't exist !
>> >
>> > tks for your help
>> >
>> > JPB
>> >
>> > 2006/6/27, Jean-Paul BALOCHE <jpbalcidian@???>:
>> >> Hi,
>> >>
>> >> thanks for your very fast answer ;-)
>> >>
>> >> You will find attached my configuration file.
>> >> I have a first mail server which is the public one in a first DMZ and
>> >> another private one behind a second firewall.
>> >> The one I'm talking about is the public one.
>> >>
>> >> tks,
>> >> JPB
>> >>
>> >> 2006/6/27, Renaud Allard <renaud@???>:
>> >> > Hello,
>> >> >
>> >> > I think you will need to send us your full configuration because the
>> >> > problem seems deeper than only this ACL. You shouldn't have returned
>> >> > bounces for non existent users in the first place.
>> >> >
>> >> > Also, do you relay mail to another internal server?
>> >> >
>> >> > Jean-Paul BALOCHE wrote:
>> >> > > Hi,
>> >> > >
>> >> > > I contact you to have some help on exim4 regarding bounce
>> messages.
>> >> > >
>> >> > > I wrote in the acl_check_rcpt acl those lines :
>> >> > > accept domains = +local_domains
>> >> > > endpass
>> >> > > message = unknown user / l'utilisateur n'existe
>> pas
>> >> > > verify = recipient
>> >> > >
>> >> > > and then i wrote : bounce_return_message = false
>> >> > > because I don't wan't original messages to be send : before, when
>> >> > > spammer send me spam messages, exim replied with a bounce message
>> >> > > including the spam message, so I was considered like a spammer by
>> >> > > spamcop !
>> >> > >
>> >> > > But When I put those options, gmail see me like a spammer !
>> >> > > I really don't understand.
>> >> > > How can I do, to reply when the user doesn't exist without
>> >> becomming a
>> >> > spammer ?
>> >> > >
>> >> > > thanks for your help ;-)
>> >> > > JPB
>> >> > >
>> >> >
>> >> > --
>> >> >
>> >> > .O.
>> >> > ..O
>> >> > OOO
>> >> >
>> >> > PGP key: http://www.llorien.org/gnupg/key.pub
>> >> >
>> >> > Insanity: doing the same thing over and over again and expecting
>> >> > different results.
>> >> > - Albert Einstein
>> >> >
>> >> >
>> >> >
>> >>
>> >>
>> >
>>
>> --
>>
>> .O.
>> ..O
>> OOO
>>
>> PGP key: http://www.llorien.org/gnupg/key.pub
>>
>> Insanity: doing the same thing over and over again and expecting
>> different results.
>> - Albert Einstein
>>
>>
>>
>
> ------------------------------------------------------------------------
>
> ######################################################################
> # Runtime configuration file for Exim #
> ######################################################################
>
>
> # This is a default configuration file which will operate correctly in
> # uncomplicated installations. Please see the manual for a complete list
> # of all the runtime configuration options that can be included in a
> # configuration file. There are many more than are mentioned here. The
> # manual is in the file doc/spec.txt in the Exim distribution as a plain
> # ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are available
> # from the Exim ftp sites. The manual is also online at the Exim web sites.
>
>
> # This file is divided into several parts, all but the first of which are
> # headed by a line starting with the word "begin". Only those parts that
> # are required need to be present. Blank lines, and lines starting with #
> # are ignored.
>
>
> ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
> # #
> # Whenever you change Exim's configuration file, you *must* remember to #
> # HUP the Exim daemon, because it will not pick up the new configuration #
> # until you do. However, any other Exim processes that are started, for #
> # example, a process started by an MUA in order to send a message, will #
> # see the new configuration as soon as it is in place. #
> # #
> # You do not need to HUP the daemon for changes in auxiliary files that #
> # are referenced from this file. They are read every time they are used. #
> # #
> # It is usually a good idea to test a new configuration for syntactic #
> # correctness before installing it (for example, by running the command #
> # "exim -C /config/file.new -bV"). #
> # #
> ########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
>
>
>
> ######################################################################
> # MAIN CONFIGURATION SETTINGS #
> ######################################################################
>
> local_interfaces = 0.0.0.0.25 : 127.0.0.1.10025
>
> #local_scan_timeout = 3m
> #local_scan_path = /usr/lib/exim4/local_scan/sa-exim.so
> smtp_banner = "Anonymous SMTP server"
>
>
> # Specify your host's canonical name here. This should normally be the fully
> # qualified "official" name of your host. If this option is not set, the
> # uname() function is called to obtain the name. In many cases this does
> # the right thing and you need not set anything explicitly.
>
> # primary_hostname =
>
>
> # The next three settings create two lists of domains and one list of hosts.
> # These lists are referred to later in this configuration using the syntax
> # +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
> # are all colon-separated lists:
>
> domainlist local_domains = toto.com:localhost
> domainlist relay_to_domains = toto.com
> hostlist relay_from_hosts = 127.0.0.1 : 192.168.102.12/32
> # : 192.168.1.0/24
>
> # Most straightforward access control requirements can be obtained by
> # appropriate settings of the above options. In more complicated situations, you
> # may need to modify the Access Control List (ACL) which appears later in this
> # file.
>
> # The first setting specifies your local domains, for example:
> #
> # domainlist local_domains = my.first.domain : my.second.domain
> #
> # You can use "@" to mean "the name of the local host", as in the default
> # setting above. This is the name that is specified by primary_hostname,
> # as specified above (or defaulted). If you do not want to do any local
> # deliveries, remove the "@" from the setting above. If you want to accept mail
> # addressed to your host's literal IP address, for example, mail addressed to
> # "user@???", you can add "@[]" as an item in the local domains
> # list. You also need to uncomment "allow_domain_literals" below. This is not
> # recommended for today's Internet.
>
> # The second setting specifies domains for which your host is an incoming relay.
> # If you are not doing any relaying, you should leave the list empty. However,
> # if your host is an MX backup or gateway of some kind for some domains, you
> # must set relay_to_domains to match those domains. For example:
> #
> # domainlist relay_to_domains = *.myco.com : my.friend.org
> #
> # This will allow any host to relay through your host to those domains.
> # See the section of the manual entitled "Control of relaying" for more
> # information.
>
> # The third setting specifies hosts that can use your host as an outgoing relay
> # to any other host on the Internet. Such a setting commonly refers to a
> # complete local network as well as the localhost. For example:
> #
> # hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16
> #
> # The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
> # have to include 127.0.0.1 if you want to allow processes on your host to send
> # SMTP mail by using the loopback address. A number of MUAs use this method of
> # sending mail.
>
>
> # All three of these lists may contain many different kinds of item, including
> # wildcarded names, regular expressions, and file lookups. See the reference
> # manual for details. The lists above are used in the access control list for
> # incoming messages. The name of this ACL is defined here:
>
> acl_smtp_rcpt = acl_check_rcpt
>
> # You should not change that setting until you understand how ACLs work.
>
> # The following ACL entry is used if you want to do content scanning with the
> # exiscan-acl patch. When you uncomment this line, you must also review the
> # acl_check_content entry in the ACL section further below.
>
> # tocheck pour fonctionner avec spamassassin
> acl_smtp_data = acl_check_content
>
>
> acl_smtp_mail = acl_check_sender
>
>
>
> # This configuration variable defines the virus scanner that is used with
> # the 'malware' ACL condition of the exiscan acl-patch. If you do not use
> # virus scanning, leave it commented. Please read doc/exiscan-acl-readme.txt
> # for a list of supported scanners.
>
> # av_scanner = sophie:/var/run/sophie
>
> # The following setting is only needed if you use the 'spam' ACL condition
> # of the exiscan-acl patch. It specifies on which host and port the SpamAssassin
> # "spamd" daemon is listening. If you do not use this condition, or you use
> # the default of "127.0.0.1 783", you can omit this option.
>
> spamd_address = 127.0.0.1 783
>
> # Specify the domain you want to be added to all unqualified addresses
> # here. An unqualified address is one that does not contain an "@" character
> # followed by a domain. For example, "caesar@???" is a fully qualified
> # address, but the string "caesar" (i.e. just a login name) is an unqualified
> # email address. Unqualified addresses are accepted only from local callers by
> # default. See the recipient_unqualified_hosts option if you want to permit
> # unqualified addresses from remote sources. If this option is not set, the
> # primary_hostname value is used for qualification.
>
> qualify_domain = toto.com
>
> # If you want unqualified recipient addresses to be qualified with a different
> # domain to unqualified sender addresses, specify the recipient domain here.
> # If this option is not set, the qualify_domain value is used.
>
> # qualify_recipient =
>
>
> # The following line must be uncommented if you want Exim to recognize
> # addresses of the form "user@???" that is, with a "domain literal"
> # (an IP address) instead of a named domain. The RFCs still require this form,
> # but it makes little sense to permit mail to be sent to specific hosts by
> # their IP address in the modern Internet. This ancient format has been used
> # by those seeking to abuse hosts by using them for unwanted relaying. If you
> # really do want to support domain literals, uncomment the following line, and
> # see also the "domain_literal" router below.
>
> # allow_domain_literals
>
>
> # No deliveries will ever be run under the uids of these users (a colon-
> # separated list). An attempt to do so causes a panic error to be logged, and
> # the delivery to be deferred. This is a paranoic safety catch. Note that the
> # default setting means you cannot deliver mail addressed to root as if it
> # were a normal user. This isn't usually a problem, as most sites have an alias
> # for root that redirects such mail to a human administrator.
>
> never_users = root
>
>
> # The setting below causes Exim to do a reverse DNS lookup on all incoming
> # IP calls, in order to get the true host name. If you feel this is too
> # expensive, you can specify the networks for which a lookup is done, or
> # remove the setting entirely.
>
> host_lookup = *
>
>
> # The settings below, which are actually the same as the defaults in the
> # code, cause Exim to make RFC 1413 (ident) callbacks for all incoming SMTP
> # calls. You can limit the hosts to which these calls are made, and/or change
> # the timeout that is used. If you set the timeout to zero, all RFC 1413 calls
> # are disabled. RFC 1413 calls are cheap and can provide useful information
> # for tracing problem messages, but some hosts and firewalls have problems
> # with them. This can result in a timeout instead of an immediate refused
> # connection, leading to delays on starting up an SMTP session.
>
> rfc1413_hosts = *
> rfc1413_query_timeout = 0s
>
>
> # By default, Exim expects all envelope addresses to be fully qualified, that
> # is, they must contain both a local part and a domain. If you want to accept
> # unqualified addresses (just a local part) from certain hosts, you can specify
> # these hosts by setting one or both of
> #
> # sender_unqualified_hosts =
> # recipient_unqualified_hosts =
> #
> # to control sender and recipient addresses, respectively. When this is done,
> # unqualified addresses are qualified using the settings of qualify_domain
> # and/or qualify_recipient (see above).
>
>
> # If you want Exim to support the "percent hack" for certain domains,
> # uncomment the following line and provide a list of domains. The "percent
> # hack" is the feature by which mail addressed to x%y@z (where z is one of
> # the domains listed) is locally rerouted to x@y and sent on. If z is not one
> # of the "percent hack" domains, x%y is treated as an ordinary local part. This
> # hack is rarely needed nowadays; you should not enable it unless you are sure
> # that you really need it.
> #
> # percent_hack_domains =
> #
> # As well as setting this option you will also need to remove the test
> # for local parts containing % in the ACL definition below.
>
>
> # When Exim can neither deliver a message nor return it to sender, it "freezes"
> # the delivery error message (aka "bounce message"). There are also other
> # circumstances in which messages get frozen. They will stay on the queue for
> # ever unless one of the following options is set.
>
> # This option unfreezes frozen bounce messages after two days, tries
> # once more to deliver them, and ignores any delivery failures.
>
> ignore_bounce_errors_after = 2d
>
> # This option cancels (removes) frozen messages that are older than a week.
>
> timeout_frozen_after = 5d
> bounce_return_message = false
> errors_reply_to = postmaster@???
>
> ######################################################################
> # ACL CONFIGURATION #
> # Specifies access control lists for incoming SMTP mail #
> ######################################################################
>
> begin acl
>
> # This access control list is used for every RCPT command in an incoming
> # SMTP message. The tests are run in order until the address is either
> # accepted or denied.
>
> acl_check_rcpt:
>
> # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
> # testing for an empty sending host field.
>
> accept hosts = :
>
> # Deny if the local part contains @ or % or / or | or !. These are rarely
> # found in genuine local parts, but are often tried by people looking to
> # circumvent relaying restrictions.
>
> # Also deny if the local part starts with a dot. Empty components aren't
> # strictly legal in RFC 2822, but Exim allows them because this is common.
> # However, actually starting with a dot may cause trouble if the local part
> # is used as a file name (e.g. for a mailing list).
>
> deny local_parts = ^.*[@%!/|] : ^\\.
>
> # to check rbl :
> warn message = X-Warning: $sender_host_address is listed in a black list at $dnslist_domain
> dnslists = blackholes.mail-abuse.org : \
> dialup.mail-abuse.org
> log_message = found in $dnslist_domain
>
>
> # Accept mail to postmaster in any local domain, regardless of the source,
> # and without verifying the sender.
>
> accept local_parts = postmaster
> domains = +local_domains
>
> # Deny unless the sender address can be verified.
>
> # require verify = sender
>
> #############################################################################
> # There are no checks on DNS "black" lists because the domains that contain
> # these lists are changing all the time. However, here are two examples of
> # how you could get Exim to perform a DNS black list lookup at this point.
> # The first one denies, while the second just warns.
> #
> # deny message = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
> # dnslists = black.list.example
> #
> # warn message = X-Warning: $sender_host_address is in a black list at $dnslist_domain
> # log_message = found in $dnslist_domain
> # dnslists = black.list.example
> #############################################################################
>
> # Accept if the address is in a local domain, but only if the recipient can
> # be verified. Otherwise deny. The "endpass" line is the border between
> # passing on to the next ACL statement (if tests above it fail) or denying
> # access (if tests below it fail).
>
> accept domains = +local_domains
> endpass
> message = unknown user / l'utilisateur n'existe pas
> verify = recipient
>
> # Accept if the address is in a domain for which we are relaying, but again,
> # only if the recipient can be verified.
>
> accept domains = +relay_to_domains
> endpass
> message = unrouteable address
> verify = recipient
>
> # If control reaches this point, the domain is neither in +local_domains
> # nor in +relay_to_domains.
>
> # Accept if the message comes from one of the hosts for which we are an
> # outgoing relay. Recipient verification is omitted here, because in many
> # cases the clients are dumb MUAs that don't cope well with SMTP error
> # responses. If you are actually relaying out from MTAs, you should probably
> # add recipient verification here.
>
> accept hosts = +relay_from_hosts
>
> # Accept if the message arrived over an authenticated connection, from
> # any host. Again, these messages are usually from MUAs, so recipient
> # verification is omitted.
>
> # accept authenticated = *
>
> # Reaching the end of the ACL causes a "deny", but we might as well give
> # an explicit message.
>
> deny message = relay not permitted
>
>
> # This access control list is used for content scanning with the exiscan-acl
> # patch. You must also uncomment the entry for acl_smtp_data (scroll up),
> # otherwise the ACL will not be used. IMPORTANT: the default entries here
> # should be treated as EXAMPLES. You MUST read the file doc/exiscan-acl-spec.txt
> # to fully understand what you are doing ...
>
> acl_check_content:
>
> # First unpack MIME containers and reject serious errors.
> deny message = This message contains a MIME error ($demime_reason)
> demime = *
> condition = ${if >{$demime_errorlevel}{2}{1}{0}}
>
> # Reject typically wormish file extensions. There is almost no
> # sense in sending such files by email.
> deny message = This message contains an unwanted file extension ($found_extension)
> demime = src:vbs:bat:lnk:pif
>
> # Reject virus infested messages.
> #deny message = This message contains malware ($malware_name)
> # malware = *
>
> # Reject messages containing "viagra" in all kinds of whitespace/case combinations
> # WARNING: this is an example !
> deny message = This message matches a blacklisted regular expression ($regex_match_string)
> regex = [Vv] *[Ii] *[Aa] *[Gg] *[Rr] *[Aa]
>
> # Always add X-Spam-Score and X-Spam-Report headers, using SA system-wide settings
> # (user "nobody"), no matter if over threshold or not.
> warn message = X-Spam-Score: $spam_score ($spam_bar)
> spam = nobody:true
> warn message = X-Spam-Report: $spam_report
> spam = nobody:true
>
> # Add X-Spam-Flag if spam is over system-wide threshold
> warn message = X-Spam-Flag: YES
> spam = nobody
>
> # Reject spam messages with score over 30, using an extra condition.
> deny message = This message scored $spam_score points.
> spam = nobody:true
> condition = ${if >{$spam_score_int}{100}{1}{0}}
>
> # finally accept all the rest
> accept
>
>
> acl_check_sender:
> deny senders = mail_frog@??? : administrateur@???
> message = Cet utilisateur n'est pas autorisé a envoyer des messages.
> accept
>
>
> ######################################################################
> # ROUTERS CONFIGURATION #
> # Specifies how addresses are handled #
> ######################################################################
> # THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT! #
> # An address is passed to each router in turn until it is accepted. #
> ######################################################################
>
> begin routers
>
> # This router routes to remote hosts over SMTP by explicit IP address,
> # when an email address is given in "domain literal" form, for example,
> # <user@???>. The RFCs require this facility. However, it is
> # little-known these days, and has been exploited by evil people seeking
> # to abuse SMTP relays. Consequently it is commented out in the default
> # configuration. If you uncomment this router, you also need to uncomment
> # allow_domain_literals above, so that Exim can recognize the syntax of
> # domain literal addresses.
>
> # domain_literal:
> # driver = ipliteral
> # domains = ! +local_domains
> # transport = remote_smtp
>
>
> # This router handles aliasing using a linearly searched alias file with the
> # name SYSTEM_ALIASES_FILE. When this configuration is installed automatically,
> # the name gets inserted into this file from whatever is set in Exim's
> # build-time configuration. The default path is the traditional /etc/aliases.
> # If you install this configuration by hand, you need to specify the correct
> # path in the "data" setting below.
> #
> ##### NB You must ensure that the alias file exists. It used to be the case
> ##### NB that every Unix had that file, because it was the Sendmail default.
> ##### NB These days, there are systems that don't have it. Your aliases
> ##### NB file should at least contain an alias for "postmaster".
> #
> # If any of your aliases expand to pipes or files, you will need to set
> # up a user and a group for these deliveries to run under. You can do
> # this by uncommenting the "user" option below (changing the user name
> # as appropriate) and adding a "group" option if necessary. Alternatively, you
> # can specify "user" on the transports that are used. Note that the transports
> # listed below are the same as are used for .forward files; you might want
> # to set up different ones for pipe and file deliveries from aliases.
>
> # system_aliases:
> # driver = redirect
> # allow_fail
> # allow_defer
> # data = ${lookup{$local_part}lsearch{SYSTEM_ALIASES_FILE}}
> # user = exim
> # file_transport = address_file
> # pipe_transport = address_pipe
>
>
>
> amavis:
> driver = manualroute
> condition = "${if eq {$interface_port}{10025} {0}{1}}"
> # if scanning incoming mails, uncomment the following line and
> # change local_domains accordingly
> domains = +local_domains
> transport = amavis
> route_list = "* localhost byname"
> self = send
>
>
>
> smarthost_1:
> driver = manualroute
> domains = +local_domains
> local_parts = lsearch;/etc/exim/valid_mailboxes1
> transport = remote_smtp
> route_list = "* 192.168.102.12"
>
>
> smarthost_2:
> driver = manualroute
> domains = +local_domains
> local_parts = lsearch;/etc/exim/valid_mailboxes2
> transport = remote_smtp
> route_list = "* 192.168.102.12"
>
>
>
> # This router routes addresses that are not in local domains by doing a DNS
> # lookup on the domain name. Any domain that resolves to 0.0.0.0 or to a
> # loopback interface address (127.0.0.0/8) is treated as if it had no DNS
> # entry. Note that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated
> # as the local host inside the network stack. It is not 0.0.0.0/0, the default
> # route. If the DNS lookup fails, no further routers are tried because of
> # the no_more setting, and consequently the address is unrouteable.
>
> dnslookup:
> driver = dnslookup
> domains = ! +local_domains
> transport = remote_smtp
> ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
> no_more
>
>
>
> # The remaining routers handle addresses in the local domain(s).
>
>
>
> # This router handles forwarding using traditional .forward files in users'
> # home directories. If you want it also to allow mail filtering when a forward
> # file starts with the string "# Exim filter", uncomment the "allow_filter"
> # option.
>
> # The no_verify setting means that this router is skipped when Exim is
> # verifying addresses. Similarly, no_expn means that this router is skipped if
> # Exim is processing an EXPN command.
>
> # The check_ancestor option means that if the forward file generates an
> # address that is an ancestor of the current one, the current one gets
> # passed on instead. This covers the case where A is aliased to B and B
> # has a .forward file pointing to A.
>
> # The three transports specified at the end are those that are used when
> # forwarding generates a direct delivery to a file, or to a pipe, or sets
> # up an auto-reply, respectively.
>
> #userforward:
> # driver = redirect
> # check_local_user
> # file = $home/.forward
> # no_verify
> # no_expn
> # check_ancestor
> # allow_filter
> # file_transport = address_file
> # pipe_transport = address_pipe
> # reply_transport = address_reply
>
>
> # This router matches local user mailboxes.
>
> # localuser:
> # driver = accept
> # check_local_user
> # transport = local_delivery
>
>
>
> ######################################################################
> # TRANSPORTS CONFIGURATION #
> ######################################################################
> # ORDER DOES NOT MATTER #
> # Only one appropriate transport is called for each delivery. #
> ######################################################################
>
> # A transport is used only when referenced from a router that successfully
> # handles an address.
>
> begin transports
>
>
> # This transport is used for delivering messages over SMTP connections.
>
> amavis:
> driver = smtp
> port = 10024
> allow_localhost
>
> remote_smtp:
> driver = smtp
>
>
> # This transport is used for local delivery to user mailboxes in traditional
> # BSD mailbox format. By default it will be run under the uid and gid of the
> # local user, and requires the sticky bit to be set on the /var/mail directory.
> # Some systems use the alternative approach of running mail deliveries under a
> # particular group instead of using the sticky bit. The commented options below
> # show how this can be done.
>
> #local_delivery:
> # driver = appendfile
> # file = /var/mail/$local_part
> # delivery_date_add = true
> # envelope_to_add = true
> # return_path_add = true
> # group = mail
> # mode = 0660
> # directory = /home/${local_part}/Maildir/
> # maildir_format
>
>
> # This transport is used for handling pipe deliveries generated by alias or
> # .forward files. If the pipe generates any standard output, it is returned
> # to the sender of the message as a delivery error. Set return_fail_output
> # instead of return_output if you want this to happen only when the pipe fails
> # to complete normally. You can set different transports for aliases and
> # forwards if you want to - see the references to address_pipe in the routers
> # section above.
>
> address_pipe:
> driver = pipe
> return_output
>
>
> # This transport is used for handling deliveries directly to files that are
> # generated by aliasing or forwarding.
>
> address_file:
> driver = appendfile
> delivery_date_add
> envelope_to_add
> return_path_add
>
>
> # This transport is used for handling autoreplies generated by the filtering
> # option of the userforward router.
>
> address_reply:
> driver = autoreply
>
>
>
> ######################################################################
> # RETRY CONFIGURATION #
> ######################################################################
>
> begin retry
>
> # This single retry rule applies to all domains and all errors. It specifies
> # retries every 15 minutes for 2 hours, then increasing retry intervals,
> # starting at 1 hour and increasing each time by a factor of 1.5, up to 16
> # hours, then retries every 6 hours until 4 days have passed since the first
> # failed delivery.
>
> # Domain Error Retries
> # ------ ----- -------
>
> * * F,2h,15m; G,16h,1h,1.5; F,4d,6h
>
>
>
> ######################################################################
> # REWRITE CONFIGURATION #
> ######################################################################
>
> # There are no rewriting specifications in this default configuration file.
>
> begin rewrite
>
>
>
> ######################################################################
> # AUTHENTICATION CONFIGURATION #
> ######################################################################
>
> # There are no authenticator specifications in this default configuration file.
>
> begin authenticators
>
>
>
> ######################################################################
> # CONFIGURATION FOR local_scan() #
> ######################################################################
>
> # If you have built Exim to include a local_scan() function that contains
> # tables for private options, you can define those options here. Remember to
> # uncomment the "begin" line. It is commented by default because it provokes
> # an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
> # set in the Local/Makefile.
>
> # begin local_scan
>
>
> # End of Exim configuration file
--
.O.
..O
OOO
PGP key:
http://www.llorien.org/gnupg/key.pub
Insanity: doing the same thing over and over again and expecting
different results.
- Albert Einstein
