Re: [Exim] :fail: from a router

Quoting Lane Vance (lists@???):

> Sander - Thanks for the suggestions and ideas. I tried with the space after
> :fail: but it did not seem to make a difference.

That's why it was just an idea ;)
All my :fail: lines in my aliases files have a tab after the last :.

> In a router, is the message after :fail: only for logging purposes? If so,
> the cannot_route_message should do the trick, right?

In a router, the cannot_route_message is used whenever the router can't
route the message and it is the last router in the chain. And if
unspecified it takes the default which is something like 'Cannot route
address'. The last value of cannot_route_message is used in the return
message. So if you set that key to a value in the first router, and the
last one can't route it, the value set in the first router will be
shown.

> Could this simply be a problem with the remote mail server not reading the
> errors properly? I will have to test this if I can get my hands on another
> mail account.

You can also telnet to your own server on port 25 and do a 'hand
delivery' to that specific user to see what exim tells you.

> Anyone else using user defined white and blacklists?
> If so, how are you implementing them?

Shouldn't your blacklist be implemented in the RCPT TO-acl ?
It seems like a nicer place and saves you the bounces in your mailq.

Sander.
--
| Searching for lost relatives? Win the Lottery!
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8 9BDB D463 7E41 08CE C94D