Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 1 subscriber
  • Views 1016 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

Issue with incomming messages

CODE
Hi All,

we are not able receive incoming messages below is our setup

Firewall----------UTM9.2--------Exchange Server

A and MX records is pointing to UTM (9.2) 
UTM is  configured to route to the  internal Exchange Server by static host list 
 SMTP -> Relay added  Exchange server to Allowed hosts.


We are able to sent messages out and we can see the logs in UTM but not able to see any logs related to incoming messages.
we are able to telnet to the port 25

Senders will get the below error message



*****************************************************

This is an automatically generated Delivery Status Notification

THIS IS A WARNING MESSAGE ONLY.

YOU DO NOT NEED TO RESEND YOUR MESSAGE.

Delivery to the following recipient has been delayed:

     admin@*********X.com

Message will be retried for 2 more day(s)

Technical details of temporary failure:
The recipient server did not accept our requests to connect. Learn more at http://support.google.com/mail/bin/answer.py?answer=7720
[(10) *********.com. [XX.***.***.XX]:25: socket error]

*************************************************
How can we troubleshoot this issue

Thanks


This thread was automatically locked due to age.
  • 0
    Hi, CODE, and welcome to the User BB!

    First, check your configuration against Exchange with SMTP Proxy.  If you still have a problem, show us the related lines for one such delivery attempt in the UTM's SMTP log.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0
    CODE, since you don't see anything in the UTM logs the problem is obviously related with your front firewall settings or public DNS records.

    Check again your A and MX records and try to telnet to port 25 by the hostname from the outside.
Unfiltered HTML