Re: [Exim] Failed to send message from address_reply transpo…

Pàgina inicial
Delete this message
Reply to this message
Autor: Simon Alman
Data:  
A: exim-users
Assumpte: Re: [Exim] Failed to send message from address_reply transport error
Ooops, didn't realise that the mailing list automatically strips
attachments - I've embedded the attachments queue.log and exim.conf in the
message below:

Regards

Simon Alman

-----------------------------------queue.log------------------------------------------------
Exim version 4.05 uid=0 gid=0 pid=14540 L=834cd8 D=fff7577f
Berkeley DB: Sleepycat Software: DB 2.4.14: (6/2/98)
changed uid/gid: forcing real = effective
uid=0 gid=0
auxiliary group list: <none>
trusted user
admin user
skipping ACL configuration - not needed
set_process_info: 14540 delivering specified messages
set_process_info: 14540 delivering 17mu5t-0003C8-00
reading spool file 17mu5t-0003C8-00-H
user=root uid=0 gid=0 sender=<user1>@<domain>
sender_fullhost = (grumpy.<domain>) [192.168.100.113]
sender_rcvhost = [192.168.100.113] (helo=grumpy.<domain> ident=<user1>)
sender_local=0 ident=<user1>
Non-recipients:
-->\0\<user2>@<domain> [1]
-->/home/<user2>/Backup/:<user2>@<domain> [0]
---- End of tree ----
recipients_count=1
body_linecount=2 message_linecount=14
Delivery address list:
<user2>@<domain>
locking /var/spool/exim/db/retry.lockfile
locked /var/spool/exim/db/retry.lockfile
opened hints database /var/spool/exim/db/retry: flags=0
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Considering: <user2>@<domain>
active address <user2>@<domain>
local_part=<user2> domain=<domain>
unique = <user2>@<domain>
dbfn_read: key=R:<domain>
dbfn_read: key=R:<user2>@<domain>
no domain retry record
no address retry record
<user2>@<domain>: queued for routing
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

routing <user2>@<domain>
--------> dnslookup router <--------
local_part=<user2> domain=<domain>
checking domains
<domain> in "chameleon: <domain>: *.<domain>: localhost"? yes (matched
"<domain>")
<domain> in "! +local_domains"? no (matched "! +local_domains")
cached lookup data = NULL
dnslookup router skipped: domains mismatch
--------> system_aliases router <--------
local_part=<user2> domain=<domain>
calling system_aliases router
rda_interpret (string): ${lookup{$local_part}lsearch{/etc/aliases_$domain}}
search_open: lsearch "/etc/aliases_<domain>"
search_find: file="/etc/aliases_<domain>"
key="<user2>" partial=-1
LRU list:
8/etc/aliases_<domain>
End
internal_search_find: file="/etc/aliases_<domain>"
type=lsearch key="<user2>"
file lookup required for <user2>
in /etc/aliases_<domain>
lookup failed
expanded:
file is not a filter file
parse_forward_list:
system_aliases router declined for <user2>@<domain>
--------> userforward router <--------
local_part=<user2> domain=<domain>
checking for local user
calling userforward router
rda_interpret (file): $home/.forward
expanded: /home/<user2>/.forward
changed uid/gid: userforward router
uid=531 gid=531
auxiliary group list: <none>
203 bytes read from /home/<user2>/.forward
data is a filter program
Filter: start of processing
Filter: end of processing
rda_interpret: subprocess yield=0 error=NULL
set transport address_reply
userforward router generated ><user1> <<user1>@<domain>>
pipe, file, or autoreply
errors_to=NULL transport=address_reply
uid=531 gid=531 home=\N/home/<user2>\N
userforward router generated <user2>@<domain>
errors_to=NULL transport=NULL
uid=unset gid=unset home=NULL
set transport address_directory
userforward router generated /home/<user2>/Backup/
pipe, file, or autoreply
errors_to=NULL transport=address_directory
uid=531 gid=531 home=\N/home/<user2>\N
routed by userforward router
envelope to: <user2>@<domain>
transport: <none>
locking /var/spool/exim/db/retry.lockfile
locked /var/spool/exim/db/retry.lockfile
opened hints database /var/spool/exim/db/retry: flags=0
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Considering: /home/<user2>/Backup/
unique = /home/<user2>/Backup/:<user2>@<domain>
/home/<user2>/Backup/ was previously delivered: discarded
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Considering: <user2>@<domain>
active address <user2>@<domain>
local_part=<user2> domain=<domain>
unique = \0\<user2>@<domain>
\0\<user2>@<domain> was previously delivered: discarded
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Considering: ><user1> <<user1>@<domain>>
unique = ><user1> <<user1>@<domain>>:<user2>@<domain>
queued for address_reply transport
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

After routing:
   Local deliveries:
     ><user1> <<user1>@<domain>>
   Remote deliveries:
   Failed addresses:
   Deferred addresses:
search_tidyup called

>>>>>>>>>>>>>>>>>> Local deliveries >>>>>>>>>>>>>>>>>>

--------> ><user1> <<user1>@<domain>> <--------
locking /var/spool/exim/db/retry.lockfile
locked /var/spool/exim/db/retry.lockfile
opened hints database /var/spool/exim/db/retry: flags=0
dbfn_read: key=T:><user1> <<user1>@<domain>>:<user2>@<domain>
retry record exists: age=425 (max=604800)
time to retry = -475 expired = 0
search_tidyup called
changed uid/gid: local delivery to ><user1> <<user1>@<domain>> <><user1>
<<user1>@<domain>>> transport=address_reply
uid=531 gid=531
auxiliary group list: <none>
home=/home/<user2> current=/home/<user2>
set_process_info: 14543 delivering 17mu5t-0003C8-00 to ><user1>
<<user1>@<domain>> using address_reply
address_reply transport entered
taking data from address
writing data block fd=9 size=574 timeout=0
exec /usr/exim/bin/exim -C /usr/exim/exim_outgoing.conf -d=0xfff7577f -t
-oem -oi -f <> -E17mu5t-0003C8-00
Exim version 4.05 uid=531 gid=531 pid=14544 L=834cd8 D=fff7577f
Berkeley DB: Sleepycat Software: DB 2.4.14: (6/2/98)
changed uid/gid: -C, -D, -be or -bf forces real uid
uid=531 gid=531
auxiliary group list: <none>
exim: debugging permission denied
address_reply transport succeeded
search_tidyup called
address_reply transport returned DEFER for ><user1> <<user1>@<domain>>
added retry item for T:><user1> <<user1>@<domain>>:<user2>@<domain>:
errno=0 0 flags=0
post-process ><user1> <<user1>@<domain>> (1)
LOG: MAIN
== ><user1> <<user1>@<domain>> <<user2>@<domain>> R=userforward
T=address_reply defer (0): Failed to send message from address_reply
transport (1)
>>>>>>>>>>>>>>>>>> deliveries are done >>>>>>>>>>>>>>>>>>

changed uid/gid: post-delivery tidying
uid=42 gid=12
auxiliary group list: <none>
set_process_info: 14540 tidying up after delivering 17mu5t-0003C8-00
Processing retry items
Succeeded addresses:
<user2>@<domain>: no retry items
Failed addresses:
Deferred addresses:
><user1> <<user1>@<domain>>

locking /var/spool/exim/db/retry.lockfile
locked /var/spool/exim/db/retry.lockfile
opened hints database /var/spool/exim/db/retry: flags=42
address match: subject=>simon alman <<user1>@<domain>>:<user2>@<domain>
pattern=*
<domain> in "*"? yes (matched "*")
><user1> <<user1>@<domain>>:<user2>@<domain> in "*"? yes (matched "*")

retry for T:><user1> <<user1>@<domain>>:<user2>@<domain> = *
dbfn_read: key=T:><user1> <<user1>@<domain>>:<user2>@<domain>
Writing retry data for T:><user1> <<user1>@<domain>>:<user2>@<domain>
first failed=1031222575 last try=1031224141 next try=1031225041 expired=0
error 0 0: Failed to send message from address_reply transport (1)
dbfn_write: key=T:><user1> <<user1>@<domain>>:<user2>@<domain>
<user2>@<domain>: no retry items
end of retry processing
time on queue = 26m24s
warning counts: required 0 done 0
delivery deferred: update_spool=0 header_rewritten=0
end delivery of 17mu5t-0003C8-00
search_tidyup called
search_tidyup called
>>>>>>>>>>>>>>>>>> Exim pid=14540 terminating with rc=0 >>>>>>>>>>>>>>>>>>

---------------------------------------------------end of queue
log-------------------------------------------------









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


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


# 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 = chameleon: <domain>: *.<domain>: localhost
domainlist relay_to_domains =
hostlist relay_from_hosts = 127.0.0.1:192.168.100.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.


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


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

#####################################################################
#                        MAILMAN                                    #
#####################################################################
# Mailman


## Home dir for mailman
MAILMAN_HOME=/home/mailman
# wrapper script for mailman
MAILMAN_WRAP=MAILMAN_HOME/mail/wrapper
# user and group for mailman
MAILMAN_UID=mailman
MAILMAN_GID=mailman

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

   deny    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


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




######################################################################
#                      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. 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 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
data = ${lookup{$local_part}lsearch{/etc/aliases_$domain}}
user = exim
allow_fail
allow_defer
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", 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.

# Vacation Router
user_vacation:
   driver = accept
   check_local_user
   require_files = $local_part:$home/tripnote
   no_verify
   senders = !^.*-request@.* : !^owner-.*@.* : !^postmaster@.* : \
             ! ^listmaster@.* : !^mailer-daemon@.*
   transport = vacation_reply
   unseen


# UserForward check

userforward:
driver = redirect
allow_filter
check_local_user
file = $home/.forward
file_transport = address_file
pipe_transport = address_pipe
reply_transport = address_reply
no_verify
no_expn
directory_transport = address_directory
skip_syntax_errors
syntax_errors_to = $local_part@$domain
syntax_errors_text = \
This is an automatically generated message. An error has\n\
been found in your .forward file. Details of the error are\n\
reported below. While this error persists, you will receive\n\
a copy of this message for every message that is addressed\n\
to you. If your .forward file is a filter file, or if it is\n\
a non-filter file containing no valid forwarding addresses,\n\
a copy of each incoming message will be put in your normal\n\
mailbox. If a non-filter file contains at least one valid\n\
forwarding address, forwarding to the valid addresses will\n\
happen, and those will be the only deliveries that occur.

#Mailman
# Mailman
## First 2 directors rewrite list-owner or owner-list to list-admin
## This is only done if the list exists.
## List existence checks are done by seeing if the file
## MAILMAN_HOME/lists//config.db
## exists.

list_owner_director:
driver = redirect
allow_defer
allow_fail
data = "${local_part}-admin@${domain}"
local_part_suffix = "-owner"
require_files = MAILMAN_HOME/lists/$local_part/config.db
retry_use_local_part

owner_list_director:
driver = redirect
allow_defer
allow_fail
data = "${local_part}-admin@${domain}"
local_part_prefix = "owner-"
require_files = MAILMAN_HOME/lists/$local_part/config.db
retry_use_local_part

##
## Next 3 directors direct admin, request and list mail to the appropriate
## transport. List existence is checked as above.

list_admin_director:
driver = accept
local_part_suffix = -admin
require_files = MAILMAN_HOME/lists/$local_part/config.db
retry_use_local_part
transport = list_admin_transport

list_request_director:
driver = accept
local_part_suffix = -request
require_files = MAILMAN_HOME/lists/$local_part/config.db
retry_use_local_part
transport = list_request_transport

list_director:
driver = accept
require_files = MAILMAN_HOME/lists/$local_part/config.db
retry_use_local_part
transport = list_transport

# This router matches virtual_users.forward files
Virtual_userforward:
driver = redirect
allow_filter
domains = +local_domains
user = vmail
local_parts = lsearch:/etc/virtual_users
file =/home/vmail/domains/$domain/$local_part/.forward
no_verify
no_expn
check_ancestor
#allow_filter
file_transport = address_file
pipe_transport = address_pipe
reply_transport = address_reply
directory_transport = address_directory
skip_syntax_errors
syntax_errors_to = $local_part@$domain
syntax_errors_text = \
This is an automatically generated message. An error has\n\
been found in your .forward file. Details of the error are\n\
reported below. While this error persists, you will receive\n\
a copy of this message for every message that is addressed\n\
to you. If your .forward file is a filter file, or if it is\n\
a non-filter file containing no valid forwarding addresses,\n\
a copy of each incoming message will be put in your normal\n\
mailbox. If a non-filter file contains at least one valid\n\
forwarding address, forwarding to the valid addresses will\n\
happen, and those will be the only deliveries that occur.

# This router matches virtual_users mailboxes
# also add a record *: postmaster@<domain> for all unresolved local addresses.

virtual_user:
driver = accept
domains = +local_domains
local_parts = lsearch:/etc/virtual_users_$domain
transport = virtual_localuserdelivery

# This router matches local_user mailboxes.
#*** only problem I can see with this is that the username is matched
regardless of domain for system users***
#not sure what the best option is for this at the moment#

localuser:
driver = accept
check_local_user
transport = local_delivery

#this final router does a final check for local users matching - if none exist
#then it will send the mail to whoever is configured as * in the relevant alias
#file

virtual:
      driver = redirect
      data = postmaster@$domain


# if the domain doesnt have a postmaster entry then the final stop is a
gerneral scan for a postmater in all the alias files.
# an e.mail is then sent to that postmaster.
unknown:
      driver = redirect
      data = postmaster
      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

# This transport is used for delivering messages over SMTP connections.

remote_smtp:
driver = smtp

# TRANSPORT
vacation_reply:
driver = autoreply
file = $home/tripnote
file_expand
log = $home/tripnote.log
once = $home/tripnote.db
from = vacation@???
to = $sender_address
subject = "Re: $h_subject"
text = "\
Dear $h_from:\n\n\
This is an automatic reply. Feel free to send additional\n\
mail, as only this one notice will be generated. The following\n\
is a prerecorded message, sent for $local_part@???:\n\
====================================================\n\n\
"

#This transport is for virtual user delivery prior to local delivery

virtual_localuserdelivery:
     driver = appendfile
     user=vmail
     maildir_format
     directory = /home/vmail/domains/$domain/$local_part
     create_directory
     delivery_date_add
     envelope_to_add
     return_path_add
   # group = mail
# mode = 0660


# 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
maildir_format
directory = /home/$local_part/Maildir
create_directory
delivery_date_add
envelope_to_add
return_path_add
# group = exim
# mode = 0660

#Mailman Transports
# Mailman
list_transport:
driver = pipe
command = MAILMAN_WRAP post ${lc:$local_part}
current_directory = MAILMAN_HOME
group = MAILMAN_GID
home_directory = MAILMAN_HOME
user = MAILMAN_UID

list_request_transport:
driver = pipe
command = MAILMAN_WRAP mailcmd ${lc:$local_part}
current_directory = MAILMAN_HOME
group = MAILMAN_GID
home_directory = MAILMAN_HOME
user = MAILMAN_UID

list_admin_transport:
driver = pipe
command = MAILMAN_WRAP mailowner ${lc:$local_part}
current_directory = MAILMAN_HOME
group = MAILMAN_GID
home_directory = MAILMAN_HOME
user = MAILMAN_UID

# 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 deliveries to directories that are
# generated by aliasing or forwarding.
#
address_directory:
driver = appendfile
maildir_format
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


# End of Exim configuration file
--------------------------------------------------end of
exim.conf---------------------------------------------

At 12:40 05/09/2002 +0100, you wrote:
>--
>Hi all
>
>I'm using exim 4.05 and have been trying to get the mail and vacation
>functions to work via users filters .
>
>Using the following .forward file:
>
>---------------------------------------------
>#Exim filter
>
>if error_message then finish endif
>
>save $home/Backup/
>deliver $local_part
>
>mail
>to $reply_address
>subject "<VACATION> Re: $h_subject:"
>expand file .vacation.msg
>return message
>---------------------------------------------
>
>Using the above filter when a user receives email I would expect a reply
>message to be sent out with the correct subject and body.
>However this is not happening and I am at a loss as to why, a reply message
>is being generated but it is failing to deliver and getting stuck in the
>queue instead. I have attached the forced delivery information <queue.log>
>which gives the error shown in the subject line. I have also attached my
>exim config for completeness.
>
>Finally failing the above, I tried using the config outlined in C006 to try
>and get vacation messages to work. Using the config exactly as specified I
>still get:
>"Failed to send message from address_reply transport error"
>
>Any help/advice on how to get mail and vacation to work, as well as
>information on the above error Re: address_reply transport, would be
>gratefully appreciated.
>
>Regards
>
>Simon Alman
>--
>[ exim.conf of type application/octet-stream deleted ]
>--
>[ queue.log of type application/octet-stream deleted ]
>--
>
>
>--
>
>## List details at http://www.exim.org/mailman/listinfo/exim-users Exim
>details at http://www.exim.org/ ##