Re: [Exim] Yahoo bulk email problem

>>######################################################################
>>#                           ADDED ZBTA SAVEEVMAIL                    #
>>######################################################################
>># New configuration / 2002-9-22 /
>>trusted_users = nobody
>>ZBTAMAIL_HOME = /usr/local/mailers
>>ZBTAMAIL_SAVEMAIL = /usr/local/mailers/savemail.pl
>>ZBTAMAIL_UID = nobody
>>ZBTAMAIL_GID = nobody

>>######################################################################
>>#                       ACL CONFIGURATION                            #
>>#         Specifies access control lists for incoming SMTP mail      #
>>######################################################################
>>begin acl

>>#############################################################################
>>   # The following section of the ACL is concerned with local parts that
>>contain
>>   # @ or % or ! or / or | or dots in unusual places.
>>   #
>>   # The characters other than dots are rarely found in genuine local
>>parts, but
>>   # 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. It 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.
>>#  old method
>>#  deny    local_parts   = ^.*[@%!/|] : ^\\.
>>   deny    domains       = +local_domains
>>           local_parts   = ^[.] : ^.*[@%!/|]
>>   # The second rule applies to all other domains, and is less strict. This
>>   # 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    domains       = !+local_domains
>>           local_parts   = ^[./|] : ^.*[@%!] : ^.*/\\.\\./

>>   deny    domains = *.refhost.net : list.cashculture.com
>>   deny    hosts = 217.158.42.0/255.255.255.0 : 202.179.7.51 : 202.131.0.7
>>: 216.18.7.59 : 81.199.84.104 : 61.154.79.46 : 68.208.25.230 :
>>80.179.249.197 : 192.116.116.103
>>   deny    senders = staff@??? : openlifebiz@??? :
>>introduce.site@???
>>   # deny if connection comes from different host, but domain is in
>>local_domains list
>>#  deny           hosts = !202.179.0.199
>>#          senders = *@chinggis.com
>>#         domains = +local_domains
>>   # 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      = sbl-xbl.spamhaus.org : relays.ordb.org :
>>dnsbl.njabl.org : bl.spamcop.net : dnsbl.sorbs.net : dsn.rfc-ignorant.org :
>>list.dsbl.org
>>##  warn   hosts        = !127.0.0.1
>>##        message       = X-Warning: $sender_host_address is in a relay list
>>at $dnslist_domain
>>##         log_message   = found in $dnslist_domain
>>##         dnslists      = relays.mail-abuse.org
>>   deny    message       = rejected because $sender_host_address is listed
>>as routing via an insecure proxy at $dnslist_domain\n$dnslist_text
>>           dnslists      = opm.blitzed.org
>>#          dnslists      = opm.blitzed.org : formmail.relays.monkeys.com :
>>proxies.relays.monkeys.com

>>#############################################################################
>>   # 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
>>#         verify        = sender/callout=15s
>>           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:
>>   deny  senders = :
>>         message = A valid sender header is required for bounces
>>         !verify  = header_sender
>>   # 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 = scr:vbs:bat:lnk:pif
>>   # Reject virus infested messages.
>>   deny  message = This message contains malware ($malware_name)
>>         demime = *
>>         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
>>#        !senders = *@mongol.net : *@publica.ub.mng.net : *@micom.mng.net
>>##        !hosts = +relay_from_hosts
>>#        spam = nobody:true
>>   # Add X-Spam-Flag if spam is over system-wide threshold
>>   warn message = X-Spam-Flag: YES
>>         spam = nobody
>>   # add second subject line with *SPAM* marker when message
>>   # is over threshold
>>   warn  message = Subject: ***SPAM*** $h_Subject
>>         spam = nobody
>>   # Reject spam messages. Remember to tweak your
>>   # site-wide SA profile. Do not spam-scan messages
>>   # larger than eighty kilobytes.
>>   deny message = Spam score too high ($spam_score)
>>      condition = ${if <{$message_size}{80k}{1}{0}}
>>      spam = nobody:true
>>      condition = ${if >{$spam_score_int}{80}{1}{0}}
>>   # finally accept all the rest
>>   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 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
>>   condition = ${if exists{$home/.forward} {yes} {no} }
>># This router matches local user mailboxes.
>>#zbtarouter:
>>#  driver = accept
>>#  condition = ${if eq {}{${lookup mysql {SELECT id FROM host WHERE name =
>>'$domain'}}}{no}{yes}}
>>#  transport = zbtamail
>>localuser:
>>   driver = accept
>>   check_local_user
>>   transport = local_delivery
>>non_exist:
>>   driver = accept
>>   transport = non_exist_reply
>>   no_verify
>>######################################################################
>>#                      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
>>non_exist_reply:
>>   driver = autoreply
>>   user = mailnull
>>   to = $sender_address
>>   subject = User does not exist
>>   text = You sent mail to $local_part. That's not a valid user here.

>>######################################################################
>>#                             ZBTA DELIVERY                          #
>>######################################################################
>>zbtamail:
>>   driver = pipe
>>   command = ZBTAMAIL_SAVEMAIL "$local_part" "$domain" "$message_size"
>>"$spam_score" "$sender_address" "$sender_host_address"
>>   current_directory = ZBTAMAIL_HOME
>>   home_directory = ZBTAMAIL_HOME
>>   user = ZBTAMAIL_UID
>>   group = ZBTAMAIL_GID
>>   log_output
>>   log_defer_output
>>   return_fail_output
>>#  return_path_add
>>   delivery_date_add
>>   envelope_to_add

>>######################################################################
>>#                      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
>>plain:
>>     driver = plaintext
>>     public_name = PLAIN
>>     server_prompts = :
>>     server_condition = ${lookup mysql{select count(*) from usrs where \
>>(id = '${quote_mysql:$2}') and pwrd = '${quote_mysql:$3}' \
>>and pwrd != ''}}

>>     server_set_id = $2
>>login:
>>     driver = plaintext
>>     public_name = LOGIN
>>     server_prompts = Username:: : Password::
>>     server_condition = ${lookup mysql{select count(*) from usrs where \
>>(id = '${quote_mysql:$1}') and pwrd = '${quote_mysql:$2}' \
>>and pwrd != ''}}

>>     server_set_id = $1
>>cram:
>>     driver = cram_md5
>>     public_name = CRAM-MD5
>>     server_secret = ${lookup mysql{select pwrd from usrs \
>>where (id = '${quote_mysql:$1}') and pwrd != ''}}

>>     server_set_id = $1