On Fri, 18 May 2012, Matt Simerson wrote: > That was 4 years ago, and the posted patch never got committed. > > It makes me think the problem was a local and ultimately fixed via other > means. Are you aware of anyone having this problem today?
I see sporadic new reports of this type of problem. See for instance: http://bugs.contribs.org/show_bug.cgi?id=6628 But this isn't a little bug - it's a serious design deficiency. Any plugin might block forever, and there is nothing in the core framework to detect that and timeout the connection. Ask has already stated this is a "pretty bad bug". http://www.mail-archive.com/qpsmtpd@perl.org/msg06534.html > > Matt > > On May 18, 2012, at 9:45 AM, Charlie Brady wrote: > > > > > Maybe I've missed it in the flurry of patches, but I still see no sign of > > timeouts being enforced across plugins. > > > > http://grokbase.com/p/perl/qpsmtpd/097nr0gyr2/never-times-out > > > > http://www.nntp.perl.org/group/perl.qpsmtpd/2008/02/msg7779.html > > > > Hanno once developed some code to address the issue, but I don't know what > > became of that. > > > > http://grokbase.com/t/perl/qpsmtpd/0864wdzm0n/per-plugin-hook-timeouts > >
