Here's an abbreviated version of my script: $list=Get-ContentFilterConfig $list.BypassedSenderDomains ="domain1.com" $list.BypassedSenderDomains +="domain2.com" $list.BypassedSenderDomains +="domain3.com" $list.BypassedSenders ="us...@aol.com" $list.BypassedSenders +="us...@aol.com" $list | set-ContentFilterConfig
Basically, it just recreates the list of addresses in BypassedSenderDomains and BypassedSenders. Of course, the real version has a lot more addresses. I stole the idea from a forum; all I've really done is change the names to protect our specific innocent. You've brought up a point that I have to research though. I don't know if this data is server-specific or enterprise-wide. I might be duplicating my efforts. It sure seems like this should be in a GUI somewhere. Steve Steve Hart I T Manager Wright Business Graphics Inc. wrightbg.com Wright Imaging Inc. wrightimg.com P.O. Box 20489 18440 NE San Rafael Portland, OR 97230 503-491-4343 Direct sh...@wrightbg.com -----Original Message----- From: Troy Meyer [mailto:troy.me...@monacocoach.com] Sent: Tuesday, February 17, 2009 4:19 PM To: MS-Exchange Admin Issues Subject: RE: Whitelist adds Yes, there is an easier way. I whitelist at the gateway so I don't know the specific exchange command, but first I would use a variable for the address so you don't have to mod you script every time. Something like Write-host "Give me your address please:" Read-host $whiteaddy I am not sure how you add these addresses, to me it looks like the default HT spam tools have IP whitelisting but not individual email addresses. What command are you using? If you were using the IP Allow list, that is stored in AD and shouldn't be server specific (ie you shouldn't have to TS into the 2nd box). If your command isn't storing the data in AD, I bet you can add -server to the command to specify which box it effects. -troy -----Original Message----- From: Steve Hart [mailto:sh...@wrightbg.com] Sent: Tuesday, February 17, 2009 4:03 PM To: MS-Exchange Admin Issues Subject: Whitelist adds For various sundry and corporate reasons, we've got two Exchange 2007 servers. Each one is running the Exchange anti-spam tools as a hub transport server. Funding for an external spam solution is lacking. We're using Spamhaus and a rather long list of ugly words with surprising success. We have myriads of customers (well at least a notable few) that are running businesses from their garages with yahoo and aol accounts. Others are using cheap, not quite so reputable ISPs. We do printing for pharmaceutical customers and we have at least one customer with an unfortunate last name that's typically filtered. Whitelist management has become a daily task. I've adapted an online Exchange Shell script to our use. Adding an address to the "Server1" whitelist involves a simple text edit to the script and then running it in the shell. Then I have to remote to the second server and run the same script there. All in all, it's only five minutes, but five minutes several times a week is getting annoying. Is there an easier way to manage these little whitelist additions? ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~ ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
