(Whups! My bad, "whitelist anywhere" is right there in black and white in the current online manual.)
If you use this directive in your .cfg file: PREWHITELIST ON then you get "short-circuit evaluation", and a WHITELISTed message will get processed a little faster than it otherwise would. Without that directive, all tests are performed on the message, because any of them could weight the message enough to change the action performed. In my humble opinion, you should avoid whitelisting; I suggest using counterweights instead as you illustrated in your question. Save whitelisting for things that are unquestionable, like whitelisting the IP of an internal mail server. Andrew 8) -----Original Message----- From: Robert Grosshandler [mailto:[EMAIL PROTECTED] Sent: Thursday, October 02, 2003 2:04 PM To: [EMAIL PROTECTED] Subject: [Declude.JunkMail] Performance Having just upgraded from JM Standard to Pro, I'm wondering about the best way to approach some of the tests I previously set up. Is there any difference between the following from a performance or maintenance standpoint?: Version A Whitelist anywhere blahblah Or Version B BODY -50 CONTAINS blahblah Thanks Rob =========================== Robert N. Grosshandler www.iGive.com --- [This E-mail scanned for viruses by Declude Virus] --- [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. --- [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.
