[Declude.JunkMail] Order of processing various filter types.
Scott, I know this has been discussed at least in pieces in the past, but I was hoping that maybe you could put it all together for me (and maybe also add the order to the manual when the new functionality finds its way into a full release). Could you give me an idea about the order of processing for the following, or indicate which ones might be run according to where they lie in the Global.cfg? This will of course make a difference in performance, and I would like to provide good guidance myself as I comment up my filters for sharing with others. The types that I can come up with off the top of my head are as follows - ipblacklist - fromblacklist - ipfile - fromfile - spamdomains - filter Also, if it's not that big of a deal in modifying the programming, would it be possible to add SKIPIFWEIGHT functionality to the non-filter types? I don't believe that MAXWEIGHT, MINWEIGHT and END though would provide any more functionality to non-filters, but SKIPIFWEIGHT still has potential for saving processing with these other types. Having that in the filter type though is of course 90% or more of the issue, so don't let me appear to be looking a gift horse in the mouth :) Thanks, Matt --- [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.
Re: [Declude.JunkMail] Order of processing various filter types. types.
Could you give me an idea about the order of processing for the following, or indicate which ones might be run according to where they lie in the Global.cfg? This will of course make a difference in performance, and I would like to provide good guidance myself as I comment up my filters for sharing with others. The types that I can come up with off the top of my head are as follows - ipblacklist - fromblacklist - ipfile - fromfile - spamdomains - filter The very general order is that IP-based spam tests come first, and everything else is done later. You could try looking through debug log file entries to try to get a better understanding of the order the tests are run in. That is something that we do not keep track of, as the tests are not all run at the same time (meaning that other code runs between tests as needed). Also, if it's not that big of a deal in modifying the programming, would it be possible to add SKIPIFWEIGHT functionality to the non-filter types? That would start to get tricky. It works for the filters because each filter has many lines determining what should get caught. Some other tests do this (such as the sender blacklists), but other tests do not. Those that do would require a change in the way the files work (the sender blacklist just lists E-mail addresses or domains, and doesn't contain any commands). It's possible that we may work on this, but it would take a while (as we would have to add code for each test). -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [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.
RE: [Declude.JunkMail] Order of processing various filter types. types.
Matt, On Dec 11th, Scott replied to John Tolmachoff: --- A while back, I had asked about the comparison in performance of a fromfile and a filter using MAILFROM ENDSWITH. But wouldn't Declude stop processing a fromfile as soon as a match is found, where in a filter to goes through the whole file? That will happen. :) In the current version, it will go through all entries. However, as you pointed out, there is no benefit in continuing processing with a fromfile after the first match is reached -- so the logic will be changed for the next release (and therefore giving the fromfile a slight performance advantage over filters -- but it would only be noticeable if there were a lot, perhaps 1000s, of entries). -Scott - This would indicate that using a MAILFROM filter rather than a fromfile and utilizing SKIPIFWEIGHT and END would provide the functional control without any performance loss. George -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of R. Scott Perry Sent: Tuesday, December 23, 2003 8:30 AM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] Order of processing various filter types. types. Could you give me an idea about the order of processing for the following, or indicate which ones might be run according to where they lie in the Global.cfg? This will of course make a difference in performance, and I would like to provide good guidance myself as I comment up my filters for sharing with others. The types that I can come up with off the top of my head are as follows - ipblacklist - fromblacklist - ipfile - fromfile - spamdomains - filter The very general order is that IP-based spam tests come first, and everything else is done later. You could try looking through debug log file entries to try to get a better understanding of the order the tests are run in. That is something that we do not keep track of, as the tests are not all run at the same time (meaning that other code runs between tests as needed). Also, if it's not that big of a deal in modifying the programming, would it be possible to add SKIPIFWEIGHT functionality to the non-filter types? That would start to get tricky. It works for the filters because each filter has many lines determining what should get caught. Some other tests do this (such as the sender blacklists), but other tests do not. Those that do would require a change in the way the files work (the sender blacklist just lists E-mail addresses or domains, and doesn't contain any commands). It's possible that we may work on this, but it would take a while (as we would have to add code for each test). -Scott --- Declude JunkMail: The advanced anti-spam solution for IMail mailservers. Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection. Find out what you've been missing: Ask about our free 30-day evaluation. --- [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.
