On Tue, 29 Jun 2004 08:34:30 +0700
François Wautier [EMAIL PROTECTED] wrote:
Hi,
The patch applies does not solve the underlying problem, the fact that you
cannot connect to the DB server. It just makes sure the system behaves properly
even when one cannot access the DB.
I see. You
Hi,
I see. You said, in your previous message:
The code in vpopmail was first trying to connect to the server for a given
database. If that was failing, it would try the server only and if that
succeeded, it was considering that the server was fine but that the DB was
not created.
So,
On Fri, 25 Jun 2004 18:17:53 -0700
Tom Collins [EMAIL PROTECTED] wrote:
http://vpopmail.sf.net
Release Notes:
There are significant changes in here for MySQL and Postgres backends.
If you've had errors stating couldn't create table/database because it
already exists with MySQL, you
Hi,
Since I submitted that patch.. I guess I should answer.
The code in vpopmail was first trying to connect to the server for a given
database. If that was failing, it would try the server only and if that
succeeded, it was considering that the server was fine but that the DB was
not
On Mon, 28 Jun 2004 21:54:55 +0700
François Wautier [EMAIL PROTECTED] wrote:
Hi,
Since I submitted that patch.. I guess I should answer.
The code in vpopmail was first trying to connect to the server for a given
database. If that was failing, it would try the server only and if that
Hi,
The patch applies does not solve the underlying problem, the fact that you
cannot connect to the DB server. It just makes sure the system behaves
properly even when one cannot access the DB.
In the case of email delivery, proper behaviour means that the message is put
back into the queue
http://vpopmail.sf.net
Release Notes:
There are significant changes in here for MySQL and Postgres backends.
If you had problems with Postgres and roaming users, you should
definitely upgrade.
If you've had errors stating couldn't create table/database because it
already exists with MySQL, you
