On Thursday, July 29, 2004, 2:52:07 PM, John wrote: JTL> Should I continue to forward spam that is not caught then?
Always send spam that is not captured to [EMAIL PROTECTED] If these keep coming through even after your update then we need to hunt for why they are not being tagged... If you find others that keep getting through then they are worth looking at, at least until we figure out what is going on. If you have a chronic spam then send us a zipped copy to support@ and we will research it. Spammers are crafty and well funded - so they might come up with something new that we don't see - not likely, but always possible. - If it is something we have filtered then either your rulebase is behind ours, or something is broken. If something is broken then we want to fix it of course. If the former, then we can explore ways to expedite discovery get rules in place more quickly. - If it is something we have not filtered then there is probably a reason we could not add a rule to the core - so we will be able to add a local black rule for you. JTL> I problem I have, is on the gatewayed domains, which are running Exchange, JTL> Exchange strips out the Header that Declude puts in, making it difficult to JTL> see what happened and caught by what tests. That can make things challenging. Once we have the message in hand we can figure out if there is a rule for it. In fact you can do that yourself by scanning the message from the command line and examining the results in the log file. (Set up a special directory for doing this so that you don't interfere with your normal operations.) Hope this helps, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
