|
You are here: Home>> FAQ>>Forwarding
If you run a forwarder you know the problems associated with forwarding and spam filtering. Mail that did not originate from your server, but is sent through your server is causing you headaches. Because the connecting IP is your mail server it may end up being delayed or even blocked. For the most part AOL associates the connecting IP with the mail being delivered. This can cause a problem when an AOL member clicks "This is Spam." Ultimately this is your IP they are reporting right? In this article, I will go over a few ways to help you forward once again.
* X-SPAM-FLAG: Yes
Implement your normal anti-spam measures on any mail being forwarded. If you detect the mail as spam you can add the above header line and we can deposit that mail in the AOL members Spam folder. If the AOL member has built a relationship with the sender, the mail will be deposited into the inbox and NOT the SPAM folder. Note: The flag must be printed exactly as it is above no other information can be added to the line.
*Segregate your forwarders
If possible, send forwarded mail from different IP's than your normal mail. This will allow us to determine which mail is typical mail and which is forwarded.
*Setup a Feedback Loop
The Feedback Loop will help you determine if your anti-spam measures are working. It can also give you insight as to which customers may need to be educated concerning the forwarding process.
* Let us know
Contact our postmaster help desk to let us know which servers will be forwarding mail. We also have other options available including those listed below. You must contact us for these options to be affective.
* Receive line Checking
If your forwarders are segregated, we may have the ability to look through the headers of the email to determine what the originating IP is and act on it appropriately.
*X-Originating-IP
Include the MTA IP that connected to your network in this header. You must strip applicable X headers when the mail comes in for this information to be accurate.
| 
