Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Wietse Venema (wietseporcupine.org)
Date: Sat Sep 12 2009 - 07:05:54 CDT
Egoitz Aurrekoetxea Aurre:
> I'm pretty sure about this but... I prefer asking for being totally
> sure. Hey mates imagine a policy daemon has a (server time limit) time
> limit of 3600 seconds... like hasn't arrived the max_idle time...
> spawn doesn't close it.... and now it's near to it's time_limit....
> imagine that in 120 seconds arrives the configured time_limit for the
> policy (the 3600 seconds)... Now and smtpd proccess connects to it and
> it's going to accept a big mail over a slow inet connection... so it's
When you are running the policy service under the spawn daemon:
1) The time limit BEGINS after an SMTP server connects to the
policy server port, when a new policy daemon process is created.
Thus, an SMTP server always "mates" with a policy server that
has the full time limit left.
2) The time limit ENDS after an SMTP server process disconnects,
because the policy daemon terminates immediately.
If you still think the time limit is too short, make it longer.
> going to take perhaps 600 seconds to receive the mail.... is the
> policy daemon closed by spawn when that 120 seconds arrive and then
> smtpd proccess will retry to connect again to a new available (not
> linked by any smtpd proccess) or just new spawed policy daemon or does
> spawn wait till smtpd proccess ends with policy daemon althouhg the
> 120 seconds have passed? or if the policy daemon doesn't never exit
> because enters in a loop (a good loop I mean accept parameters decide,
> accept parameter decide and so) it's still alive (doesn't die in those
> 120 seconds) till smtpd proccess dies for some reason (max_use or
> Thanks a lot mates.