3 replies
by [_rick_>
@domain, name@domain and domain are all valid for this. For instance if you receve a message from @mail1.bogus.com and another from @mail2.bogus.com, instead of entering both full domain names you can add the common factor to the filter list - bogus.com, the connector should match it against both full domains.
If you want to restrict against a certain person then use the name@domain. If you want to restrict against a certain domain then use the @domain, but keep in mind the example - if you filter @mail1.bogus.com, messages from @mail2.bogus.com will still be permitted.
Also check your IMC routing to make sure that you are not inadvertently configured as a open relay. There are articles on this for Exchange 5.5, go to the technet WebSite and search on open relay.
As a thought you may want to consider investing in a content/spam filter for the IMC. These addon application range in price depending on what bells and whistles you want and need. On the low end with price (but notfunction) is an application found on http://www.nemx.com, it allows you to filter on address, subject, message content, Open Relay Database, and RFC header information. This app. ties directly in with the Exchange Directory and does not require a separate system. Maintenance is via the Exchange admin program.
This application does have some draw backs and the Exchange 5.5 version does have size limitations to the number of entries possible for each filter - which I understand is not true in the Exchange 2000 version. The size limitation is an inherited limitation of the Exchange 5.5 Directory Store - where the rules and filters are kept. Exchange 2000 uses Active Directory which has a much better capacity for data objects.
Good luck
-Rick
by dlweaver
by dlweaver
This discussion is closed to new replies.
Trending Software posts
Sort by Trending