Hi Scott, > >I see the same (with a very small domain and very light usage). The mail > >server is nowhere near the strongest, but is sometmies stressed with 1.70 > >(and was the same with 1.69b) but not 1.65. > > My recommendation for those that are experiencing this is to try adding a > line "DECODE OFF" to the \IMail\Declude\global.cfg file, and see if this > takes care of the problem. There were some base64 and HTML decoding > functions added since 1.65, which use more CPU time than most Declude > JunkMail functionality. They can be disabled with the "DECODE OFF" line.
Well as you can read in another mail I went back to 1.65 first. This server has been running normally for several hours however.... I also went back from daisychaining to normal IpSwitch smtp32. If it all runs stable today then tonight I'll enable daisychaining again to make sure attachments via the webinterface get scanned. If all still runs normal on tuesday (monday is a holiday overhere) then I'll go bacl to 1.70 and see if the problem returs. If it does I'll enable the DECODE OFF option te see if that solves the problem. > I'm also going to investigate the changes to the ip4r tests, to see if that > may be the root of the problem. It *shouldn't* be, but then again there > isn't anything in Declude JunkMail that *should* cause 100% CPU usage. :) Right, this setup has been rocksolid for two years so if it realy has been Declude which was responsible, then that's a first. ;-) Met vriendelijke groet, Bonno Bloksma --- [This E-mail scanned for viruses by Declude Virus using f-prot] --- [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.
