User Tools

Site Tools


microsoft:excange_2013_whitelist

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
microsoft:excange_2013_whitelist [2017/11/24 15:08]
admin
microsoft:excange_2013_whitelist [2017/11/24 15:14] (current)
admin
Line 5: Line 5:
 The mail from the whitelist senders (individuals or entire domains) is considered safe and the end users receive it even if it falls within the filtering rules. The whitelist of senders in Exchange Server 2013 can only be managed from Powershell command prompt (Exchange Management Shell). The mail from the whitelist senders (individuals or entire domains) is considered safe and the end users receive it even if it falls within the filtering rules. The whitelist of senders in Exchange Server 2013 can only be managed from Powershell command prompt (Exchange Management Shell).
  
-<​note>​Note. The whitelist of senders in Exchange 2007 and 2010 is configured in the same way.</​note>​+<​note>​The whitelist of senders in Exchange 2007 and 2010 is configured in the same way.</​note>​
  
 +The whitelist in Exchange 2013 is configured on Mailbox or Edge Transport server with the installed Exchange anti-spam protection.
 +
 +The spam filter based on the content filtering checks if the address is in the white list. To edit the white list of addresses, the cmdlet **ContentFilterConfig** is used. The command has the following syntax:
 +
 +
 +<code winbatch>​
 +Set-ContentFilterConfig -BypassedSenderDomains microsoft.com
 +</​code>​
 +
 +
 +After running this command, all messages from senders in Microsoft.com domain will be received by the Exchange users regardless of their contents or attachments. (Further scanning with the Content Filter won’t take place.)
 +You can view the current contents of domains whitelist using this command:
 +
 +<code bash>
 +get-ContentFilterConfig
 +</​code>​
 +
 +If you have to add several domains to the white list at once, the command will look like this:
 +
 +
 +<code sql>
 +Set-ContentFilterConfig -BypassedSenderDomains microsoft.com,​woshub.com,​gmail.com
 +</​code>​
 +
 +To add a certain email address to the Content Filter white list, use BypassedSenders parameter:
 +
 +<code sql>
 +Set-ContentFilterConfig -BypassedSenders jkarlin@gmail.com
 +</​code>​
 +
 +The main problem of using Set-ContentFilterConfig cmdlet is that each time it is run, it completely rewrites (clears) the current white list of the safe senders. To avoid it, each time you have to add a new address/​domain to this list, get the current white list of addresses, add a new one to it and upload it back to Exchange.
 +
 +To add several domains to the Exchange white list (without clearing current list entries), you can use the following script:
 +
 +<code bash>
 +$list = (Get-ContentFilterConfig).BypassedSenderDomains
 + 
 +$list.add("​domain1.com"​)
 + 
 +$list.add("​domain2.com"​)
 + 
 +$list.add("​domain3.com"​)
 + 
 +Set-ContentFilterConfig -BypassedSenderDomains $list
 +</​code>​
 +
 +If you are adding individual addresses:
 +
 +
 +<code bash>
 +$list = (Get-ContentFilterConfig).BypassedSenders
 + 
 +$list.add("​bob@gmail.com"​)
 + 
 +$list.add("​jeorge@gmail.com"​)
 + 
 +Set-ContentFilterConfig -BypassedSenders $list
 +</​code>​
 +
 +To delete one entry from the white list of senders, run this command:
 +
 +<code bash>
 +Set-ContentFilterConfig -BypassedSenderDomains @{Remove="​gmail.com"​}
 +</​code>​
 +
 +Or:
 +
 +<code bash>
 +Set-ContentFilterConfig -BypassedSenders @{Remove="​bob@gmail.com"​}
 +</​code>​
  
microsoft/excange_2013_whitelist.1511532499.txt.gz · Last modified: 2017/11/24 15:08 by admin