[exim] Mailing list messages go awry.

Kezdőlap
Üzenet törlése
Válasz az üzenetre
Szerző: Sherwood Botsford
Dátum:  
Címzett: exim-users
Tárgy: [exim] Mailing list messages go awry.


I have shot myself in the foot. I did something to my config
file that results in many messages that come in from a mailing
list be marked as recipient unknown.

What I have done (or tried to do...{rueful grimace}) is set it up
so that mail for non-existent users goes to postmaster. Once a
week or so, I go through this, adding some names to the blackhole
list. (As a school we have a high turnover. I forward for a year
after they leave, then junk anything else.) At the same time I
forward obvious user mis-spellings to the correct destination.

Somewhere I am doing something that on the basis of the To:
header is rewriting the envelope-to:.

As you can see from the example, my exim mail is going to the
postmaster. (So if you reply, be sure that sbotsford@???
gets a copy so I don't have to wade through a gigabyte of spam to
find it next tuesday.)

 From exim-users-bounces+sbotsford=sjsa.ab.ca@??? Fri May 05 
10:26:43 2006
X-UIDL: 8Kn!!:W("!NO"#!lLP!!
Return-path: <exim-users-bounces+sbotsford=sjsa.ab.ca@???>
Envelope-to: postmaster@localhost
Delivery-date: Fri, 05 May 2006 10:26:43 -0600
Received: from exim by postie.sjsa.ab.ca with spam-scanned (Exim 
4.42)
         id 1Fc0YV-000NYu-3q
         for postmaster@localhost; Fri, 05 May 2006 07:41:15 -0600
Received: from [127.0.0.1] (helo=pop.incentre.net)
         by postie.sjsa.ab.ca with esmtp (Exim 4.42)
         id 1Fc0YU-000NYr-93
         for postmaster@localhost; Fri, 05 May 2006 07:41:15 -0600
Received: by bach.incentre.net (mbox sjsa)
  (with Cubic Circle's cucipop (v1.31 1998/05/13) Fri May  5 
07:41:13 2006)
X-From_: exim-users-bounces+sbotsford=sjsa.ab.ca@???  Fri 
May  5 07:36:08 2
006
Received: from sesame.csx.cam.ac.uk (sesame.csx.cam.ac.uk 
[131.111.8.41])
         by bach.incentre.net (8.12.9p2/8.12.9) with ESMTP id 
k45Da6JX033546
         for <sbotsford@???>; Fri, 5 May 2006 07:36:07 
-0600 (MDT)
         (envelope-from 
exim-users-bounces+sbotsford=sjsa.ab.ca@???)
Received: from [::1] (port=1825 helo=sesame.csx.cam.ac.uk)
         by sesame.csx.cam.ac.uk with esmtp (Exim 4.44)
         id 1Fc0TB-000GFz-Re; Fri, 05 May 2006 14:35:45 +0100
Received: from happy.kiev.ua ([193.109.241.145]:35152)
         by sesame.csx.cam.ac.uk with esmtp (Exim 4.44) id 
1Fc0T6-000GFt-Is
         for exim-users@???; Fri, 05 May 2006 14:35:43 +0100
Received: from gul by happy.kiev.ua with local (Exim 4.54) id 
1Fc0T6-0005a2-3B
         for exim-users@???; Fri, 05 May 2006 16:35:40 +0300
Date: Fri, 5 May 2006 16:35:40 +0300
From: Pavel Gulchouck <gul@???>
To: exim-users@???
Message-ID: <20060505133539.GB10781@???>
References: <20060504223210.GI3242@???>
         <Pine.LNX.4.64.0605050941400.5850@???>
         <20060505120952.GA10781@???>
         <Pine.LNX.4.64.0605051359230.5850@???>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.64.0605051359230.5850@???>
X-Operating-System: Linux
X-FTN-Address: 2:463/68
X-GC: GCC d- s+: a35 C+++ UL++++ UB++++ P+ L++ E--- W++ N++ o-- 
K- w--- O++
X-GC: M? V- PS PE+ Y+ PGP+ t? 5? X? R? !tv b+ DI? D? G e h--- 
r+++ y+++
User-Agent: Mutt/1.5.6i
Subject: Re: [exim] problems with retry logic
X-BeenThere: exim-users@???
X-Mailman-Version: 2.1.8
Precedence: list
Reply-To: gul@???
List-Id: A user list for the exim MTA <exim-users.exim.org>
List-Unsubscribe: <http://www.exim.org/mailman/listinfo/exim-users>,
         <mailto:exim-users-request@exim.org?subject=unsubscribe>
List-Archive: <http://www.exim.org/mail-archives/exim-users>
List-Post: <mailto:exim-users@exim.org>
List-Help: <mailto:exim-users-request@exim.org?subject=help>
List-Subscribe: <http://www.exim.org/mailman/listinfo/exim-users>,
         <mailto:exim-users-request@exim.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: exim-users-bounces@???
Errors-To: exim-users-bounces+sbotsford=sjsa.ab.ca@???
X-Fetchmail-Warning: recipient address exim-users@??? didn't 
match any loca
l name
X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on
         postie.sjsa.internal.net
X-Spam-Status: No, score=0.0 required=3.0 tests=none 
autolearn=failed
         version=3.0.0
X-Spam-Level:
Status: O
X-Status:
X-Keywords:
...



Here's my config file:

#####################################################################
#                  Runtime configuration file for Exim 
     #
######################################################################


# SJSA MODIFIED


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



log_selector = +subject +address_rewrite -delay_delivery
+received_recipients -q
ueue_run
log_file_path = syslog

# 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 = postie.sjsa.ab.ca


# 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 =      @ : localhost : 
localhost.sjsa.internal.net \
                                 *.sjsa.ab.ca:sjsa.ab.ca : \
                                 *.sjsa.internal.net : 
sjsa.internal.net :\
                                 129.168.1.0/24


domainlist relay_to_domains =
hostlist relay_from_hosts = 127.0.0.1 : 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.

message_size_limit = 10M


# 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
#acl_smtp_mime = acl_check_mime
acl_smtp_data = acl_check_content

# You should not change that setting until you understand how
ACLs work.


# 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 = sjsa.ab.ca


# 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 = sjsa.ab.ca


# 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 = 30s


# 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 = 192.168.1.0/24
recipient_unqualified_hosts = 192.168.1.0/24
#
# 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 = 1h

# This option cancels (removes) frozen messages that are older
than a week.

timeout_frozen_after = 7d

system_filter = /opt/exim/filter

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


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

  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   = ^[./|] : ^.*[@%!] : ^.*/\\.\\./


# Accept mail to postmaster in any local domain, regardless of
the source,
# and without verifying the sender.

   accept  local_parts   = postmaster
           domains       = +local_domains


   # Accept all local domains until we get DNS working.
   #accept        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 a
t $dnslist_domain
   #         log_message   = found in $dnslist_domain
   #         dnslists      = black.list.example


#############################################################################

     accept message = X-SpamTrap: Fake user in recipients
           domains = +local_domains
           recipients = /opt/exim/spamtrap
           set acl_m0 = "SpamTrap"


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


acl_check_mime:
# Decode MIME parts to disk. This will support virus scanners
later.
#warn decode = default

   # File extension filtering.
   warn message = X-Spam-Ext: Blacklisted file extension detected
        condition = ${if match \
                     {1}{0}}


accept


#acl_smtp_data:
#       accept mssage = "X-Spam-HoneyPot: False addresses detected
#       condition = ${if match {$acl_m0}{SpamTrap} }
#       control = freeze


acl_check_content:
#accept domains = +local_domains

   #deny message = "Addressed to non-existent recipient"
#     condition = ${if  match \
#                       {$acl_m0} \
#                       {"SpamTrap"} \
#                       {1}{0}}


         #save "/var/spool/mail/spamtrap"


   # Reject virus infested messages.
   #deny  message = This message contains malware ($malware_name)
   #      malware = *


   # Always add X-Spam-Score and X-Spam-Report headers, using SA 
system-wide sett
ings
   # (user "nobody"), no matter if over threshold or not.
   warn  message = X-Spam-Score: $spam_score_int ($spam_bar)
        spam = nobody:true
   warn  message = X-Spam-Bar: SPAM ($spam_bar)
        spam = nobody:true


   warn  message = X-Spam-Report: $spam_report
         spam = nobody:true
         condition = ${if >{$spam_score_int}{40}{1}{0}}


   # 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 10, using an extra 
condition.
   ##warn  message = This message scored $spam_score points. 
Congratulations!
   ##      spam = nobody:true
   ##      condition = ${if >{$spam_score_int}{100}{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 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



#copy_stream:
# driver = accept
# transport = stream_delivery
# unseen

# Added 3 Nov 2005

#spamtrap_router:
# driver = redirect
# domains = +local_domains
# condition = { match {$acl_m0}{"SpamTrap"}}
# data = spam

# ADDED 12 July 2002 SGB
# Modified to route specific domains to telus

#send_to_telus:
#       driver = manualroute
#       domains = !+local_domains
#       transport = remote_smtp
#       route_list = * mx01.telusplanet.net


#send_to_gateway:
#     driver = manualroute
#     domains = !+local_domains
#     transport = remote_smtp
#     route_list = aol.com mx02.telusplanet.net ; \
#               netcom.ca mx02.telusplanet.net ; \
#               compuserve.com mx02.telusplanet.net ; \
#               ecn.ab.ca mx02.telusplanet.net ; \
#               sierrawireless.com mx02.telusplanet.net ; \
#               cs.com  mx02.telusplanet.net    ; \
#               *.mr.outblaze.com mx02.telusplanet.net ;\
#               *.ualberta.net mx02.telusplanet.net ;\
#               mail.mcprint.ca mx02.telusplanet.net ;\
#               mail.global.frontbridge.com mx02.telusplanet.net ;\
#               hotmail.com mx02.telusplanet.net    ; \
#               *.kerio.com mx02.telusplanet.net ;


#     route_list = * smtp.incentre.net
#     route_list = * 192.168.1.1


# 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
#fallback_hosts = mx01.telus.net:mx02.telus.net
no_more


# The remaining routers handle addresses in the local domain(s).


# This router handles aliasing using a traditional /etc/aliases file.
#
##### NB You must ensure that /etc/aliases 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
file_transport = address_file
pipe_transport = address_pipe

# Placed here so that local aliases happen first.
spamcheck_router:
no_verify
check_local_user
# When to scan a message :
# - it isn't already flagged as spam
# - it isn't already scanned
# - it isn't from outside.
senders = ! *@sjsa.ab.ca

   condition = \
   "${if and { {!def:h_X-Spam-Flag:} \
               {!eq {$received_protocol}{spam-scanned}} \
             }\
             {1}{0}\
     }"
   driver = accept
   transport = spamcheck


# 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
directory_transport = address_file
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

unkownlocaluser:
driver = accept
transport = unknown_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.

remote_smtp:
         driver = smtp
         message_size_limit = 10M


# Spamtrap:
spamtrap_transport:
         driver = appendfile
         file = /var/mail/spool/spamtrap
         user = exim
         group = mail


# SpamAssassin
spamcheck:
         driver = pipe
         command = /opt/exim/bin/exim -oMr spam-scanned -bS
         use_bsmtp = true
         transport_filter = /opt/exim/bin/spamc
         home_directory = "/tmp"
         current_directory = "/tmp"
# must use a privileged user to set $received_protocol on the way 
back in!
         user = exim
         group = mail
         log_output = true
         return_fail_output = true
         return_path_add = false
         message_prefix =
         message_suffix =



# 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/spool/mail direc
tory.
# 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/spool/mail/$local_part
delivery_date_add
envelope_to_add
return_path_add
group = mail
mode = 0660

stream_delivery:
driver = appendfile
file = /var//spool/mail/mailstream
user=exim
group=mail
mode = 0660

unknown_local_delivery:
driver = appendfile
file = /var/spool/mail/postmaster
user = postmaster
delivery_date_add
envelope_to_add
group = mail
mode = 0660

# 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
group = mail
mode = 0660
check_owner = false

# 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


# Every 10 minutes for telus.
*.telus.net             *          F,3d,10m;


# Every 15 for 2 hours, every 30 min for 4 more, every 2 hours
for the
# rest of the day, every 6 hours for 4 days.

*                      *           F,2h,15m; F,4h,30m ; F,18h,2h; 
F,4d,6h



# BANG on hotmail's door until it opens

*.hotmail.com           *               F,3d,10m


# If we can't deliver locally bounce it quickly.

sjsa.ab.ca              *          F, 1h, 15m


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

   fixed_plain:
     driver = plaintext
     public_name = PLAIN
     client_send = ^username^mysecret


# End of Exim configuration file