Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 27 subscribers
  • Views 7844 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 notifications not working properly

cyberzeus

Hello,

Running Sophos XG v16.05.7 MR-7 w/ 2 interfaces - 1 LAN and 1 WAN.  

For the better part of 2 days, I have been battling an issue with trying to get e-mail notifications setup properly.  I have tested using both the built-in and external server options with slightly different observed behavior as noted below.

First off, nothing is received when using the built-in server.  In checking the /var/log/awarrenmta.log, it shows that the XG is initiating an SMTP connection using a source IP of 127.0.0.1 however, these connections are not being seen by the destination SMTP server.

Next, test e-mails sent via the external server are received as expected but the queued emails, when re-sent, are not received.  Also, when the test e-mails are sent, there is no output in any logfile including the /var/log/awarrenmta.log file mentioned above.  Interestingly, re-sending the queued emails does result in the same 127.0.0.1 connection attempt discussed above.

One last point - I have set the WAN gateway to send an email notification when it goes up and those notifications do come though as expected but no logged info regarding those notifications is found.

Any and all help is appreciated - Thanks.



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

    Hi,

    do you have a firewall rule for mail? Those settings you a configuring are only for the XG to send notifications not for clients or email servers.

    Is your mail server in-house or do your clients need to access external mail servers? There is a business rule mail template you can use.

    Ian

  • 0 in reply to rfcat_vk

    All of the e-mail clients and IMAP servers are external to and do not communicate via the XG so firewall rules should not play a role here. 

    Also, if the 127-net source IP is truly being used, then communication with an external server is impossible without NAT which should not be mandatory for SMTP comms.

    Therefore, the source = 127-net is either a bug or the system is lying to us.

  • 0 in reply to cyberzeus

    I was trying MTA and IPv6. The logs were full of failing to send :: :0 failing to send :: :24 failing to send 127.0.1:24, frozen messages, accepted for scanning but not progressing any further.

    In the end I deleted all the messages in the quarantine which stopped all the strange messages appearing the logs.

    Ian

Reply
  • 0 in reply to cyberzeus

    I was trying MTA and IPv6. The logs were full of failing to send :: :0 failing to send :: :24 failing to send 127.0.1:24, frozen messages, accepted for scanning but not progressing any further.

    In the end I deleted all the messages in the quarantine which stopped all the strange messages appearing the logs.

    Ian

Children
No Data