On Mon, 24 Mar 2003, Philip Hazel wrote:
> I see the problem, but there is a difficulty. If I simply make it
> discard the message on any temporary routing error, it will discard a
> bounce message when the DNS server for the domain of the recipient
> happens to be down (for example). Unfortunately, there isn't a way of
> distinguishing between "expected" temporary routing errors such as DNS
> unavailable, and "unexpected" errors such as screwed up configurations.
> Indeed, I don't really think there should be.
I see your point. I was considering it only from my current situation. I
did find out what's causing this particular problem, though - a client w/
a groupwise server turns on vacation autoreplies and they are sent from
the address mailer-daemon@???. That address is 1) invalid
and 2) in no way within their rights to use. *sigh*
