Brian Neu wrote: > THANK YOU!!!! > > I had already recompiled an RPM of postfix with postgres support. > > Also, I ended up configuring it differently, because I'm using virtual > domains for everything instead of local delivery. However, you > pointed me in the right direction. Here's what I did: > > main.cf: > virtual_mailbox_domains = proxy:pgsql:/etc/postfix/pgsql-v-mbox-domains.cf > virtual_mailbox_maps = proxy:pgsql:/etc/postfix/pgsql-v-mbox-maps.cf > > pgsql-v-mbox-maps.cf: > hosts = localhost > user = dbmail > password = **password** > dbname = dbmail > query = SELECT alias FROM dbmail_aliases where alias='%s'; > > I know that I should create a "read-only" user and put it in there, > but for now I'm happy to be saving my server from the attack. > > You know, every time that I've heard someone saying that "the world is > against" him or her, I've though that person was crazy. Today, > hundreds, if not thousands of different hosts from all over the world > were attacking my server, and I nearly joined the ranks of the insane. > > Thanks to everyone who contributes to dbmail. Yaknow it would probably be possible without too much difficulty to come up with some sort of setup that listed the IP of the failed SMTP connection and that could then be plugged into a firewall that would just drop packets from those IPs. After 2 minutes after it started all attacking IP's would be firewalled, bandwidth use would drop to basically nothing, but Valid connections would still get through. Obviously you would only deploy that system in a ddos situation but still. It takes you from a "service" attack, where they try to break your system by overloading a service, to just a bandwidth problem.
_______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
