| Main Archive Page > Month Archives > postfix-users archives |
Re: spawn give a command time limit exceeded
From: Jeroen Geilman <jeroen_at_nospam>Date: Fri Jul 08 2011 - 20:19:14 GMT
To: postfix-users@postfix.org
On 2011-07-08 20:30, Victor Duchovni wrote:
> On Fri, Jul 08, 2011 at 06:33:31PM +0200, Jeroen Geilman wrote:
>
>> On 2011-07-08 18:30, Damien Robinet wrote:
>>> Dear Jeroen,
>>>
>>> On the main.cf I've this two lines:
>>>
>>> grey0 = check_policy_service unix:private/dunnopl
>> grey0 = dunno
> No, one can use:
>
> grey0 = check_client_access static:dunno
>
> Since access(5) built-in keywords are not always valid restrictions
> in their own right.
>
> But this is really silly, it is far better to just not return any
> value for the lookup key in question, the default is "dunno" when
> the table returns nothing.
>
>>> I make a request into MySQL, if the user have enable postgrey, MySQL
>>> return grey1, if postgrey is disable mysql return grey0.
> Just don't return any result for lookup key.
>
Didn't the OP say that that produced a warning ?
We haven't seen said warning, of course - it could be that he means
postfix complains when a /policy script/ produces no output.
-- J.