Interceptors perform actions on incoming requests that seek to post content. You can configure interceptors on the Interceptors page of the admin console.
Admin Console: Spaces > Settings > Interceptors
Some of the interceptors have functionality related to features exposed for configuration elsewhere in the admin console. For example, the Ban User interceptor is designed to prevent the specified users from posting content. In contrast, the ban settings you can make elsewhere (see Banning People for more information) are designed to ban users from logging in at all.
When you don't want any part of a post or comment with an offending word to enter the space before an action is taken, use an interceptor instead of a filter.
For more about filters, see Filtering and Formatting Content.
Interceptors are included, but not installed (and active) by default. To use an interceptor, you first install it by clicking the filter name in the list, then clicking the Install button. After you've installed it, it will appear in a list of current interceptors. In that list, click its edit button to edit its properties. Interceptors are executed in the order they appear in the list -- if you install more than one, use the move arrows to make sure they're in an order that makes sense (for example, a message shouldn't be added to a moderation queue by a person whose IP is banned from posting).
Note that you can install an interceptor multiple times, giving different property values for each.
The following is a list of included interceptors, along with more about their properties.
In the Ban List box, enter a comma-separate list of application usernames for people you want to ban from posting. You can also select to have email sent to these users when they try to post. You can edit the "User Interceptor" message template for the email (see Managing Email Templates for more).
This interceptor provides ways to keep an eye on content coming in from certain people (or to simply ban them) based on their IP addresses. In the Banned IP List, enter a comma-separated listed of the IP addresses you want to ban from posting. Use the Email Notification boxes to send email to people you specify (such as administrators in your community) when posts come from certain IP addresses (see Managing Email Templates for more on the "IP Interceptor" template). In the Moderation IP List, enter the addresses of content sources whose posts should automatically be added to the moderation queue. (For more about moderation, see Moderating Content)
This interceptor gives you slightly finer control over how gateway-imported messages are handled (for more on gateways, see Synchronizing Content with Email or Newsgroups). You can hide the name or email address of the poster in the incoming message. If you do, you can store the hidden values in extended properties to you can take a look at them later. (For more on extended properties, see Fine-Tuning with Extended Properties.)
Use this interceptor for finer control over which users' content is moderated. The interceptor uses the user and group lists that are viewable on the People pages of the admin console (for more information, see Managing User and Groups.) Enter comma-separated lists of usernames or groups to specify who should always or never be moderated.
Use this interceptor to control how quickly a single user can post messages. For example, you might want to limit frequency if you're having trouble with auto-posting of spam messages. The message template is provided for you in the interceptor properties.
Through this interceptor you can use search query strings to locate text in incoming posts and associate predefined actions with them. For the query strings, use the Lucene search engine conventions described in Search Tips. Note that you cannot enter a comma-separated list of words. You can send posts to the moderation queue, block them from being published, or notify others via email when the post is received.
For example, imagine your community supports a product whose main competitor is something called a "flangy." You might want to have email sent to the community's manager if someone posts something that mentions the flangy in your community. You might even want to check if someone is posting quality-related adjectives about it. So you could define a keyword interceptor whose Email Query String is flangy NEAR awesome (or some such), then add a comma-separated list of email addresses to the Email Notification List box.