On Fri, Jul 08, 2011 at 10:19:14PM +0200, Jeroen Geilman wrote:
>> Just don't return any result for lookup key.
>>
>
>
> Didn't the OP say that that produced a warning ?
No, what produced a warning, was returning a restring name that expands
to an empty list. Instead, the lookup key should not be
Dear Jeroen, Dear Viktor,
If I put "grey0 = dunno", when this value is used, Postfix return a
Warning on le logfiles.
The rules from Viktor work "grey0 = check_client_access static:dunno" work.
Postfix understand the value and don't give a warning on the logfiles.
With my other script and the pr
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:
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 st
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
grey1 = check_policy_service inet:127.0.0.1:10023
I use it because the user can select wich greylist or not.
I make a request into MyS
Dear Jeroen,
On the main.cf I've this two lines:
grey0 = check_policy_service unix:private/dunnopl
grey1 = check_policy_service inet:127.0.0.1:10023
I use it because the user can select wich greylist or not.
I make a request into MySQL, if the user have enable postgrey, MySQL
return grey1, if po
On 2011-07-08 17:54, Damien Robinet wrote:
Sorry for the debug, I've think (bad think) that can help for find the reason.
That is for example my dunno.pl script:
http://pastebin.com/cCQp1Few
It's hard to understand why this perl script need more than 3600 sec...
It must just reply "dunno" at p
Sorry for the debug, I've think (bad think) that can help for find the reason.
That is for example my dunno.pl script:
http://pastebin.com/cCQp1Few
It's hard to understand why this perl script need more than 3600 sec...
It must just reply "dunno" at postfix when they call the perl script ...
And
Damien Robinet:
> Dear Wietse,
>
> I'm sorry, but I'm not sure to have all understand.
> After you reply with the link
> http://www.postfix.org/SMTPD_POLICY_README.html#client_config
>
> I've add on my main.cf this 2 lines with my policy name.
>
> sendercheck_time_limit = 3600
> dunnopl_time_lim
Dear Wietse,
I'm sorry, but I'm not sure to have all understand.
After you reply with the link
http://www.postfix.org/SMTPD_POLICY_README.html#client_config
I've add on my main.cf this 2 lines with my policy name.
sendercheck_time_limit = 3600
dunnopl_time_limit = 3600
But the error have contin
Damien Robinet:
> Dear Wietse,
>
> Thank again for your reply.
>
> I've make the change on the master.cf and the main.cf.
> After restarted postfix, I've fewer errors.
>
> I've add this line in my main.cf:
> debugger_command = /usr/bin/strace -p $process_id -o
> /tmp/smtpd.$process_id & sleep 5
Dear Wietse,
Thank again for your reply.
I've make the change on the master.cf and the main.cf.
After restarted postfix, I've fewer errors.
I've add this line in my main.cf:
debugger_command = /usr/bin/strace -p $process_id -o
/tmp/smtpd.$process_id & sleep 5
And updated my master.cf with that:
/etc/postfix/master.cf:
sendercheck unix - n n - - spawn
user=nobody argv=/etc/postfix/policy/sender_check.pl
http://www.postfix.org/SMTPD_POLICY_README.html#client_config says:
To create a policy service that listens on a UNIX-domain socket
called "pol
Hi Wietse,
Sorry I've forgot my main.cf, you can find it here:
http://pastebin.com/Ydt0Xqtp
And the master.cf:
http://pastebin.com/G0MW6rZw
Bests Regards,
Damien
2011/7/7 Wietse Venema :
> Damien Robinet:
>> Hi Wietse,
>>
>> Thank for your reply, I've add this line "my_service_time_limit =
>>
Damien Robinet:
> Hi Wietse,
>
> Thank for your reply, I've add this line "my_service_time_limit =
> 3600" but I've alway the trouble ...
>
> Jul 7 18:18:48 mx02 postfix/spawn[19801]: warning:
> /etc/postfix/policy/dunno.pl: process id 19802: command time limit
> exceeded
> Jul 7 18:19:48 mx02
Hi Wietse,
Thank for your reply, I've add this line "my_service_time_limit =
3600" but I've alway the trouble ...
Jul 7 18:18:48 mx02 postfix/spawn[19801]: warning:
/etc/postfix/policy/dunno.pl: process id 19802: command time limit
exceeded
Jul 7 18:19:48 mx02 postfix/spawn[20189]: warning:
/et
Damien Robinet:
> Hi All,
>
> I need your help for a problem with Postfix.
>
> My postfix make several errors and I can not understand why.
>
> The error:
> Jul 7 17:16:42 mx02 postfix/spawn[9807]: warning:
> /etc/postfix/policy/sender_check.pl: process id 9812: command time
> limit exceeded
S
Hi All,
I need your help for a problem with Postfix.
My postfix make several errors and I can not understand why.
The error:
Jul 7 17:16:42 mx02 postfix/spawn[9807]: warning:
/etc/postfix/policy/sender_check.pl: process id 9812: command time
limit exceeded
Jul 7 17:16:42 mx02 postfix/spawn[981
18 matches
Mail list logo
