To read the official Microsoft topic on this subject, see Configuring backscatter filtering in the Microsoft TechNet Library.
*****************************************************************
Forefront Protection 2010 for Exchange Server (FPE) Backscatter filtering is intended to prevent bounced mail or Delivery Status Notifications (DSN) for mail that was never sent from addresses in your organizations. In other words, mail that was sent with a forged “Sender” field in the P1 header. FPE prevents backscatter by tagging all outbound mail with a Bounce Address Tag Validation (BATV) token and then verifies all DSNs for the integrity of the tokens. If the token does not exist or does not compute correctly, the agent will reject the DSN.
To use Backscatter filtering, you need to enable the feature, configure optional domain exclude and reject lists, generate backscatter keys, and distribute the keys to all of your edge and hub servers that are protected by FPE.
In the Forefront Protection 2010 for Exchange Server Administrator Console Policy Management tree view, expand Antispam, and then click Configure.
In the Antispam - Configure pane, in the Backscatter filter section, select the Enable Backscatter filtering check box
You can add entries to the Excluded Domains list to allow DSNs from certain domains to always be accepted. All DSNs from domains on this list are exempted from backscatter filtering.
In the FPE Administrator Console Policy Management tree view, expand Antispam, and then click Configure.
In the Antispam - Configure pane, in the Backscatter filter section, click Configure Backscatter Lists or select Configure Backscatter Lists in the Actions pane.
In the Configure Backscatter Lists dialogue box, perform the following steps:
Click Save at the top of the pane to save your configuration.
The domain block list is used to block all DSNs from domains that you suspect to be spammers or domains from which you do not want DSNs for any reason.
The backscatter filter uses keys to tag all outgoing mail with a token that can be validate on bounced messages. The keys are generated in batches of ten and are valid until another set is generated. If you have multiple edge or hub servers in your environment, you will need to distribute the keys to all FPE protected servers so that they use the same keys to create tokens for outgoing mail. The keys are saved in the configuration.xml file that is stored in the data folder; for the default data folder on your operating system, see Default folders.
In the Antispam - Configure pane, in the Backscatter filter section, click Generate.
The keys are generated and the date and time are displayed in the UI.
In the Antispam - Configure pane, in the Backscatter filter section, click Export Keys.
In the export dialogue box, navigate to the configuration.xml file in the “data” folder and highlight the file.
Navigate to the folder where you would like to which you would like to export the file and click Save.
The file is saved to the location you selected.
In the Antispam - Configure pane, in the Backscatter filter section, click Import Keys.
In the import dialogue box, navigate to the configuration.xml file you saved and highlight the file.
Navigate to the “data” folder and click Open.
The file is saved to the data file.
Bruno Lewin MSFT edited Revision 5. Comment: Tweaked TechNet library URL to allow non-English users to be directed to article in their prefered language (if available)