this is what we do for those valid mailing lists that get blocked from time to time...we just add those individual addresses requested by our customers to this list as well; if forgery becomes a problem, then we alert the customer that made the addition request and remove the address; the customer is then forced to follow the whitelisting in WebMail process. FILTER-GOODMAILINGLISTS fromfile C:\IMail\Declude\filters\filter-GoodMailingLists.txt x -50 0
Sincerely, Randy Armbrecht Global Web Solutions, Inc. 804-346-5300 x112 877-800-GLOBAL (4562) x112 http://globalweb.net ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of IS - Systems Eng. (Karl Drugge) Sent: Friday, July 28, 2006 12:27 PM To: [email protected] Subject: RE: [Declude.JunkMail] Max whitelists hit Sensitivity: Confidential Maybe you don't really want to whitelist. What we do here is use a FROMFILE, and assign a large negative point value to all domains or individuals on that list. We still suffer with forged return addresses, but that's fairly minimal. It tends to work a little bit better then whitelists, IMO. This lets you pass the mail, but it still run the tests you have defined in declude to filter out the really horrendous stuff, or at least explain WHY stuff did or didn't get through. Karl Drugge --- 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.
