@johnpoz:
"In the case of smtp how should I fill in those fields (Interface, Protocol, Source etc.)"
Well the protocol is tcp.. email sure is not sent via udp ;) Source would be the IP address of your smtp server. Interface would be your wan but you pick the vip you want to use.. Dest could be just 25 which is the port email is sent on..
So is there any reason this server can not just use your vip for everything? If so then it makes real easy just put in his IP and the vip..
So see my attached example.. Lets pretend that 192.168.100.2 is a public IP that you created on your wan as a vip, etc.
That is what I am doing. I have about a dozen public VIPs all using the WAN interface. One VIP is for email with ports 25,465,993,995 open.
Another server using yet another VIP is listening on UDP port range 25000:25000 for GPS coordinates to track municipality service vehicles
like plow and salter. Some of our servers are actually in the could, that's how I started using PFSense, the cloud company uses it to manage
access to the virtual servers.
Anyway I am getting side tracked here. I will try the outbound NAT rule on our other smtp server, that one is not used that much. I don't want
to fudge up the other one that is already working.
Thanks for you input again.