11 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Saturation DDoS
FromSent OnAttachments
Zenon PanoussisOct 22, 2007 5:50 am 
Enda CronnollyOct 22, 2007 6:25 am 
Leigh S. JonesOct 22, 2007 7:29 am 
Gordon MessmerOct 22, 2007 7:48 am 
Zenon PanoussisOct 22, 2007 8:25 am 
Gordon MessmerOct 22, 2007 9:50 am 
Zenon PanoussisOct 22, 2007 10:34 am 
Gordon MessmerOct 22, 2007 12:48 pm 
Sam VarshavchikOct 22, 2007 3:36 pm 
Zenon PanoussisOct 23, 2007 12:27 am 
DanielOct 23, 2007 11:29 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Saturation DDoSActions...
From:Enda Cronnolly (en@codefoundry.com)
Date:Oct 22, 2007 6:25:51 am
List:net.sourceforge.lists.courier-users

Zenon Panoussis wrote:

status=deferred (delivery temporarily suspended: connect to [my courier]: Connection refused)

I would hazard a guess that you have either ran out of pre-configured available threads for esmtpd to listen on (in which case increasing the limits will help) or your system has run out of available resources to provide esmtpd with new threads. Its the only logical reason why esmtpd can't answer requests.

Either way, since your enemy's response will be to increase the load to find your new break point, in my opinion, you need to consider clustering esmtpd, which isn't difficult if you have some spare hardware given the modular nature of courier. You'll get a load balancer project from freshmeat which you can run to delegate the esmtpd load across multiple servers. Perhaps scrambling a solution to show this guy that you've beaten him will cause him to backoff allowing you to put a more structured system in place.

Best of luck!

-Enda.