Xavier Beaudouin wrote: > Hi, > > >>> How many concurrent smtpd processes do you have on your MX? >>> >>> >>> >> Up to 1.5k per MX in peak during bot attacks. >> > > Hum. Anvil on postfix is a very good idea to avoid too mutch ressources > utilization. > > /Xavier > >
But anvil will still only work on a single SMTP gateway as far as monitoring aggregate email flow-- and as I see it, anvil is a "backup" in case for some reason policyd doesn't kick in early enough, at least, thats the way we have it configured -- it's also a good idea to have it in place in case for some reason connections to the DB fail, so mail continues to flow but anvil can still deal with the most egregious email floods. I can see anvil being ahead of policyd on a single server, but with several, you wnat to limit connections early on, so unles you scale anvil to catch lower loads on all the processors, it seems to me that policyd is a better choice up front. Or is there disagreement here about what is more effective/efficient in a multi-SMTP gateway environment? ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
