• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 654
  • Last Modified:

Exchange mail relay through Watchguard XTM 505

We have a remote Hosted Web Application in a server with IP address 80.241.209.xx
Our Network is behind a Watchguard XTM 505 with OS 1.7.
Our Exchange 2010 Server  has a Private IP, 150.81.1.x and has a 1-1 NAT with one external interface which its Ip is 146.198.136.xx in which the server responds to DNS. The smptp packet filtering works perfectly for inbound and outbound smtp traffic.

Now the problem is that I want this application to send email to external addresses through the exchange server. I already created the receive connector on Exchange that has in the remote address the 80.241.209.xx. The Authentication is Externally secured using IPSec as per instructions and the permitions is Exchange Servers and Anonymous users.
While I telnet  from 80.241.209.xx to mail.avratours.gr port 25 which responds in 146.198.136.xx I can send email only to internal users and not to external addresses.
Can I do something by creationg a policy in watchguard?
Thanks
0
nmariolis10
Asked:
nmariolis10
  • 2
1 Solution
 
DLeaverCommented:
Uncheck the Anonymous check box

Only Exchange servers needs to be checked for authentication as you are relaying a server.
0
 
nmariolis10Author Commented:
Sorry but checked or unchecked the same result. I can send from the remote located machine and send email only to local exchange users but not to remote addresses. I get the error 500 mailbox unavailable
0
 
DLeaverCommented:
Have you got the actual NDR you are receiving - thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Increase Security & Decrease Risk with NSPM Tools

Analyst firm, Enterprise Management Associates (EMA) reveals significant benefits to enterprises when using Network Security Policy Management (NSPM) solutions, while organizations without, experienced issues including non standard security policies and failed cloud migrations

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now