How can MailScanner "push back"?

Andrew MacLachlan andy.mac at global-domination.org
Thu Aug 23 22:50:27 IST 2007


> Actually, "he who shall not be named" provides a sample policy daemon
> with the postfix source.
> 


There is a much simpler solution (but I could also be confused...):
Main.cf
...
# INPUT RATE CONTROL
#
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
#
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
#
# Specify 0 to disable the feature. Valid delays are 0..10.
#
#in_flow_delay = 1s
...

-HTH, Andy


--
This message was scanned by ESVA and is believed to be clean.



More information about the MailScanner mailing list