Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 28 subscribers
  • Views 3494 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

XG outbound email stuck in mail pool

Fred_B

I am in the process of routing the email over the XG. We have now two MX records in place. The XG MX records has the highest priority. Inbound is delivered just fine to the internal mail server. We are using MTA and followed https://docs.sophos.com/nsg/sophos-firewall/18.0/Help/en-us/webhelp/onlinehelp/nsg/sfos/learningContent/EmailConfigureEmailProtectionMTA.html#:~:text=Allow%20outbound%20emails,-You%20configure%20XG&text=In%20MTA%20mode%2C%20XG%20Firewall%20performs%20antivirus%20scanning%20on%20all,click%20Switch%20to%20MTA%20mode.

Problem is that the email coming from the internal mail server is accepted and queued for scanning but ends up failed in the mail pool for no apparent reason. In mail spool it says failed but in the log viewer there are no more status records for these emails after accepted and queued for scanning.  So were can we find what is going wrong?

A DNS lookup against 8.8.8.8 works. I switch to llegacy and back again to MTA which created a new firewall and linked NAT. My old one was not linked. Still does not deliver the outbound email. 

Firmware is SFOS 18.0.4 MR-4

Thnaks,

Fred



This thread was automatically locked due to age.
  • +1 in reply to Fred_B

    I solved the issue. The tcpdump showed that tls1.2 was used for the connection between the XG and the internal mailserver. It also showed ehlo and immediately followed by quit by the XG. This seems a time out issue on the XG. 

    I added the IP of the XG to the internal relay receivers of our email server so TLS is no longer needed,

    Now all email also the email stuck was released automatically.

  • 0 in reply to Fred_B

    Hi Fred,

    I'd been battling with error 'R=default_mx_router T=remote_smtp defer (110): connection timed out' for past 3 days until I came across this thread.

    I configured my mail server to relay to XG. I guess it solved problem as emails to the specific domains timing out no longer occurs and stuck mails in the mail pool after retrying are gone.

    Thanks very much.