On Thu, 20 Nov 1997, Andrew V. Kovalev wrote:
> if a user ivan on say, horse, has a .forward file containing:
>
> someone@???
> \ivan
>
> he expects to receive a copy of incoming mail at his mailbox on horse and
> another one copy sent to someone@???. But instead the second line
> of his .forward generates ivan@??? and the message is passed to
> tiger, where it is looked up in forwardtable again, sent back to horse ad
> infinitum. It seems that check_ancestor doesn't work when qualify_domain
> are not recognized as local domains. Looks like a bug to me.
How is the message forwarded from tiger to horse? Do you transform the
address into ivan@horse? In that case, the incoming address is
ivan@horse and so of course check_ancestor won't match when checking it
againsg ivan@???.
> Tiger also has director forwardtable
> forwardtable:
> driver = aliasfile;
> file = forwardtable,
> search_type = nis,
Does this turn ivan@??? into ivan@???? I'm guessing
it does, leading to check_ancestor not working as you expect.
Have you tried setting
qualify_recipient = horse.jet.msk.su
on horse? Then any unqualified recipient addresses on that system will
be treated as truly local, but since you have got
qualify_domain = jet.msk.su
the *sender* addresses will look like ivan@???.
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
*** Exim information can be found at
http://www.exim.org/ ***
