On Wed, 18 Sep 2002, Philip Hazel wrote:
> On Wed, 18 Sep 2002, Russell Wilton wrote:
>
> > >>A message that you sent could not be delivered to one or more of its
> > >>recipients. This is a permanent error. The following address(es) failed:
> > >>
> > >> test.user@???
> > >> SMTP error from remote mailer after RCPT TO:<test.user@???>:
> > >> host polaris.netsrv.uleth.ca [142.66.ccc.ddd]:
> > >> 550 unknown user
>
> Is your Exim host the one that generates the bounce message, or is it
> polaris.netsrv.uleth.ca?
Phil, it looks to me like its his host that has to generate the NDR,
since this looks like it was speaking SMTP to the remote host, and the
remote host did not accept the message at SMTP time, giving "550 unknown
user" as the response.
>
> > Maybe I didn't describe my problem adequately. Your answer would
> > address the inverse of my problem.
>
> Sorry, answering quickly sometimes has this kind of effect...
>
> > When a local user "A" sends mail to another local user "B", and "B" has
> > set an invalid forwarding address, "A" gets a bounce message saying that
> > "B" doesn't exist, with no mention of the bad forwarding address.
>
> I guess I need to know more about the hosts involved. In the example
> above, the control of the wording is with the polaris.netsrv.uleth.ca
> host. If it's an Exim 4 host, the wording will be in the ACL.
user1@hisdomain sends a message to user2@hisdomain. user2@hisdomain has
a .forward with nonexistantuser@???, which the remote
server rejects at SMTP time.
When his host sends the bounce to user1@hisdomain, he wants it to give
some indication that while user2@hisdomain is valid, a chile address
thereof is not.
I think he specifically wants to expose the fact that there was a
.forward which had an invalid address, as opposed to there being an
internal problem delivering locally to user2@hisdomain.
>
> > I
> > understand that hide_child_in_errmsg is supposed to prevent the
> > forwarding address from being displayed, but I don't have it set. So, I
> > expected the bad forward address to be displayed in the bounce message,
> > giving user "A" a chance of figuring out what's wrong. Instead, since
> > they know "B"s address is valid, they think the mail system is broken
> > and waste their and my time tracking down the problem.
>
> ... but it IS broken! (In some sense. :-)
>
> > Why is the bad forwarding address not mentioned in the bounce?
>
> > Do I
> > have something configured incorrectly or do I need to create a
> > customized bounce message? Thanks for your help.
>
> A customized bounce message isn't going to help you, because the text of
> the message is coming from a host that is remote to the one that creates
> the bounce message. The bounce creator doesn't know anything about the
> forwarding.
>
>
>
> --
> Philip Hazel University of Cambridge Computing Service,
> ph10@??? Cambridge, England. Phone: +44 1223 334714.
>
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
>
