This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Routing of Mailprotection

Hello together,

I have eth1 with an additional (public + static) IP.

Is it possible to bind SMTP of mailprotection on this second IP?

Thank you very much.


This thread was automatically locked due to age.
  • It's a simple NAT rule, Jack: 'SNAT : External (Address) -> SMTP -> Internet : from External [Mail] (Address)'.  Any luck with that?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • That worked!  Will the traffic always try and come from the primary External Address or am I going to have to make a rule for each possible Address that is bound to it in case it tries one of the other ones?
  • The SMTP Proxy always sends from "External (Address)"- it's the reason that I recommend naming the UTM something like mail.domain.com, and having the mail IP be the primary IP on the External interface.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • I wouldn't recommend naming the UTM with the mail.company.com FQDN because of my negative experience that I posted here...[;)]:
    https://community.sophos.com/products/unified-threat-management/astaroorg/f/52/t/29651

    Since then I always name new UTMs with FQDN utm.company.com and create new host records in public and internal DNS zones. 
    In E-mail protection -> SMTP -> Advanced -> Advanced settings then change the SMTP hostname to mail.company.com for use in HELO commands and SMTP welcome banner.
  • Good idea, vilic!  Since the device has changed from ASG to UTM and soon to SG, I've used secure.company.com recently where there already was a "mail" member of AD, and haven't changed the banner in 'Advanced'.  The key in both our approaches is that the primary MX record for the domain is for an FQDN that points at the IP of "External (Address)."

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA