FOPE: New updates for managing policy rules

Forefront Online Protection for Exchange (FOPE) customers, we’re listening to your feedback and queries about FOPE — and we’ve got new documentation updates for you. Please check out the improved Create, Edit, or Delete a Policy Rule in the TechNet Library.

In addition to spam and virus filtering, the FOPE administration center policy rules let you enforce specific company regulations and policies by configuring customizable filtering rules. As a direct response to your feedback about the policy rule information that we’ve published, we updated our guidance to clarify the administrator rights that are necessary in order to make changes to FOPE policy rules. Previously it wasn’t clear that the ability to view and change policies depends upon the access permissions of the logged-in user. You can see the updated information at

Share your experience or get more help

If you have your own experiences to contribute, we strongly encourage you to edit or post your own article in the public TechNet wiki. Check out the FOPE FAQ just to get started and look for the Post an article link.

If you need more help, there are other resources too. You can find related information in the links at the end of the policy rule topic that was just updated or, for assisted technical support, you can ask the community in the FOPE forum or contact Microsoft as noted in FOPE Support Information. You can always send us more feedback by using the rating system at the top of every TechNet Library page and Twitter users can follow us @FOPE_UA.

John Andrilla
Forefront Technical Writer

Comments (5)
  1. Nick F says:

    Cool stuff, can we get some improvements to the message tracking section next?  I'd love to be able to export tracking logs as a CSV or Excel file to my users, or link directly to a quarantined message from a log if possible (since we don't allow users to access their own quarantines).  Any hope there?

  2. ExchangeAdmin says:

    The ability to track ALL messages without populating both the to/from field would be amazing! We've been asking for years. There are some cases where a customer says they didn't receive an email, but are not sure of the exact domain because so many companies nowadays have subdomains, etc.

    Never understood why I couldn't just put in the recipient address and see ALL messages processed through FOPE for that user. Sadly, this is something only Tier 2 support can do.

    Also, how about providing *some* indication on why something was quarantined. I understand the whole proprietary information in regards to filtering, but it really is frustrating when a user asks why a message was quarantined and I have absolutely no idea…

  3. Korbyn says:

    What we would find handy is the ability to filter the AD Sync so that only certain mail enabled objects get published up into FOPE, either by LDAP query, or OU inclusion or OU exclusion…  We've really been surprised that these options aren't there, either that or we've not found the method in which to do this.

  4. says:

    Thanks for all the feedback here folks–keep it coming! We'll be discussing this and using your ideas to help us prioritize future updates. Cheers, John.

  5. Nick Izk says:

    Since migrating to Office 365 (enterprises), FOPE has been useless for us.  Until SSO is incorporated into the service, its near impossible to create over 400+ new passwords and expect our users to remember a different password for managing their SPAM.

    I'd love to switch over, but the management overhead is far too much with the current offerings of FOPE.

Comments are closed.

Skip to main content