Scott- I think this is a great idea.
Once we know a message has passed the delete limit, why would we want to keep testing it in routine operations? Of course, we'd need to be able to turn it off when needed for debugging or whatever, but it would save a lot of processing time under normal conditions. My suggestion would be to define it in global.cfg (maybe QUITIFWEIGHT ?) and have it become active only when encountered in the junkmail file test sequence. That would let us group the positive tests first, then any tests we considered mandatory, then QUITIFWEIGHT would stop the processing at that point or any later point if the specified weight is met or exceeded. That would minimize the need for SKIPIFWEIGHT and other statements. My two cents worth, anyway. -Dave Doherty Skywaves, Inc. ----- Original Message ----- From: "R. Scott Perry" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 21, 2004 11:41 AM Subject: RE: [Declude.JunkMail] Clarification > > > Is there a test, in the works, that will end all processing of > >any further filters. Basically, exit all Declude processing, or is it > >best to use the SKIPWEIGHT, thanks, > > There isn't anything like that in the works now, but it is something that > we may end up adding. > > -Scott --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
