Re: Found a clue for (Postfix-Cyrus delivery bug)

2001-11-21 Thread Eranga Udesh
: Wednesday, November 21, 2001 8:14 PM Subject: Re: Found a clue for (Postfix-Cyrus delivery bug) > Quoting Eranga Udesh <[EMAIL PROTECTED]>: > > > Hi All, > > > > With the test I conducted lately I found that notification process causes > > this problem. In m

Re: Found a clue for (Postfix-Cyrus delivery bug)

2001-11-21 Thread Ken Murchison
Quoting Eranga Udesh <[EMAIL PROTECTED]>: > Hi All, > > With the test I conducted lately I found that notification process causes > this problem. In my setup I'm using unix domain socket notification. For the > socket I'm using a domain socket created by Postfix which spawns a program > written

Re: Found a clue for (Postfix-Cyrus delivery bug)

2001-11-21 Thread Nuno Silva
hi, you must be reading 2000 (or so) bytes from the socket and then closing it. Try to read the data until you have an EOF from the sender and only then closing/exiting the script. ...another wild guess :) regards, nuno silva Eranga Udesh wrote: > Hi All, > > With the test I conducted lat

Found a clue for (Postfix-Cyrus delivery bug)

2001-11-21 Thread Eranga Udesh
Hi All, With the test I conducted lately I found that notification process causes this problem. In my setup I'm using unix domain socket notification. For the socket I'm using a domain socket created by Postfix which spawns a program written in PHP. (This setup I used because it's not possible wr

Found a clue for (Postfix-Cyrus delivery bug)

2001-11-21 Thread Eranga Udesh
Hi All,   With the test I conducted lately I found that notification process causes this problem. In my setup I'm using unix domain socket notification. For the socket I'm using a domain socket created by Postfix which spawns a program written in PHP. (This setup I used because it's not poss