We have a spam blocker that sits on the Internet and forwards clean mail to our Exchange server. The MX record points to this IP, but we are still getting a lot of spam that never passes through our spam blocker. I have confirmed that it is not an internal spambot.
Question: How do I configure the ASA to only allow the Spam blocker IP to send mail to our internal network?
Software/Hardware used:
ASKED:
May 8, 2009 3:10 AM
UPDATED:
May 11, 2009 6:12 PM
KevinBeaver is basically right. You need to create an access list that allows mail from the spam blocker, but not from anywhere else. It will also need to allow any other traffic to any hosted systems, such as a web server. It will also block anything else that is not implicitly allowed, as there is an implied deny everything at the end of any access list.
It should look sometihng like this
access-list Internet-In permit tcp host {IP of spam blocker} host {public IP of your Mailhost} eq 25
access-list Internet-In deny ip any host {public IP of your Mailhost}
access-list Internet-In permit [other services you want to allow in]
Then apply this to the inbound traffic on the ‘outside’ interface with the command
access-group Internet-In in interface outside
Then the only mail traffic that will hit your mail server will be from the spam blocker.
PM me if you need something more detailed for your particular network.
Thanks for the information and it worked perfectly. I knew it had to be a rule, but I was looking at the static routes and not the access list. Thanks again, and by the way it did stop the spam instantly.
Good posting BLankReq!!!
Thanks Guys – I appreciate the feedback