> Have you customized any registry settings for TCP/IP? No. Haven't needed to.
> with your DNS lookups. First, you should be downloading TXT records > from the RBL's instead of doing remote lookups. That should > save you a ton of resources. We have a caching DNS server in front of Declude that's getting about a 98% cache hit on the lookups right now, which says a lot about spammer demographics. We experimented with TXT records when we were still evaluating Declude (and many others) and it didn't change performance enough to be worth more than the benefit of real-time lookups. We get so much email here, five minutes sometimes makes a difference in how much spam is caught. (Hey Scott "god of spam blocking" Perry, if you're reading this, a caching feature internal to Declude would be a nice feature... just keep the last 1500 or so lookups in memory with a configurable TTL... now that would be really cool.) I do know that switching to "Bounce" on any of the tests causes the server to immediately bog down. :) > If you insist on testing the outgoing stuff, why not try > Declude Hijack > instead of JunkMail? It's got to be a whole bunch easier on your Is there a way to disable outbound testing in the "pro" version? I couldn't see that in the documentation (but I haven't really looked that hard, either). With the mess that Microsoft has created over the last couple of months, I haven't had time to look at the other Declude options, but will do. My biggest client published all of their employees' email addresses on their web page (a bright move, eh?), becoming one of the reasons why blocking the incoming hurricane of spam has been such a priority. Declude has been enormously successful! > could turn off some tests like DUL lists to save on resources? We don't run an open relay, so this doesn't matter. The biggest risk we have is from people finding our customers' wireless access points and using them to spam. We had someone in July park his car in front of a client's building and send over a million emails. Fortunately a sharp-eyed IT guy caught him and he is now Bubba's boyfriend. Our customers have been extremely resistant to SMTP authentication, and in some cases we've blocked SMTP from the WAPs. > Paying Microsoft for a trouble ticket also isn't anywhere near as > expensive as a new server either. It's pretty clear they broke your > setup, and from reading the bulletin, it shouldn't be limiting your My experience is this is just about as good at yelling at the sky for rain. > I read, there is no danger if you are isolated behind a > firewall that is > blocking ports that you should be blocking by default. Right-- the biggest risks are from the inside, not from the outside. You can't cure stupid, and someone in the organization will eventually cause a problem if we don't protect ourselves. So the server is now talking through firewalls on both ends until we get this figured out. By the way, thanks for your help. --- [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.
