On Fri, 18 Oct 1996, Neal Becker wrote:
> I don't think I should need to know where the MX points for this rule
> to apply. It should apply to all machines that this MX points to. If
> the other admins add MXs or change them I shouldn't need to know.
Let me be sure I understand properly. You get a message addressed to
xxxx@??? and then you rewrite it as yyyy@??? and if
you get zzz@??? you rewrite as aaaa@??? and then
these rewritten domains get looked up as MXs?
> The tricky part is that the rule must apply to the address as I have
> rewritten it. Clearly, it can't apply to the address as I received
> it, since some of that mail I will redirect differently.
That already happens, as retries apply to delivery addresses.
> So, it looks to me that the retry rules should be matched to addresses
> after rewriting, but before MX. The reason is that I control
> rewriting, but others control their MX.
I am thinking (but not for the next release, which is just waiting for
documentation) of changing the way Exim works so that, if there isn't an
explicit retry rule for a host, then the retry rule that applies to
the MX that produced that host is used. This sounds as though it would
do what you want. For example, if a.com is an MX that points to b.com,
and delivery to b.com fails temporarily, then a retry rule that matches
b.com is used, if it exists; if not, a retry rule that matches a.com is
used.
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
