Hello everyone,

I was wondering how to bypass the blacklistprovider, RBL ? I added the sender to bypass with the command Set-ContentFilterConfig -BypassedSenders but it seems not to work. The sender is still being blocked by the spamhaus blacklist provider.

Hello

tip: with Set-TransportAgent change agent priority

Hi Flavio,

As we know, IP Block List providers are frequently referred to as real-time block lists, or RBLs.

You can refer to the following article to configure filtering:

IP Block List provider procedures

These procedures apply to IP Block List providers. They don't apply to the IP Block list.

Use the IPBlockListProvidersConfig cmdlets to view and configure how connection filtering uses all IP Block List providers. Use the IPBlockListProvider cmdlets to view, configure, and test IP Block List providers.

Best regards,

Everything is working fine, but I have one specific sender that  I want to be ignored by the RBL.

How can I make the RBL ignore a specific domain? 

I'm not using Edge Transport server. I installed the "Connection Filtering Agent" through this command

Install-TransportAgent -Name "Connection Filtering Agent" -TransportService FrontEnd -TransportAgentFactory "Microsoft.Exchange.Transport.Agent.ConnectionFiltering.ConnectionFilteringAgentFactory" -AssemblyPath "C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\Microsoft.Exchange.Transport.Agent.Hygiene.dll" 

Everything is working fine, but I have one specific sender that  I want to be ignored by the RBL.

How can I make the RBL ignore a specific domain? 

I'm not using Edge Transport server. I installed the "Connection Filtering Agent" through this command

Install-TransportAgent -Name "Connection Filtering Agent" -TransportService FrontEnd -TransportAgentFactory "Microsoft.Exchange.Transport.Agent.ConnectionFiltering.ConnectionFilteringAgentFactory" -AssemblyPath "C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\Microsoft.Exchange.Transport.Agent.Hygiene.dll" 

The Connection Filter does not provide the functionality to exclude senders from RBL processing. The setting you are applying:

Set-ContentFilterConfig -BypassedSenders

...is only used by the Content Filter Agent but not the Connection Filter Agent.

What you can do is to whitelist the IPs of the sender at the IP Allow List using:

Configure this list using: Set-IPAllowListConfig

Add IPs to bypass RBLs using: Add-IPAllowListEntry

Oh and in Exchange 2013 the Connection Filter is only supported on the Edge server role!

What I said above is true for:

Exchange 2007 Hub/Edge

Exchange 2010 Hub/Edge

Exchange 2013 Edge

I tried to get the connection filter on the Ex 2013 Mailbox Server Role by installing it manually as you did, but this did not work for me.

I was able to install the Connection Filter, but the feature -IPAllowlistEntry doesn't work properly. So, if you want to allow some IP that has been blocked by the RBL, you won't be able to do that. If someone find a solution for it, please let me know!

I also noticed that the CLSJunkThreshold stopped to work. Once I installed the edge transport, everything started to work properly. The solution to install the Connection Filter is not bad but I think we need to be very careful how to use it.

You can check how to install the Connection Filter on the link below:

http://clintboessen.blogspot.com/2014/05/rbl-providers-and-exchange-2013.html