FW: [exim] one more condition

Grrrr. Didn't send to the list. Sorry Jeremy :)

--
C


> -----Original Message-----
> From: Chris Knipe [mailto:savage@savage.za.org]
> Sent: 20 December 2005 15:08
> To: 'Jeremy Harris'
> Subject: RE: [exim] one more condition
>
> > -----Original Message-----
> > From: exim-users-bounces@???
> > [mailto:exim-users-bounces@exim.org] On Behalf Of Jeremy Harris
> > Sent: 20 December 2005 14:48
> > To: exim-users @ exim. org
> > Subject: Re: [exim] one more condition
> >
> > Chris Knipe wrote:
> > > Basic idea... Verify recipient address from a mysql
> > database.... It's
> > > supposed to be for recipient address maps on domains I intend to
> > > *relay* mail for (and therefore, I believe I cannot use
> > verify = recipient)...
> >
> > That isn't so - a recipient verify, preferably with callout, will
> > work.
>
> I'm pretty sure if the primary MX is offline, the
> verification will fail (unable to connect to the MX for a
> callout, per example), and reject. This would also be worsen
> if the primary MX is down for a prolonged period of time
> (say, a couple of days).
>
> Looking at the verify = recipient section in the manual right now:
> - Initial verification is done through the router - which
> just ensures that the address is valid, and routable (thus, I
> do not have a verified address yet, the address can be
> non-existant, not exist on the primary MX, and get stuck in
> my queue as a frozen message)
> - If callout is specified, the successful verification is
> followed by a callout. This, will fail if the primary MX is
> offline, or unable to verify the recipient (which is all well
> as long as the primary MX actually is online and told me
> specifically that the address does not exist).
> - If I include defer_ok, the above scenario with the error
> when the MX is offline, will be resolved. BUT, then I still
> don't know whether or not the address exist, and I accepted
> the message. When the Primary MX gets back online, again, I
> attempt delivery, and the pri MX tunes me nooit china, I
> don't have such a user, and again, I'm stuck with the frozen
> message in my queue.
>
> Thus, for a secondary MX, verify = recipient is only accurate
> if the primary is online, or a local usermap of the domain in
> question is accessible (which is what I'm attempting now)...
>
> The problem here, is whether the primary MX is online or not,
> I need to verify the recipient, and accept the message. As
> long as the recipient is verified, I don't mind the message
> sitting in my queue for weeks. What I don't want however, is
> ending up with a queue full of frozen messages because the
> primary server rejects the recipients, or I accept the
> messages initially without proper verification.
>
> Hope it makes sense...
>
> --
> Chris.
>
>
> --
> C
>