Prev: timeout problem on inbound and outbound SMTP
Next: postfix multi-instances and qmail co-existence
From: Vladimir Vassiliev on 4 May 2010 02:44
I'm curious about how does parameter <policy>_time_limit work.
Docs say it's time after which command is terminated but really it doesn't.

tst_pol_time_limit = 20
policy tst_pol defined in master.cf using spawn.

Log shows that policy command was terminated only in 8 minutes after warning "command time limit
exceeded".

May 4 10:29:19 localhost postfix/smtpd[3433]: connect from localhost.localdomain[127.0.0.1]
May 4 10:29:19 localhost policy.py: start
May 4 10:29:39 localhost postfix/spawn[3435]: warning: /home/vova/misc/policy.py: process id 3436:
command time limit exceeded
May 4 10:30:59 localhost postfix/smtpd[3433]: warning: problem talking to server private/tst_pol:
Connection timed out
May 4 10:31:00 localhost policy.py: start
May 4 10:31:20 localhost postfix/spawn[3447]: warning: /home/vova/misc/policy.py: process id 3448:
command time limit exceeded
May 4 10:32:22 localhost postfix/spawn[3232]: warning: command /home/vova/misc/policy.py exit status 1
May 4 10:32:40 localhost postfix/smtpd[3433]: warning: problem talking to server private/tst_pol:
Connection timed out
May 4 10:32:40 localhost postfix/smtpd[3433]: NOQUEUE: reject: RCPT from
localhost.localdomain[127.0.0.1]: 451 4.3.5 Server configuration problem; from=<vova(a)localhost>
to=<vova(a)localhost> proto=SMTP helo=<a>
May 4 10:32:40 localhost postfix/smtpd[3433]: disconnect from localhost.localdomain[127.0.0.1]
May 4 10:37:39 localhost postfix/spawn[3435]: warning: command /home/vova/misc/policy.py exit status 1
May 4 10:39:20 localhost postfix/spawn[3447]: warning: command /home/vova/misc/policy.py exit status 1

--
Vladimir Vassiliev

 | 
Pages: 1
Prev: timeout problem on inbound and outbound SMTP
Next: postfix multi-instances and qmail co-existence