Re: [exim] PROBLEMS HELP

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Alex
Datum:  
To: xyon
CC: exim-users
Betreff: Re: [exim] PROBLEMS HELP
Thanks xyon I solved the overquota message to sender.




2006/4/15, xyon <xyon@???>:
> You need this in under the Retry section (for quotas):
>
> begin retry
>
> *                       quota
> *                      *           F,2h,15m; G,16h,1h,1.5; F,4d,6h

>
>
> On Sat, 2006-04-15 at 01:52 +0200, Alex wrote:
> > My exim is 4.60 compiled.
> >
> > i put may config file why i have some problems
> >
> > The server rejects the virus and spam messages but don't send a message
> >
> > Then if a user i overquota, retry never sends a mail to sender.
> >
> >
> > ################################################
> >
> >
> > #split_spool_directory = true
> > #check_spool_space = 1024M
> > #smtp_check_spool_space = true
> >
> > message_size_limit = 10M
> > #bounce_return_size_limit = 8k
> >
> > deliver_queue_load_max = 2.00
> > queue_only_load = 1.50
> > remote_max_parallel = 8
> >
> >
> > primary_hostname = test.net
> >
> >
> > #domainlist local_domains = @
> > VIRTUAL_DOMAINS = SELECT DISTINCT domain FROM domains WHERE type =
> > 'local' AND enabled = '1' AND domain = '${quote_mysql:$domain}'
> > RELAY_DOMAINS = SELECT DISTINCT domain FROM domains WHERE type =
> > 'relay' AND domain = '${quote_mysql:$domain}'
> > ALIAS_DOMAINS = SELECT DISTINCT alias FROM domainalias WHERE alias =
> > '${quote_mysql:$domain}'
> > domainlist local_domains = @ : ${lookup mysql{VIRTUAL_DOMAINS}} :
> > ${lookup mysql{ALIAS_DOMAINS}}
> > domainlist relay_to_domains = ${lookup mysql{RELAY_DOMAINS}}
> > hostlist relay_from_hosts = localhost :
> > net-lsearch;/usr/local/var/state/exact/relay
> > #domainlist relay_to_domains =
> > #hostlist relay_from_hosts = 127.0.0.1
> >
> >
> > hide mysql_servers = localhost::(/var/run/mysqld/mysqld.sock)/test/test/test
> >
> >
> > # 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.
> >
> > acl_smtp_rcpt = acl_check_rcpt
> > acl_smtp_data = acl_check_content
> > acl_smtp_helo = acl_check_helo
> >
> >
> > av_scanner = clamd:127.0.0.1 3310
> > spamd_address = 127.0.0.1 783
> >
> >
> > # qualify_domain =
> >
> >
> > # 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 =
> >
> > # allow_domain_literals
> >
> >
> > exim_user = exim
> > exim_group = exim
> > never_users = root
> > trusted_users = www-data
> >
> >
> > # 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 = 7d
> >
> >
> >
> > ######################################################################
> > #                       ACL CONFIGURATION                            #
> > #         Specifies access control lists for incoming SMTP mail      #
> > ######################################################################

> >
> > begin acl
> >
> > acl_check_helo:
> >   accept hosts = :
> >   accept hosts = +relay_from_hosts
> >   drop condition = ${if match{$sender_helo_name}{MY_IP}{yes}{no} }
> >        message   = "Dropped spammer pretending to be us"
> >   drop condition = ${if
> > match{$sender_helo_name}{^[0-9]\.[0-9]\.[0-9]\.[0-9]}{yes}{no} }
> >        message   = "Dropped IP-only or IP-starting helo"
> >   accept
> > # 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 = :
> >
> > #############################################################################
> > # The following section of the ACL is concerned with local parts that contain
> > # @ or % or ! or / or | or dots in unusual places.
> > #
> >
> >   deny    message       = DNSBL listed at $dnslist_domain\n$dnslist_text
> >           dnslists      = sbl-xbl.spamhaus.org:list.dsbl.org:dynablock.njabl.org

> >
> > # are often tried by people looking to circumvent relaying restrictions.
> > # Therefore, although they are valid in local parts, these rules lock them
> > # out, as a precaution.
> > #
> > # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
> > # allows them because they have been encountered. (Consider local parts
> > # constructed as "firstinitial.secondinitial.familyname" when applied to
> > # someone like me, who has no second initial.) However, a local part starting
> > # with a dot or containing /../ can cause trouble if it is used as part of a
> > # file name (e.g. for a mailing list). This is also true for local parts that
> > # contain slashes. A pipe symbol can also be troublesome if the local part is
> > # incorporated unthinkingly into a shell command line.
> > #
> > # Two different rules are used. The first one is stricter, and is applied to
> > # messages that are addressed to one of the local domains handled by this
> > # host. The line "domains = +local_domains" restricts it to domains that are
> > # defined by the "domainlist local_domains" setting above. The rule blocks
> > # local parts that begin with a dot or contain @ % ! / or |. If you have
> > # local accounts that include these characters, you will have to modify this
> > # rule.
> >
> >   deny    message       = Restricted characters in address
> >           domains       = +local_domains
> >           local_parts   = ^[.] : ^.*[@%!/|]

> >
> > # The second rule applies to all other domains, and is less strict. The line
> > # "domains = !+local_domains" restricts it to domains that are NOT defined by
> > # the "domainlist local_domains" setting above. The exclamation mark is a
> > # negating operator. This rule allows your own users to send outgoing
> > # messages to sites that use slashes and vertical bars in their local parts.
> > # It blocks local parts that begin with a dot, slash, or vertical bar, but
> > # allows these characters within the local part. However, the sequence /../
> > # is barred. The use of @ % and ! is blocked, as before. The motivation here
> > # is to prevent your users (or your users' viruses) from mounting certain
> > # kinds of attack on remote sites.
> >
> >   deny    message       = Restricted characters in address
> >           domains       = !+local_domains
> >           local_parts   = ^[./|] : ^.*[@%!] : ^.*/\\.\\./
> >   #############################################################################

> >
> > # 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

> >
> > # Accept if the message comes from one of the hosts for which we are an
> > # outgoing relay. It is assumed that such hosts are most likely to be MUAs,
> > # so we set control=submission to make Exim treat the message as a
> > # submission. It will fix up various errors in the message, for example, the
> > # lack of a Date: header line. If you are actually relaying out out from
> > # MTAs, you may want to disable this. If you are handling both relaying from
> > # MTAs and submissions from MUAs you should probably split them into two
> > # lists, and handle them differently.
> >
> > # 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.
> >
> > # Note that, by putting this test before any DNS black list checks, you will
> > # always accept from these hosts, even if they end up on a black list. The
> > # assumption is that they are your friends, and if they get onto a black
> > # list, it is a mistake.
> >
> >   accept  hosts         = +relay_from_hosts
> >           control       = submission

> >
> > # Accept if the message arrived over an authenticated connection, from
> > # any host. Again, these messages are usually from MUAs, so recipient
> > # verification is omitted, and submission mode is set. And again, we do this
> > # check before any black list tests.
> >
> >   accept  authenticated = *
> >           control       = submission

> >
> >   #############################################################################
> >   # There are no default 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 can get Exim to perform a DNS black list lookup at this
> >   # point. The first one denies, whereas the second just warns.
> >   #
> >    deny    message       = rejected because $sender_host_address is in
> > a black list at $dnslist_domain\n$dnslist_text
> >            log_message   = found in $dnslist_domain
> >          dnslists      = sbl.spamhaus.org : cbl.abuseat.org :
> > dul.dnsbl.sorbs.net : dynablock.njabl.org
> >   #
> >   # 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
> >   #############################################################################

> >
> > #############################################################################
> > # This check is commented out because it is recognized that not every
> > # sysadmin will want to do it. If you enable it, the check performs
> > # Client SMTP Authorization (csa) checks on the sending host. These checks
> > # do DNS lookups for SRV records. The CSA proposal is currently (May 2005)
> > # an Internet draft. You can, of course, add additional conditions to this
> > # ACL statement to restrict the CSA checks to certain hosts only.
> > #
> > # require verify = csa
> > #############################################################################
> >
> > # 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
> >           verify        = recipient

> >
> > # Accept if the address is in a domain for which we are an incoming relay,
> > # but again, only if the recipient can be verified.
> >
> >   accept  domains       = +relay_to_domains
> >           endpass
> >           verify        = recipient

> >
> > # Reaching the end of the ACL causes a "deny", but we might as well give
> > # an explicit message.
> >
> >   deny    message       = relay not permitted

> >
> >
> > # This ACL is used after the contents of a message have been received. This
> > # is the ACL in which you can test a message's headers or body, and in
> > # particular, this is where you can invoke external virus or spam scanners.
> > # Some suggested ways of configuring these tests are shown below, commented
> > # out. Without any tests, this ACL accepts all messages. If you want to use
> > # such tests, you must ensure that Exim is compiled with the content-scanning
> > # extension (WITH_CONTENT_SCAN=yes in Local/Makefile).
> >
> > acl_check_content:
> >
> > # Deny if the message contains a virus. Before enabling this check, you
> > # must install a virus scanner and set the av_scanner option above.
> > #
> >
> >   deny   message   = This message contains a virus ($malware_name).
> >          malware   = *
> >          log_message     = This message contains malware ($malware_name)

> >
> >   deny  message = This message matches a blacklisted regular
> > expression ($regex_match_string)
> >         regex = [Vv] *[Ii] *[Aa] *[Gg] *[Rr] *[Aa]

> >
> >   warn message = X-Spam-Score: $spam_score ($spam_bar)
> >       spam = spamd:true

> >
> >   warn message = X-Spam-Flag: YES
> >       spam = spamd

> >
> >   deny message   = This message scored $spam_score spam points. See
> > http://www.sput.nl/spam/
> >         #spam      = spamd:true
> >       spam      = nobody:true
> >         condition = ${if >{$spam_score_int}{10}{1}{0}}

> >
> >
> >
> > # Accept the message.
> >
> > 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 routes addresses that are not in local domains by doing a DNS
> > # lookup on the domain name. The exclamation mark that appears in "domains = !
> > # +local_domains" is a negating operator, that is, it can be read as "not". The
> > # recipient's domain must not be one of those defined by "domainlist
> > # local_domains" above for this router to be used.
> > #
> > # If the router is used, 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), that is those
> > # domains that are defined by "domainlist local_domains" above.
> >
> >
> > virtual_domains:
> >   driver = redirect
> >   allow_fail
> >   data = ${lookup mysql{select smtp from users,domains \
> >               where localpart = '${quote_mysql:$local_part}' \
> >               and domain = '${quote_mysql:$domain}' \
> >               and domains.enabled = '1' \
> >               and users.enabled = '1' \
> >               and users.domain_id = domains.domain_id}}
> >   headers_add = ${if >{$spam_score_int}{${lookup mysql{select
> > users.sa_tag * 10 from users,domains \
> >               where localpart = '${quote_mysql:$local_part}' \
> >               and domain = '${quote_mysql:$domain}' \
> >               and users.on_spamassassin = '1' \
> >               and users.domain_id=domains.domain_id }{$value}fail}} {X-Spam-Flag: YES\n}{} }
> >   headers_remove = ${if or { { <{$spam_score_int}{1} } \
> >                            { <{$spam_score_int}{${lookup mysql{select users.sa_tag * 10
> > from users,domains \
> >                              where localpart = '${quote_mysql:$local_part}' \
> >                              and domain = '${quote_mysql:$domain}' \
> >                              and users.on_spamassassin = 1 \
> >                              and users.domain_id=domains.domain_id}{$value}fail}} } \
> >                            { eq {0}{${lookup mysql{select users.sa_tag * 10 from users,domains \
> >                              where localpart = '${quote_mysql:$local_part}' \
> >                              and domain = '${quote_mysql:$domain}' \
> >                              and users.on_spamassassin = 0 \
> >                              and users.domain_id=domains.domain_id}{$value}fail}}} \
> >                          } {X-Spam-Score:X-Spam-Report} }
> >   local_part_suffix = -*
> >   local_part_suffix_optional
> >   retry_use_local_part
> >   file_transport = virtual_delivery
> >   reply_transport = address_reply
> >   pipe_transport = address_pipe

> >
> > virtual_domain_alias:
> >   driver = redirect
> >   allow_fail
> >   data = ${lookup mysql{select concat('${quote_mysql:$local_part}@', domain) \
> >               from domains,domainalias where domainalias.alias =
> > '${quote_mysql:$domain}' \
> >               and domainalias.domain_id = domains.domain_id}}
> >   retry_use_local_part
> > # This router handles aliasing using a linearly searched alias file with the
> > # name /etc/aliases. 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{/etc/aliases}}
> > user = exim
> > group = exim
> > file_transport = address_file
> > pipe_transport = address_pipe
> >
> >
> > # 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" or "# Sieve filter", uncomment
> > # the "allow_filter" option.
> >
> > # If you want this router to treat local parts with suffixes introduced by "-"
> > # or "+" characters as if the suffixes did not exist, uncomment the two local_
> > # part_suffix options. Then, for example, xxxx-foo@??? will be treated
> > # in the same way as xxxx@??? by this router. You probably want to make
> > # the same change to the localuser router.
> >
> > # 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
> > # local_part_suffix = +* : -*
> > # local_part_suffix_optional
> > file = $home/.forward
> > # allow_filter
> > no_verify
> > no_expn
> > check_ancestor
> > file_transport = address_file
> > pipe_transport = address_pipe
> > reply_transport = address_reply
> >
> >
> > # This router matches local user mailboxes. If the router fails, the error
> > # message is "Unknown user".
> >
> > # If you want this router to treat local parts with suffixes introduced by "-"
> > # or "+" characters as if the suffixes did not exist, uncomment the two local_
> > # part_suffix options. Then, for example, xxxx-foo@??? will be treated
> > # in the same way as xxxx@??? by this router.
> >
> > localuser:
> > driver = accept
> > check_local_user
> > # local_part_suffix = +* : -*
> > # local_part_suffix_optional
> > transport = local_delivery
> > cannot_route_message = Unknown user
> >
> >
> >
> > ######################################################################
> > #                      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.
> >
> > 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 = /home/usuaris/$local_part
> > delivery_date_add
> > envelope_to_add
> > return_path_add
> > group = mail
> > user = $local_part
> > mode = 0660
> > no_mode_fail_narrower
> > virtual_delivery:
> >
> > driver = appendfile
> > #file = /var/mail/$local_part
> > #file = /home/$local_part
> > delivery_date_add
> > envelope_to_add
> > return_path_add
> > group = mail
> > #user = $local_part
> > mode = 0660
> > no_mode_fail_narrower
> >
> > #  driver = appendfile
> > #  envelope_to_add
> > #  return_path_add
> > #  mode = 0600
> > #  maildir_format = false
> > #  create_directory = false
> >   file = ${lookup mysql{select smtp from users,domains \
> >               where localpart = '${quote_mysql:$local_part}' \
> >               and domain = '${quote_mysql:$domain}' \
> >               and users.domain_id = domains.domain_id}}

> >
> >   user = ${lookup mysql{select users.uid  from users,domains \
> >               where localpart = '${quote_mysql:$local_part}' \
> >               and domain = '${quote_mysql:$domain}' \
> >               and users.domain_id = domains.domain_id}}
> > # group = ${lookup mysql{select users.gid from users,domains \
> > #             where localpart = '${quote_mysql:$local_part}' \
> > #             and domain = '${quote_mysql:$domain}' \
> > #             and users.domain_id = domains.domain_id}}

> >
> > # 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
> > user = ${lookup mysql{select users.uid from users,domains where
> > localpart = '${quote_mysql:$local_part}' and domain =
> > '${quote_mysql:$domain}' and users.domain_id = domains.domain_id}}
> > group = ${lookup mysql{select users.gid from users,domains where
> > localpart = '${quote_mysql:$local_part}' and domain =
> > '${quote_mysql:$domain}' and users.domain_id = domains.domain_id}}
> >
> > address_pipe_catchall:
> > driver = pipe
> > return_output
> > user = ${lookup mysql{select users.uid from users,domains where
> > localpart = '*' and domain = '${quote_mysql:$domain}' and
> > users.domain_id = domains.domain_id}}
> > group = ${lookup mysql{select users.gid from users,domains where
> > localpart = '*' and domain = '${quote_mysql:$domain}' and
> > users.domain_id = domains.domain_id}}
> >
> > address_pipe_local:
> > 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.
> >
> > # Address or Domain    Error       Retries
> > # -----------------    -----       -------

> >
> > *                      *           F,1h,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
> >
> > plain_login:
> >         driver = plaintext
> >         public_name = PLAIN
> >         server_condition = ${lookup mysql{SELECT '1' FROM users \
> >                               WHERE localpart = '${quote_mysql:$2}' \
> >                               AND clear = '${quote_mysql:$3}'} {yes}{no}}
> >         server_set_id = $2

> >
> > fixed_login:
> >         driver = plaintext
> >         public_name = LOGIN
> >         server_prompts = "Username:: : Password::"
> >         server_condition = ${lookup mysql{SELECT '1' FROM users \
> >                               WHERE localpart = '${quote_mysql:$1}' \
> >                               AND clear = '${quote_mysql:$2}'} {yes}{no}}
> >         server_set_id = $1

> >
> > fixed_cram:
> >         driver = cram_md5
> >         public_name = CRAM-MD5
> >         server_secret = ${lookup mysql{SELECT clear FROM users \
> >                               WHERE localpart = '${quote_mysql:$1}'}{$value}fail}
> >         server_set_id = $1

> >
> >
> > # End of Exim configuration file
>
>
>