For what do you need pgpool? dbmail does already connection pooling
Proxy yes - but use something better maintained than imapproxy crashing for years if the client is using a obviously unsupported login mech
Just use dovecot which comes with a SASL provider for postfix too and also supports pop3 proxying
-------- Ursprüngliche Nachricht --------
Von: "Sandino Araico Sánchez" <sandino@sandino.net>
Gesendet: 11. November 2014 03:18:24 MEZ
An: DBMail mailinglist <dbmail@dbmail.org>, 'Paul J Stevens' <paul@nfg.nl>
Betreff: Re: [Dbmail] Re max_db_connections
On 02/11/14 15:40, Rogerio Pereira wrote:
>
>
>
> >> If you want to kill your postgres server that is a good idea :-)
>
>
> *My PostreSQL server is not an issue for me, until now.*
>
> *It has 2 Sixcore processors, 16 GB RAM, SAS 15k disks in RAID
> config. Processor usage is fine.*
>
> >> Seriously: DBMail has a kick-ass database pooling mechanism. If
> you need
> >> more than 10 database connections you are having problems of a
> different
> >> nature, or you are running a setup with hundreds if not
> thousands of
> >> *very* active users.
>
> *Running 100 imapd concurrent connections. Hope to get 400 in the
> near future.*
>
*You might consider using an IMAP proxy like *
http://www.imapproxy.org/ or nginx.
Another option is pooling database connections with PgPool so you keep a
fixed number of database connections independent of how many IMAP
clients you ar serving at a time.
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> DBmail mailing list
> DBmail@dbmail.org
> http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail