Because counterweighting let's you control how good you think a particular source is. That way, if a really bad email comes in (high score), perhaps from a spammer that is mimicking certain patterns to slip through filters, then you still catch it. Whitelisting would have it go through no matter how bad it really was.
We maintain three counterweighting levels to give us the granularity we need. One at our hold weight, one just under our delete weight, and a third at twice our delete weight for the really had senders that a particular customer needs mail from. Darin. ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <Declude.JunkMail@declude.com> Sent: Friday, November 04, 2005 11:23 AM Subject: Re: [Declude.JunkMail] Address Not Whitelisted? I am missing the thought process. Why is counterweighting by a large number so much better than whitelisting if both achieve the same purpose? Just asking, Don ----- Original Message ----- From: "Travis Sullivan" <[EMAIL PROTECTED]> To: <Declude.JunkMail@declude.com> Sent: Friday, November 04, 2005 8:59 AM Subject: Re: [Declude.JunkMail] Address Not Whitelisted? > Exactly, counterweight works so much better. Whitelist at the last > possible option. > > I counterweight everything and don't have a single whitelist entry. > > Travis > > ----- Original Message ----- > From: "Darin Cox" <[EMAIL PROTECTED]> > To: <Declude.JunkMail@declude.com> > Sent: Thursday, November 03, 2005 7:24 PM > Subject: Re: [Declude.JunkMail] Address Not Whitelisted? > > >> We've found that to be too general... You might try a regex or >> phrase-based >> whitelist that looks for unique text in the newsletter to whitelist it >> (or >> rather counterweight it). >> >> Darin. >> >> >> ----- Original Message ----- >> From: "Tyler Jensen" <[EMAIL PROTECTED]> >> To: <Declude.JunkMail@declude.com> >> Sent: Thursday, November 03, 2005 7:01 PM >> Subject: RE: [Declude.JunkMail] Address Not Whitelisted? >> >> >> Try >> >> Whitelist from @returns.bulk.yahoo.com >> >> Or >> >> Whitelist from @yahoo-inc.com >> >> I have one of these to allow fantasy football and baseball emails through >> to >> my franchisees. I have not seen any spam whitelisted because of this >> setup >> and I have been using it for at least a year. It may not be the best way >> but >> it has worked for me. >> >> Tyler >> >> >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of mail-lists >> Sent: Thursday, November 03, 2005 6:36 PM >> To: declude.junkmail@declude.com >> Subject: [Declude.JunkMail] Address Not Whitelisted? >> >> >> I'm at my wits end.. These Yahoo news alerts are legitimate messages, >> but >> I can't seem to whitelist them. >> >> So far in my global.cf I've added WHITELIST FROM settings to the >> following >> addresses, but they still don't get to the recipient! >> [EMAIL PROTECTED], >> [EMAIL PROTECTED], and [EMAIL PROTECTED] Anybody >> know >> what else I can do to allow these e-mails in? >> >> Thanks! >> >> Cavell >> >> Received: from n10.bulk.scd.yahoo.com [66.218.66.189] by >> cottonwoodfinancial.com >> (SMTPD-8.21) id A1190444; Thu, 03 Nov 2005 13:12:25 -0600 >> Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys >> DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ginc1024; >> d=yahoo-inc.com; >> >> b=p2OiCTjMDGenNXSS96zFPWPUJWbDSYtXDGfx+d+759EZNpjxhxAkRF35XS37W00BJ3v6G0WpK8 >> rYURzt55Dtrw8e6wXInDswJk67+7vNJnZRNIECCZO7cXBoKKaw2i4B8/wcWwL6WNeIq2lOUW >> rYURzt55Dtrw8e6wXInDswJk67+f8JH >> rYogvNoV28SaQReeLJUYw=; >> Received: from [66.218.69.2] by n10.bulk.scd.yahoo.com with NNFMP; 03 Nov >> 2005 19:12:53 -0000 >> Received: from [66.94.229.26] by mailer2.bulk.scd.yahoo.com with NNFMP; >> 03 >> Nov 2005 19:12:53 -0000 >> Received: from [127.0.0.1] by dlv8.alerts.scd.yahoo.com with NNFMP; 03 >> Nov >> 2005 19:12:53 -0000 >> X-yahoo-newman-property: alerts >> X-yahoo-newman-id: [EMAIL PROTECTED] >> From: "Yahoo! Alerts" <[EMAIL PROTECTED]> >> Subject: **SPAM**=?UTF-8?B?S2V5d29yZCBOZXdzOiBbIkFkdmFuY2UgQW1lcmljYSJd?= >> To: [EMAIL PROTECTED] >> Reply-To: "Yahoo! Alerts" <[EMAIL PROTECTED]> >> Return-Path: [EMAIL PROTECTED] >> Errors-To: [EMAIL PROTECTED] >> MIME-Version: 1.0 >> Content-Type: text/html; charset="utf-8" >> Content-Transfer-Encoding: 8bit >> X-Yahoo-AlertId:5cYJ5LIxGXHDwPmeko3O878bwgWlTAmS >> X-Yahoo-Alerts-Beta: YES >> Date: Thu, 3 Nov 2005 11:12:53 -0800 >> Message-Id: <[EMAIL PROTECTED]> >> X-RBL-Warning: MXRATE-ALLOW: "GOOD SENDER" >> X-RBL-Warning: CMDSPACE: Space found in RCPT TO: command. >> X-RBL-Warning: MAILFROM: Domain returns.bulk.y has no MX or A records >> [0301]. >> X-RBL-Warning: SPAMHEADERS: This E-mail has headers consistent with spam >> [4000020e]. >> X-RBL-Warning: SUBJECTCHARS: Subject with at least 50 characters found. >> X-RBL-Warning: WEIGHT10: Weight of 24 reaches or exceeds the limit of 10. >> X-Declude-Sender: >> alerts.kmydqmbqgu2wknrtmy3taljygvxdau3ikndxovs7he3gwx3hhbeha2thovsvmvjxmiyuw >> [EMAIL PROTECTED] [66.218.66.189] >> X-Declude-Spoolname: D6119016000007008.smd >> X-Declude-Note: Scanned by Declude 3.0.5.5 >> (http://www.declude.com/x-note.htm) for spam. >> X-Declude-Scan: Score [24] at 13:12:37 on 03 Nov 2005 >> X-Declude-Tests: MXRATE-ALLOW, CMDSPACE, MAILFROM, SPAMHEADERS, >> SUBJECTCHARS, WEIGHT10, WEIGHT14, WEIGHT18 >> X-Country-Chain: UNITED STATES->destination >> X-RCPT-TO: <[EMAIL PROTECTED]> >> Status: U >> X-UIDL: 424737504 >> X-IMail-ThreadID: 6119016000007008 >> >> >> >> >> Confidentiality Notice: The information contained in this transmission >> is >> intended only for the personal and confidential use of the designated >> recipient named above. If the receiver of this transmission is not the >> intended recipient or an agent responsible for delivering it to the >> intended >> recipient, you are hereby notified that you have received this document >> in >> error, and that any review, dissemination, distribution, or copying of >> this >> message is strictly prohibited. If you are not the intended recipient, >> please immediately notify the sender and delete this e-mail message from >> your system. >> >> >> --- >> 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 scanned for viruses by Declude Virus] >> >> >> --- >> 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 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 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 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 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.