TCPwrappers after check_relay (access.db)

Hello all:

I know this may be beating a dead horse; Ive googled the
comp.mail.sendmail archives
about this, but I cant say I found a good explanation:

Why are the TCPwrappers called after access.db?

Maybe Im wrong, but it would seem to make more sense to kill the
connection
with the wrappers before checking access.db. I read that the cost
execute the code
for each is the same, but my access.db is MUCH bigger than my
hosts.allow/deny

Are there any plans to reverse the calling order, or is an option
already available?
(If it is already available I must have missed it in the archives).

(Im only running sendmail 8.14.1 for myself, not for others)

Thanks in advanced. Looking forward to answers, etc.
-- S.A. Birl

Re: TCPwrappers after check_relay (access.db)

On Nov 7, 11:53 am, "S.A. Birl" wrote:
> Hello all:
>
> I know this may be beating a dead horse; Ive googled the
> comp.mail.sendmail archives
> about this, but I cant say I found a good explanation:
>
> Why are the TCPwrappers called after access.db?
>
> Maybe Im wrong, but it would seem to make more sense to kill the
> connection
> with the wrappers before checking access.db. I read that the cost
> execute the code
> for each is the same, but my access.db is MUCH bigger than my
> hosts.allow/deny
>
> Are there any plans to reverse the calling order, or is an option
> already available?
> (If it is already available I must have missed it in the archives).
>
> (Im only running sendmail 8.14.1 for myself, not for others)
>
> Thanks in advanced. Looking forward to answers, etc.
> -- S.A. Birl


Wow, I REALLY didnt look in the archives too well!
Turns out I asked a similar question about 2 years ago.
Everyone can boo me now.