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 for later delivery.
In other cases, proper behaviour may means that the system complains it does
not know your user. I do not know.
Now that I think about it, that could be the problem I am having. When using
IMP-Courier imap-vpopmail some of my users need to login many times. It
could be that, because of the problem, authentication fails and they have to
> 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 succeeded, it was considering that the server was fine but that the
> > DB was not created.
> > Apparently, under some load, it could happen that the first request would
> > fail, but the second would be accepted...
> > All the patch does is make the code connect to the server first and then
> > use the Database. If the first call fails, the delivery fails (temporary
> > failure) and the message is delivered later.
> > Cheers,
> > François
> Thanks for the explanation, François :)
> I was having this problem, not only when delivering messages, but specially
> when checking POP3 mail (vchkpw). Will that be fixed too? Or am I going to
> get a different error? Also, using Antonio Nati's qmail-smtpd-chkusr patch
> (as in http://www.interazioni.it/qmail/qmail-smtpd-chkusr-10.html), what
> will be the effect with the new corrected mysql patch? I was getting some
> "no such user" errors before...