01-11-2010 11:03 AM - edited 03-11-2019 09:56 AM
Currently, I have a static mapping of my public mail ip address to my Exchange server on the inside of the ASA 5510 using the statement below:
access-list outside extended permit tcp any host 69.3.216.x eq smtp
static (inside, outside) 69.3.216.x 192.168.1.x netmask 255.255.255.254
I added a mail-filtering gateway(Symantec Brightmail) into the configuration. On the mail gateway, I use two NICs; one for incoming mail and one for outgoing mail. I have modified the above mapping to point to the incoming NIC on the mail gateway as below:
static (inside, outside) 69.3.216.x 192.168.1.8 netmask 255.255.255.254
Once the incoming mails are filtered, they will be relayed to my Exchange server.
I have configured my Exchange server to relay outgoing mail to the gateway outoging NIC (192.168.1.9). The outgoing mail reach the mail gateway, but I don't know how to configure the ASA to map the outgoing NIC of the mail gateway (192.168.1.9) to my public mail ip address (69.3.216.x).
Can anyone help?
Andrew
01-11-2010 02:52 PM
You won't be able to create another static mapping the 192.168.1.9 internal address to the same external IP address as the .8 server. If you have a spare public IP address allocated from your ISP then you can just create a second static for the outgoing mail, although that will obviously cost you additional money.
However, you may not really need a specific public IP address for outgoing mail. Certainly you need a public one for your incoming mail so that the mail can be properly directed to your incoming mail server, but outgoing mail could be treated just like any other outgoing traffic, couldn't it? What I mean by that is, why do you need a specific public IP for your outgoing mail, why not just let it use the standard nat/global that all your other outgoing traffic is using? That way you wouldn't need a second static nor need a second public IP address.
Not sure if that helps you or not. As I said at the start though, if your outgoing mail must come from a specific IP address then your only option is to get a second public IP address and add a second static. You canNOT create two statics mapping the same external address to two different internal addresses.
Thanks, Glenn.
01-11-2010 08:50 PM
Hello,
Is your SPAM filtering server located on inside as well ? Or is on DMZ network ? Anyways, let me assume you have the filtering server on inside just like your exchange server.
You really want your outbound mails to be filtered..?
In case you did not want that to be filtered, and exchange erver can send out the emails directly to internet then ALONG with the static for spam filtering server you could have made everything work with a simple dynamic NAT :
nat (inside) 2 192.168.1.8
global (outside) 2 69.3.216.x
Now, lets assume you DO want the outbound emails to be filtered. Then your requirement would be to map several internal IPs (since both servers are on inside) to one public IP address. We can acheive that using static Policy NAT :
access-list POLICY extended permit tcp any 192.168.1.8
static (inside,outside) 69.3.216.x access-list POLICY
access-list POLICY extended permit tcp any 192.168.1.9
static (inside,outside) 69.3.216.x access-list POLICY
Lets see if this helps you
Vijaya
01-11-2010 10:37 PM
Hi,
Can you clarify following point
1. When you are saying you have two NIC on mail gateway ,what subnet they belongs to ?
2. How the mail gateway connected to your mail server, Is your mail server too have two NICs?
3. You mentioned netmask as 255.255.255.254 in SNAT what are you try to achive by this?
And If you are using any public ip address apart one currently configured for mail server, make sure
that you have configured correct DNS PTR record for that IP pointing to your domain. Otherwise some mail server
will reject mails from your server.
Dileep
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide