Your Static and PAT configuration looks OK. I would like to why is the mail commint from .51 is your mail server is .50 ? I am assuming clients in your network should be using your internal mail server at .50 for mail relay. Could you check to see why the outbound source IP for mail is .51 from clients ?
There is no mail relay... the only mail server is the internal exchange server so thats why the .50 is being translated to 192.168.1.60 inbound. There is no mail server addressed as .50 so when mail gets sent out it comes straight from the internal server and all outbound connections are Nat'd to the outside interface. I know most organizations have an external mail server but this company doesn't. I would like to make it work without suggesting they buy an external mail server. All email is working today except for AOL because the source ip address does not match the MX record.
Your current config looks correct. I would do a show xlate and make sure that your mail server is mapped correctly. Also, if you go to http://www.whatismyip.com form your mail server, your ip address should be your .50 address. Did the returned mail from AOL have a reason it was bounced? Also, do you have reverse dns setup for your mx record. I don't think AOL will accept mail without doing a lookup.
To resolve your mail issues to AOL, what you need is a RDNS (Reverse DNS) setup for your PAT address, i.e. if all your internal IP's are being translated to your outside interface IP of your PIX then when you send mail to outside recipient's the IP address that will show up as the sending IP is your PIX's outside interface IP. So to resolve this issue, get your ISP to setup RDNS for your domain to point to your IP address of your PIX outside interface.
You can check this youself by going here - enter the IP address of your PIX's outside IP and see if AOL can resolve this IP to your domain name.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...