On Thu, Apr 29, 2004 at 11:11:53AM +0700, Frank Rabitsch wrote: > > > > > ----- Original Message ----- > > From: "Claudio Jeker" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Thursday, February 05, 2004 8:21 PM > > Subject: Re: QMQP problem > > > > ... > > > > > > If I do a flush on the sending side it starts up ten delivries at > once. > > Some > > > > of them return with the "communication_with_mail_server_failed" > message. > > On > > > > the receiving side I see that some of them end with status 28416 as > > above. > > > > Some of them simply end with status 0 however I don't get an OK > messages > > on > > > > the receiving side (e.g. ...ok 1075813267 qp 23974 ddc saved 43 > percent) > > for > > > > all of the ending connections with status 0. > > > > > > > > Let me know what could be the cause of this problem or how I should > > analyze > > > > the log-files. Thanks. > > > > > > > > > > Hmm. I will try to find out why qmail-qmqpd blocks after printing the OK > > > line. Seems very strange. > > > > Hi Claudio, > > Remember this thread about the communication problem in QMQP on slow WAN > connections? Anyway, I started analyzing the code of qmqpc and remote and I > noticed that qmqpc uses a read / write timeout of 60 secs and remote a > timeout of 1200 secs. I wrote a patch (below) to make the read / write > timeout configurable in a similar fashion as with remote in a control file > named "timeoutqmqpc" (for remote it is "timeoutremote"). Setting this > timeout to 1200 solved my problem and connection problems disappear. > > After applying the patch, default behavior of qmqpc stays the same. This > means that if the control/timeoutqmqpc does not exist, the timeout is still > 60 secs. I was wondering if you could add this patch to the distribution. It > might help some people in the future. >
Something like this is in the 20040401 release. -- :wq Claudio
