Re: Mail server reboot after got flood

2 msg	2 postfix server on the same domain in differen...
3 msg	mailer-deamon sends error messages to: question
3 msg	Procmail
15 msg	MAIL FROM timeout with ciphers=high
2 msg	milter, broken pipe
17 msg	How to listen on 587 as well as 25?
6 msg	reject_sender_login_mismatch doesnt work
2 msg	smtp auth
4 msg	Postfix with MYSQL compile error
8 msg	mynetworks=<empty> vs mynetworks=<defa...
3 msg	message_size_limit with ldap search parameter
2 msg	Pipe debugging
12 msg	destination_concurrency_limit not respected ?
13 msg	Virtual spam forwarding issues
2 msg	cleaning up deferred queue
2 msg	static nexthop per domain
2 msg	Simple postmap question
9 msg	Issues with Recipient_Canonical mapping

Mail server reboot after got flood
\ - Cygnus - (29 Nov 2007)
. \ Robert Schetterer (29 Nov 2007)
. . \ - Cygnus - (29 Nov 2007)

3 msg	can't create a virtual domain

Subject:	Re: Mail server reboot after got flood
Group:	Postfix-users
From:	- Cygnus -
Date:	29 Nov 2007

Robert Schetterer wrote:
> Hi,(without looking to your conf)
> 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.
>
>

Actually I did reduce the smtpd_client_connection_count_limit and
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'