From: Franco Gasperino (francogasperino.org)
Date: Sun May 01 2005 - 23:08:29 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, 2005-04-29 at 22:37 +1000, Rob Mueller wrote:
> > There may be setups were you could benefit from several DB connections
> > (heavy computations between DB requests, SMP setups, ...) but even with
> > millions mail/day, until now the load and latencies are negligible on
> > average systems for SQLgrey (it may change in the future and I might
> > very well switch to another Net::Server class then), depending on what
> > your policy service does this might apply to it too.
>
> The biggest problem in our case is potentially slow actions, specifically
> RBL queries, and to a lesser extent DB ones. The biggest problem with a
> single process/single thread solution is making all of these run
> asynchronously. It seems in a perl environment, POE is a good way to go, but
> there's a reasonable learning curve to get going there...
>
> I'd really prefer to write the logic in a straight forward blocking style,
> and then use a multiplexor to reduce the total number of processes required.
> the proxymap service lets me do this for map types in postfix, is there an
> equivalent for the attribute based policy service?
>
> Rob
>

  I have a set of python classes that handle a TCP policy service in
full non-blocking mode. From this foundation i've created both a
greylisting and SPF policy servers. Both have been in production for 8
months, handling roughly 5 million messages/day with virtually no
overhead.

  If you would like to have the code to extend (it's *real* easy to do),
let me know.

  Franco

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]