On Tue, 17 Dec 1996, John Henders wrote:
> After doing some more digging (literally) I've found that the problem
> here seems to be in this case attempting to get an MX record for
> ns.web2010.com leads to a timeout for some reason. From the SOA record
> returned for the domain it is probably a database config error. However,
> it would seem to me that if sender_verify_fixup is defined, then it
> might be a more preferable strategy to fall through to it rather than
> defering on the timed out MX lookup on the envelope From line. Is this
> possible? Would it be a good idea?
That doesn't seem an unreasonable idea. I will investigate to see how
easy it would be to implement.
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
