I hate it when this happens! I just sent off a Troubleshooter column question for the December issue on how to create separate settings on separate IMF servers. My answer involved multiple forests and was fairly ugly. I then decided to relax and do a little blog surfing. Lo and behold, It turns out that (courtesy of Evan’s blog) there’s a much more elegant solution to this problem.
The answer is “registry override“. The gateway settings are read first from the AD, but the registry on the IMF gateway server is also consulted and if there is an override setting configured, these “per-server” override settings are used instead.
It turns out that HKLM\Software\Microsoft\Exchange\ContentFilter can accept a value named GatewayThreshold; its range is 0-9, just like the SCL. Set the GatewayAction DWORD value to 0 (no action), 1 (delete), 2 (reject), or 5 (archive + delete) and you’re in business. Thanks, Evan!
Paul's Down-Home Page 