Apparently, though unproven, at 03:22 on Monday 24 January 2011, kashani did opine thusly:
> > There's lots more examples, but they all follow a similar theme. > > Thanks for the extra detail, I found what you're describing very > interesting. I've never dealt with Postfix with more than a couple > hundred internal users and more often as spam our customers system. > Other than the occasional Nagios blasts I haven't had to deal with much > of this. > In regards to controlling what users send is it feasible to use a > policy server for rate limiting them? The ability to use an extra lookup > service to decide whether to access main, filter it, allow relay, etc is > one of the things I think Postfix does well. However I suspect the > management and hand holding of a rate limit system would create more > overhead than cleaning out the queue periodically. Your last sentence is the right one. Dealing with issues arising only when they arise is infinitely easier than trying to maintain some arb list of $STUFF just in case a minority of users misconfigure their boxes. On the whole, our users send only valid mail and all of it must be allowed to pass. The problems come in when a automated system mail goes beserk, usually causing loops. Not spam though, there's a rather large Cisco Ironport in front of my MTAs which deals with that. -- alan dot mckinnon at gmail dot com
