Milter-greylist

Reschauzier wrote on Thu, 22 Jan 2009 14:26:33 -0000:

> A single database server will be able to handle a significant number
> of single domain mx servers.

There is no such thing as a "single domain mx server". I assume you mean a 
server cluster that handles mail for one company? And further assume that 
a single company has only a small number of domains to handle mail for?
Why do you think that needs less ressources than a "multi-domain" (dozens 
or hundreds of domains) server? And how do you know that a single MySQL 
server will handle this without throttling the processing rate on the 
multiple mail servers?

I'm not saying that you are wrong. I and others just caution that there 
*might* be problems performancewise which in the end might greatly reduce 
the deployment figures of such a solution. So much that it may be not 
worth it to add such an API.

If that is not enough, the next step up
> will be a high performance, high availability database cluster.

You can do that. But think about that. What do you gain with this? I think 
you gain very little but invest a lot of hardware and personell 
ressources. I think most vendors are unlikely going to do that.

Kai

-- 
Kai Sch\ufffdtzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com