OK...this is a really annoying issue, but I figured I'd throw it out there.
Recently, I guess AOL implemented some policy changes in the way they receive mail - only email with reverse DNS entry stamps are allowed delivery to AOL addresses - we called AOL and validated this. From what I have seen, many companies are having issues now sending email to AOL addresses from their corporate email servers. Our users do a lot of business with clients who have AOL addresses, so this is a problem. We thought we had it fixed by adding a few more NAT rules to cover all of the ip addresses contained in our cluster...this worked for a while, but then all outside email in or our stopped. So we removed the rules and it went back to normal, without the AOL email working.
Have any of you encountered the same issue with AOL, and what are your plans to address it? We are hesitant to add a reverse DNS entry for security purposes, and Microsoft's first level of support can't figure ot out - we don't want to pay for an escalation of the ticket.
I do know Delta Airlines was having the same problem (we have an employee working onsite and he validated that for us).
We have a 2 node cluster running Exchange 2000. Any speculation or advice is most appreciated.
JB
Recently, I guess AOL implemented some policy changes in the way they receive mail - only email with reverse DNS entry stamps are allowed delivery to AOL addresses - we called AOL and validated this. From what I have seen, many companies are having issues now sending email to AOL addresses from their corporate email servers. Our users do a lot of business with clients who have AOL addresses, so this is a problem. We thought we had it fixed by adding a few more NAT rules to cover all of the ip addresses contained in our cluster...this worked for a while, but then all outside email in or our stopped. So we removed the rules and it went back to normal, without the AOL email working.
Have any of you encountered the same issue with AOL, and what are your plans to address it? We are hesitant to add a reverse DNS entry for security purposes, and Microsoft's first level of support can't figure ot out - we don't want to pay for an escalation of the ticket.
I do know Delta Airlines was having the same problem (we have an employee working onsite and he validated that for us).
We have a 2 node cluster running Exchange 2000. Any speculation or advice is most appreciated.
JB