Chris Mauritz wrote:
Christopher Chan wrote:
I don't recall ever having a problem with postgresql.
I guess the latest versions are more crash resilient. But still no
builtin replication.
This has gotten far afield of CentOS, but recent vintages of Postgresql
DO support replication. :)
h
Christopher Chan wrote:
I don't recall ever having a problem with postgresql.
I guess the latest versions are more crash resilient. But still no
builtin replication.
This has gotten far afield of CentOS, but recent vintages of Postgresql
DO support replication. :)
http://www.postgresql.o
Les Mikesell wrote:
Christopher Chan wrote:
Heck, I see lots of circles where they wouldn't trust mysql for an
enterprise application so it seems clear that you are not talking about
stability or performance but rather familiarity and the amount of trust
you have in what you know.
Let's see,
Christopher Chan wrote:
Heck, I see lots of circles where they wouldn't trust mysql for an
enterprise application so it seems clear that you are not talking about
stability or performance but rather familiarity and the amount of trust
you have in what you know.
Let's see, mysql crashes (elche
Yeah, well, I guess the Fedora Directory server is unlikely to drop
its entire datastore and will actually keep running but hey, are you
going to migrate back to ldap if you have a system that is distributed
across different mysql boxes running on cheap boxes and does its job?
Yes, I've had
Heck, I see lots of circles where they wouldn't trust mysql for an
enterprise application so it seems clear that you are not talking about
stability or performance but rather familiarity and the amount of trust
you have in what you know.
Let's see, mysql crashes (elcheapo hardware, happens onc
On Thu, 2007-10-25 at 10:30 +0800, Christopher Chan wrote:
> Craig White wrote:
> > On Thu, 2007-10-25 at 09:58 +0800, Christopher Chan wrote:
> >> Les Mikesell wrote:
> >>> Christopher Chan wrote:
> >>>
> >>> I thought the usual ways of doing this were to either use a
> >>> high-performan
Craig White wrote:
On Thu, 2007-10-25 at 09:58 +0800, Christopher Chan wrote:
Les Mikesell wrote:
Christopher Chan wrote:
I thought the usual ways of doing this were to either use a
high-performance NFS server (netapp filer...) and maildir format so
you can run imap from any client facing se
Christopher Chan wrote:
The service provider I used to work for tried openldap in 98. They
got burned big time. Maybe it is up to the task today. What kind of
hardware, though, would you use for one that the OP indicates will
get a lot of writes? Everything I have read says LDAP is not for hi
On Thu, 2007-10-25 at 09:58 +0800, Christopher Chan wrote:
> Les Mikesell wrote:
> > Christopher Chan wrote:
> >
> > I thought the usual ways of doing this were to either use a
> > high-performance NFS server (netapp filer...) and maildir format so
> > you can run imap from any clien
Les Mikesell wrote:
Christopher Chan wrote:
I thought the usual ways of doing this were to either use a
high-performance NFS server (netapp filer...) and maildir format so
you can run imap from any client facing server, or to keep the
delivery host information in an LDAP attribute that you fi
Christopher Chan wrote:
I thought the usual ways of doing this were to either use a
high-performance NFS server (netapp filer...) and maildir format so
you can run imap from any client facing server, or to keep the
delivery host information in an LDAP attribute that you find when
validating t
Les Mikesell wrote:
Christopher Chan wrote:
I thought the usual ways of doing this were to either use a
high-performance NFS server (netapp filer...) and maildir format so
you can run imap from any client facing server, or to keep the
delivery host information in an LDAP attribute that you f
On Thu, 2007-10-25 at 02:26 +0800, Christopher Chan wrote:
> Craig White wrote:
> > On Wed, 2007-10-24 at 21:21 +0800, Christopher Chan wrote:
> >>> I thought the usual ways of doing this were to either use a
> >>> high-performance NFS server (netapp filer...) and maildir format so you
> >>> can
Craig White wrote:
On Wed, 2007-10-24 at 21:21 +0800, Christopher Chan wrote:
I thought the usual ways of doing this were to either use a
high-performance NFS server (netapp filer...) and maildir format so you
can run imap from any client facing server, or to keep the delivery host
information
On Wed, 2007-10-24 at 21:21 +0800, Christopher Chan wrote:
> > I thought the usual ways of doing this were to either use a
> > high-performance NFS server (netapp filer...) and maildir format so you
> > can run imap from any client facing server, or to keep the delivery host
> > information in a
Christopher Chan wrote:
I thought the usual ways of doing this were to either use a
high-performance NFS server (netapp filer...) and maildir format so
you can run imap from any client facing server, or to keep the
delivery host information in an LDAP attribute that you find when
validating
I thought the usual ways of doing this were to either use a
high-performance NFS server (netapp filer...) and maildir format so you
can run imap from any client facing server, or to keep the delivery host
information in an LDAP attribute that you find when validating the address.
This is t
Matt Shields wrote:
I'm trying to set up a large scale email system that supports 100,000+
IMAP accounts. We have an existing frontend web interface that does a
lookup on a mysql db to figure out which IMAP server to connect to for
each user. For the email infrastructure we have decided on Post
Matt Shields wrote:
> Because of the way that the infrastructure is (biz reasons) we are not
> doing shared storage, we have numerous IMAP servers that we distribute
> accounts across. As we add more users, we image up a new IMAP server.
> For our business's scaling purposes this was the best pla
mouss wrote:
> Matt Shields wrote:
>> I'm trying to set up a large scale email system that supports 100,000+
>> IMAP accounts. We have an existing frontend web interface that does a
>> lookup on a mysql db to figure out which IMAP server to connect to for
>> each user. For the email infrastructur
Matt Shields wrote:
> I'm trying to set up a large scale email system that supports 100,000+
> IMAP accounts. We have an existing frontend web interface that does a
> lookup on a mysql db to figure out which IMAP server to connect to for
> each user. For the email infrastructure we have decided o
What I am having a problem is how do I get postfix to transfer the
email to the particular IMAP server that the user account is on. I
know that I need to use lmtp and transport, but all the examples I
have seen show forwarding all email to 1 IMAP server. I would like
Postfix to do a lookup for
I'm trying to set up a large scale email system that supports 100,000+
IMAP accounts. We have an existing frontend web interface that does a
lookup on a mysql db to figure out which IMAP server to connect to for
each user. For the email infrastructure we have decided on Postfix
and Cyrus. We hav
24 matches
Mail list logo
