> >Is there a best practices way of making sure that specific e-mail addresses > >make it through? > > In this case, the best option would probably be "WHITELIST FROM > [EMAIL PROTECTED]" (that line would get added to the > \IMail\Declude\global.cfg file). Although this would apply to E-mail sent > from [EMAIL PROTECTED] to *any* user on your server, if that address is > important to one of your customers, it's very unlikely that spam would be > sent from it (except perhaps to other users on the same domain, as spammers > might use it for sending to the same domain). > > >I thought about creating a "per domain" whitelist for that e-mail address. > >I've seen some mention of "per domain" whitelisting on here. Can someone > >tell me how I can find out the details about how to whitelist "per domain" > >and also if there's a specific version number of Declude JunkMail that I > >have to be running to take advantage of that? > > It would be possible to set up a per-domain whitelist (using the > WHITELISTFILE option in the latest beta), but that would probably be more > work than you want in this case.
Another option is my program Match. If it finds the to address in the to.txt file AND the from address in the from.txt file, it "fails" the test, which you could then assign a weight of say -50 for "failing" allowing the message to pass. This way, you are not whitelisting the address for everyone. John Tolmachoff MCSE CSSA Engineer/Consultant eServices For You www.eservicesforyou.com --- [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.
