On 2006-10-24 20:44:04 -0500, Peter Eisch wrote: > On 10/24/06 8:23 PM, "Ask Bjørn Hansen" <[EMAIL PROTECTED]> wrote: > >> I propose in the TODO the ability to clock the time it takes for > >> spamd to scan an email. A month or so ago there was a thread about > >> this and I forgot I had such a mechanism in my spamassassin plugin. > >> Rather than pollute this patch with its already suspect sprintf and > >> sed. I can submit that as a subsequent patch. > > > > I don't get it. Is "spamd is overwhelmed" a sign the mail was spam? > > Or are you talking about handling timeouts from spamd with a 451 > > response to the smtp client?
But you would have to issue the 451 before passing the mail to spamd. Otherwise you'll just exacerbate the problem by scanning lots of mails where the result won't ever be used. > I've seen emails crafted that spin spamd off only to return 4 minutes > later. When I've seen this happen, new versions of spamassassin soon > appear with emails citing http://secunia.com/advisories/20430/ as a > reference. (as an example) ITYM http://secunia.com/advisories/15704/ (20430 is a code injection issue). hp -- _ | Peter J. Holzer | Schlagfertigkeit ist das, was einem |_|_) | Sysadmin WSR | auf dem Nachhauseweg einfällt. | | | [EMAIL PROTECTED] | -- Lars 'Cebewee' Noschinski in dasr. __/ | http://www.hjp.at/ |
signature.asc
Description: Digital signature
