Matt, I believe it is #2, as the intended function is to end the test. This is in conjunction with the various body filters in use, such as GIBBERISH and so forth.

 

FYI, that’s it for me today. Have the rest of a good weekend.

 

John Tolmachoff

Engineer/Consultant/Owner

eServices For You

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt
Sent:
Saturday, September 18, 2004 5:48 PM
To: [EMAIL PROTECTED]
Subject: [Declude.JunkMail] Question about END operation

 

Scott,

I ran into an unexpected behavior with END statements that I could use some clarification on if you don't mind.  Could you tell me which one of the following is the intended behavior:

  1. When an END condition is matched, the processing of the file will stop and the current score of the filter file will be returned along with the status (pass or fail) for scoring the Global.cfg settings.
  2. When an END condition is matched, the processing of the file will stop and the filter will return no score regardless of previous hits and a status of pass will be returned.


If the answer is #1, which I had believed it to be, I have found that it is not functioning in that manner using the latest interim release and I can expand on that if so.  #1 would of course be more desirable as well, but I need to make sure that I am working with the intended behavior in any event.

Thanks,

Matt

-- 
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================

Reply via email to