Re: Mail server reboot after got flood
- Robert Schetterer wrote:
> Hi,(without looking to your conf)Actually I did reduce the smtpd_client_connection_count_limit and
> it looks like your Antispam Box is a transparent smtp Proxy
> and it does simply empty its queue full of notifications, so it may work
> as designed.
> Try to empty the spambox queue manually.
> You should configure some "bandwith" limit on postfix
> that you cant get rushed by your antispam as workaround.
> On the second place you should look at your antispambox for a better
> configure so there should not be thousends of notifies.
> After all with postfix you should have better choosen amavis
> for Antispam and not ugly spamboxes, which arent better in the most cases.
smtpd_client_connection_rate_limit values, but server still unable to
handle those traffic, and the problem was getting worse since legitimate
email also became delayed. But there is one thing that I suspect, before
I tuned sysctl configuration, the server still can handle the traffic,
but after I change the value of kern.maxfiles, kern.maxfilesperproc,
kern.ipc.somaxconn and net.inet.tcp.inflight.enable, after that server
got rebooted. Is there any chances I misconfigured those values?
- Cygnus -
'Veritas vos liberabit'