Scott: Thank you for your response. Since we started doing this (almost a week) I have noticed several "real-life" behavior from our server.
What we used to see: - When a list was hitting our server I was seeing many Declude.exe processes at the same time - one after another taking 100% of CPU and disappearing. As stated a while back, in one case, the server was almost down for 2-3 hours. By down I mean it could not do anything else but process what was being sent to it. We could not check email, outlook was timing out, and web messaging would return error. Once the processing ended the server was back to normal. Of course part of the problem is the way we do things (isn't it always?). We have a lot of filter files and were checking a lot of ip4r tests. Actions we took: - we commented a lot of ip4r tests in Declude and that helped a lot with times when a lot of email was hitting the server at the same time (lists) but still we were getting time outs in Outlook and web messaging was very slow when the emails were arriving. In essence we stopped using so much of the ip4r tests and only used about 8 or so, rather than all that was listed in the Declude site. - with IMail 8 I thought of moving all the ip4r tests to IMail so I can test a few things. Now the results are interesting. We no longer have that problem. The Outlook does not time out and looking at the Declude processes they appear and disappear fast and even if they hit 100% CPU it is for a very short time. We have not changed our filter files and actually have added two more. So the processing for Declude has not changed at all but it is not doing any ip4r tests. We now simply do all the ip4r tests in IMail, add the header and have a X-Header filter file. After reviewing the log files we will eventually get rid of some of the ip4r tests that we find are not effective but for now we are looking at majority of what you have listed in the Declude site. The header weights ranges from 1 - 8. Myth? Fact? Or just my imagination... May be our mail ends up in our backup mail server while IMail is busy checking ip4r's and since all email is not arriving at the same time Declude can manage it without assuming control of the server for a long time. So in essence we are managing delivery of email in a pipeline .. Of course the users may not mind waiting a minute before the mail arrives but they get frustrated when their mail client times out. Our problem is solved for now. - IMail do ip4r tests - Declude do the filters This was just a report from the field... Regards, Kami --- [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.
