Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 11 replies
  • Subscribers 6 subscribers
  • Views 16070 views
  • Users 0 members are here
Options
Suggested
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

SMTP Proxy With NAT - how to publish Exchange/OWA

colly72

I'm currently using NAT with our Exchange server (I've not had any success with WAF). I've setup the UTM SMTP proxy to filter inbound and outbound mail, with Exchange using the UTM as a smart host. Any outbound mail is going through the proxy but inbound seems to come straight to the Exchange server, bypassing the smtp proxy. If I turn the NAT rule off, the proxy seems to work properly, but then I can't connect with Outlook, or Outlook Web App. It's probably really straightforward but can anyone give some advice on how I might get this to work? I'd use WAF ideally but I've tried numerous times, following the docs word for word and it never works properly for me. Thanks, Michael



This thread was automatically locked due to age.
Parents
  • 0

    Hello colly72, did you find a way to successfully publish Exchange through the WAF? I've been working on this for days and can't get it to work either.

    When I call tech support the people their seem like they don't even know what Exchange is. Quite upsetting.

    The partner I purchased the UTM from suggests that I DNAT all HTTP and HTTPS traffic to the Exchange Server. I think that's just a stupid idea. It totally defeats the purpose of having a firewall, insofar as HTTP traffic goes.


    I used Microsoft ISA Server 2006 prior to purchasing this UTM and it handled Exchange perfectly. I don't understand why Sophos can't get it to work.

    Please let me know if you found a solution.

    Thank you, Herb

  • 0 in reply to HerbStull

    Hi Herb,

    I've not got it working yet but I'm planning on migrating our existing Exchange 2010 server to 2016 and then try again, to see if I have more success.  It might take a while for me to complete but I'll update here, if I get anywhere when I've migrated.

    Cheers,

    Michael

Reply
  • 0 in reply to HerbStull

    Hi Herb,

    I've not got it working yet but I'm planning on migrating our existing Exchange 2010 server to 2016 and then try again, to see if I have more success.  It might take a while for me to complete but I'll update here, if I get anywhere when I've migrated.

    Cheers,

    Michael

Children
  • 0 in reply to colly72

    colly72 said:

    I've not got it working yet but I'm planning on migrating our existing Exchange 2010 server to 2016 and then try again, to see if I have more success....

    In opposite, it will be even more complicated to publish Exchange 2016 than Exchange 2010. Not based on mine, but from other community forum members experience.

    As a last resort, publish the Exchange with no firewall profile in WAF, just to check that everything is correctly setup on DNS/Networking level.

Unfiltered HTML