Norman Maurer wrote:
B. Maybe we should add an RcptHook that simply return HookRetCode.OK
if the user is authenticated, so that adding that check before all of
this handlers will already do the trick, and moving it up-down in the
chain will provide the "checkAuthUsers" behaviour to every handler.
Well i see some problems here. This will make it impossible to call a
hook for a auth user even if the user/developer want this. Maybe he want
to create a hook which only is used for authenticated RCPT. So this is
IMHO not the right solution. But i understand that it is annyoing to
have to configure it on every hook. Maybe thats the price we have to pay :-(
What I mean is add an RcptHook named AcceptRecipientIfRelayingIsAllowed
that will return HookRetCode.OK *IF* isRelayingAllowed and to remove the
isRelayingAllowed from any other rcptHook.
So if you add this hook sequence:
ValidRcptHandler
ResolvableEhloHeloHandler
AuthRequiredToRelayRcptHook
** AcceptRecipientIfRelayingIsAllowed
GreylistHandler
SPFHandler
DNSRBLHandler
This will means that the first 3 rcpthooks will check even clients
autorized to relay, while the last 3 rcpthooks will only check if the
sender is not allowed to relay.
Moving the "AcceptRecipientIfRelayingIsAllowed" up and down will do the
same trick as adding/removing the relayingAllowed check to every hook.
Does this solve the problem you pointed out? Or did I misunderstood your
question?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
