Re: qpsmtpd-async: premature end of data problem

2008-04-13 Thread Ask Bjørn Hansen
On Apr 12, 2008, at 6:33, Radu Greab wrote: I found a case where qpsmtpd-async detects the end of data marker incorrectly: the previous packet did not end with CRLF and the current packet starts with .CRLF. The code assumes that the previous packet ended with CRLF. Hi Radu, Can you add it to

Re: qpsmtpd-async: premature end of data problem

2008-04-13 Thread Matt Sergeant
Ask Bjørn Hansen wrote: On Apr 12, 2008, at 6:33, Radu Greab wrote: I found a case where qpsmtpd-async detects the end of data marker incorrectly: the previous packet did not end with CRLF and the current packet starts with .CRLF. The code assumes that the previous packet ended with CRLF. Hi

Re: [qpsmtpd] forkserver --limit-connections issues

2008-04-13 Thread Charlie Brady
On Fri, 11 Apr 2008, R wrote: qpsmtpd has a long-standing problem that timeouts are not applied to plugins, only to core qpsmtpd code. Sounds like that would be a better solution, though. Might anyone be working on it? Not that I've observed.

Re: qpsmtpd-async: premature end of data problem

2008-04-13 Thread Radu Greab
Matt Sergeant wrote: > > Though I could have sworn I fixed this - are you sure you're testing > against latest SVN? Hi, I do not have the latest SVN in production. I have 0.43rc1 with additional patches, including your change #129 which, I think, is what you are referring to as having fixed th

Re: qpsmtpd-async: premature end of data problem

2008-04-13 Thread Radu Greab
Radu Greab wrote: > > > Matt Sergeant wrote: > > > > Though I could have sworn I fixed this - are you sure you're testing > > against latest SVN? > > I do not have the latest SVN in production. I have 0.43rc1 with > additional patches, including your change #129 which, I think, is what > you