Hi Tim, Thanks for your response. I should have mentioned that this server is meant to be a hosting server for both web and mail, and there is no way to effectively restrict based on trusted clients.
Is there anything else perhaps more general for if not preventing, then deterring and slowing down this kind of attack? Thanks, Nick On Wed, 2008-01-30 at 10:56 -0500, Tim Evans wrote: > Nick Jennings wrote: > > > Luckily this machine is not in production yet and so I just shutdown > > the dovecot daemon. I was wondering if anyone could suggest any measures > > I can take to stop thing kind of thing happening? Also, what kinds of > > risks does this sort of an attack expose me to? Could it bring my server > > down or could they actually break in? > > 1. report the abuse to the provider; you have incoming the IP address. > > 2. Use tcp wrapper to secure dovecot, limiting access to known good > addresses. _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
