Hi Peter, on Tue, 03 Feb 2004 13:50:19 +1300 you wrote:
[last-ditch router]
> We have tried the following router config but it doesn't make a match on
> anything for some reason.
Have you got some routers above with no_more set? I hope I get my
terminology right here, but if an address matches the conditions for a
router and the router has no_more set, the routing stops there - even if
the router declined the message. This might be why messages are never
reaching your router.
> ----------------transport snippet -------------------------
>
> non_exist_reply:
> driver = autoreply
> user = mail
> to = $sender_address
> subject = User does not exist
> text = You sent mail to $local_part. That's not a valid user here. \
> The subject was: $subject.
>
> ---------------------end snippet---------------------------
If I am correct in understanding what you're trying to do, please don't do
it this way. *Don't* generate bounce messages unnecessarily, as you will
cause "collateral spam" (consider the case of a spammer who sends mail
claiming to be from "victim@???" to an invalid address at your
domain - you will end up spamming victim@???).
Much better is to use the cannot_route_message option in your routers. For
example, in a router that has no_more set:
router_blah:
driver = whatever
domains = ....
...
cannot_route_message = That address is not valid here
no_more
That way, when you're dealing with incoming SMTP connections, the
recipients will be rejected at SMTP RCPT time with the given message, and
a bounce containing that message should be generated by the remote end (if
the remote end is a real mailserver and not a spammer).
Tim
