Here's what I want in a nut shell:
STMP IN -> UTM Any configured IP (or at least being able to bind it to what ever IP(s) I want) -> Exchange Server (Or any e-mail server)
Exchange Server (Or any e-mail server) -> UTM NAT to what ever IP I configure -> SMTP OUT.
One-to-One NAT
Gil Peled.
CEO- Expert2IT LTD.
SOPHOS Platinum Partner.
Gil@expert2it.co.Il.
Gil Peled.
CEO- Expert2IT LTD.
SOPHOS Platinum Partner.
Gil@expert2it.co.Il.
In general, a packet arriving at an interface is handled only by one of the following, in order:
DNATs first, then VPNs and Proxies and, finally, manual Routes and Firewall rules.
Never create a Host/Network definition bound to a specific interface.
Always leave all definitions with 'Interface: >'.
If your DNAT wasn't getting traffic to the mail server, this is probably the reason.
As I said above, for outbound traffic that has had AV & AS done by the SMTP Proxy (the mail server uses the UTM as a smart host), you need:
SNAT : External (Address) -> SMTP -> Internet : from External (WAN) [Server] (Address)
First, enable the smtp proxy. Doing this will intercept all smtp traffic passing through the astaro on all interfaces and all ip addresses (including internal ip addresses).
Email Protection --> SMTP --> Advanced
Second, on the same screen, create an exception to skip transparent mode for your internal network and then check the box that says "Allow smtp traffic for listed hosts/nets".
SNAT : Internal (Network) -> SMTP -> Internet : from External (WAN) [Individuals] (Address)
Tom, this will work, but I recommend against using Transparent. I prefer to SNAT non-proxied traffic from an Additional Address different from the one used for the Proxy. That keeps you off blacklists when a Trojan sends spam from an infected PC. This NAT rule should come after the one in my post above and looks like:SNAT : Internal (Network) -> SMTP -> Internet : from External (WAN) [Individuals] (Address)
The other approach is to block non-mailserver SMTP traffic altogether.
Cheers - Bob