[Mimedefang] nonblocking md_check_against_smtp_server

Dirk Mueller dmuell at gmx.net
Mon Jan 27 22:57:01 EST 2003


Hi, 

how difficult would it be to make above time out if the server cannot be 
reached or is too slow to answer in time?

Or is the recommended fallback behaviour to make the whole filter just 
timeout and sendmail then tempfail the connection? Is a nice policy as well. 

BTW, is there a way to tell mimedefang-multiplexor to not start a new child 
when less than x MB of memory is free?

Because I had a case today where the mailgate was death-swapping because on 
of the internal mail servers locked up and so many mimedefang processes 
stuck in md_check_against_smpt_server() that all the memory was exhausted..

I guess my fault was that my rough guess of "max concurrent sendmail 
processes limit" in sendmail was too high, but its difficult to guess as the 
memory consumption varies a lot. 


-- 
Dirk (received 162 mails today)



More information about the MIMEDefang mailing list