sorry for Hijacking this, but I have the exact same question.
I have two mail servers which serves different mail domains, and both have different public IP addresses.
I've managed this with the additional address feature for the WAN interface.
Emails are up and running, but filtered by some ISP with reverse MX lookup.
What I tried is a SNAT rule:
Position 1
Rule Type: SNAT
Traffic from: the internal network where the mail server is located
Service: any
Going to: any
Change source to: interface address with different public IP than the WAN interface
Change service to: blank
Auto Firewall rule: checked
This one does not have any effect at all.
Then I tried a masquerading rule:
Network: the internal network
Position: 1
Interface: WAN
Use address: the additional address
Again, no effect at all, whatismyip.com shows the IP from the WAN interface rather than that from the additional address.
sorry for Hijacking this, but I have the exact same question.
I have two mail servers which serves different mail domains, and both have different public IP addresses.
I've managed this with the additional address feature for the WAN interface.
Emails are up and running, but filtered by some ISP with reverse MX lookup.
What I tried is a SNAT rule:
Position 1
Rule Type: SNAT
Traffic from: the internal network where the mail server is located
Service: any
Going to: any
Change source to: interface address with different public IP than the WAN interface
Change service to: blank
Auto Firewall rule: checked
This one does not have any effect at all.
Then I tried a masquerading rule:
Network: the internal network
Position: 1
Interface: WAN
Use address: the additional address
Again, no effect at all, whatismyip.com shows the IP from the WAN interface rather than that from the additional address.