On Mon, 29 Nov 2004, Bevis R W King wrote:
> OK, that's useful - it has choosen to skip the userforward director for
> some reason... as in here:
>
> 9096 system_aliases router declined for brwk@???
> 9096 --------> userforward router <--------
> 9096 local_part=brwk domain=bevteccom.co.uk
> 9096 userforward router skipped: verify 2 0 0
> 9096 --------> localuser router <--------
That message indicates that this is happening during a verification, not
during a delivery. Let's take a look at your router:
userforward:
driver = redirect
check_local_user
# local_part_suffix = +* : -*
# local_part_suffix_optional
file = $home/.forward
allow_filter
directory_transport = local_delivery
no_verify
no_expn
check_ancestor
file_transport = address_file
pipe_transport = address_pipe
reply_transport = address_reply
Well, it has no_verify set. So it's doing exactly what it has been
configured to do; not run during a verification. The debug info you are
quoting is part of the verification that occurs when the message is
being received, not when it is being delivered. The reception process is
9096.
Let's take a look at your full log and see what it does for delivery.
This is further down the debug file, after the <= log line. This is
process 9097. I'm quoting only relevant lines here:
9097 recipients_count=1
9097 body_linecount=81 message_linecount=35
9097 Delivery address list:
9097 list-demodellers@???
There's just one address to deliver.
9097 routing list-demodellers@???
Start routing
9097 --------> dnslookup router <--------
...
9097 dnslookup router skipped: domains mismatch
As it says.
9097 --------> system_aliases router <--------
9097 local_part=list-demodellers domain=bevteccom.co.uk
9097 calling system_aliases router
...
9097 system_aliases router generated brwk@???
So the address was an alias, and we now have a new address
9097 routing brwk@???
Start routing the new address.
9097 --------> dnslookup router <--------
...
9097 dnslookup router skipped: domains mismatch
As it says.
9097 --------> system_aliases router <--------
9097 local_part=brwk domain=bevteccom.co.uk
...
9097 system_aliases router declined for brwk@???
This address is NOT an alias.
9097 --------> userforward router <--------
9097 local_part=brwk domain=bevteccom.co.uk
9097 checking for local user
9097 calling userforward router
... so it is running the router
9097 userforward router generated /home/gabrielle/users/brwk/.maildir/.Lists.Rail.DEModellers/
The filter ran and generated that address. Is that what you expect?
9097 After routing:
9097 Local deliveries:
9097 /home/gabrielle/users/brwk/.maildir/.Lists.Rail.DEModellers/
Confirms that the result of routing is to generate a single delivery to
that specific mailbox.
9097 >>>>>>>>>>>>>>>> Local deliveries >>>>>>>>>>>>>>>>
... which it then proceeds to do. I'm now confused. What is the problem
again?
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
