On Mon, 11 Jan 1999, Marc Haber wrote:
> receiver_verify is not set on my system because it causes the address
> to be verified during the SMTP dialog.
Aarrgghh! That is what I thought we were talking about. I wrote:
> >> >(2) Verification applies only to incoming SMTP mail.
> This does a MX lookup which in
> turn causes my system to dial in to my ISP - something that is
> definetely to be avoided. receiver_try_verify does the same - MX
> lookup during SMTP dialog.
If you want to verify incoming addresses, and the verification requires
an MX lookup, then you have to do an MX lookup.
> I'd be perfectly satisfied if verification would happen during the
> queue run.
That's not "verification" in the sense Exim uses it. "Verification" *is*
checking the incoming addresses during the SMTP dialogue. Anything else
that is routing or directing.
Now, I think I understand what you are really trying to do. You don't
want verification. What you want is to do an MX-etc. routing on an
address, and if that fails, to fail the address. If it succeeds, you
don't actually want to send to the hosts you have found, but instead
send to the smart host.
I cannot see how to do that easily, because if you supply a "hosts" list
to an smtp transport, it is used only if the address has no hosts with
it. What you want is a way for the transport's host list to override the
hosts looked up by lookuphost. Have you considered using fallback_hosts
as a compromise, incidentally? That would send to your smart host only
if it couldn't immediately send to the MX host.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
