On Mon, 21 Oct 2002, Peter A. Savitch wrote:
> Can somebody tell me, if I use the errors_to option, how can I re-make
> bounce (empty sender) addresses ?
Sorry, I don't understand the question. Setting errors_to changes where
bouces are sent. Bounces always have an empty sender.
> The thing is that *real* bounces, routed by the errors_to-enabled
> logic, become non-bounces. How to avoid this?
Ah, I see what you are getting at.
> Is that possible:
> errors_to = ${if <some-cond> {special_error@???}{} }
That's not possible. Maybe it should be. I also think that forcing an
expansion failure should cause errors_to to be ignored - but that
doesn't currently happen. I have made a note about that.
> I noted that when my bounces are routed, my smart host rejects my dumb
> host with something like:
>
> no localpart in address after MAIL FROM: <@my.qualified.domain.org>
>
> I don't want Exim to qualify my addresses.
>
> What am I doing wrong?
Nothing. The feature you want just isn't there because I hadn't thought
about it.
However, you can work round the problem by using another feature of
errors_to. It uses the address you give it only if the address can
verify successfully. Otherwise, it quietly ignore is. So, if you use
something like
errors_to = ${if <some-cond> {special_error@???}{junk@???} }
it should do more or less what you want.
Philip
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
