> > max size for spamc/spamd). I ended up solving it by adding > > a read() loop to spamc to flush the read buffer so that the > > milter would be ready for the response. It's probably not > > the best solution, but I'll attach the patch anyway. > > Are there any particular problems with this approach? Does > anyone know of a better solution? If not, I propose that the > patch attached to the original mailing be committed, at least > until something better can be worked out. Any thoughts?
I agree - I've been running a patched spamc for a few days now. It has totally solved my deadlocks. I plan on submitting it to the Debian maintainer fo SA if it makes it out the end of the week. Ross _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
