Thread Info
  • State Suggested Answer
  • +4 person also asked this people also asked this
  • Locked Locked
  • Replies 13 replies
  • Answers 1 answer
  • Subscribers 37 subscribers
  • Views 29529 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

Problems sending email notifications from Sophos XG

floppyraid

Hi all.

 

Quick question, if you know the answer, skip everything below this line: Can I completely disable EVERYTHING regarding email scanning on the Sophos XG series?

 

We are using a Sophos XG 105 Rev 2, it shipped with SFOS 16.05.5-233 (according to the box). After numerous unsuccessful attempts at sending a test email I decided to go ahead and download the latest ISO and install it. To my surprise it was "HW-SFOS_16.05.5_MR-5-233". Anyway after a complete reinstall of the Sophos XG software the problem continues.

From reading online I see Sophos XGs are still having issues sending email via o365, so I gave up on trying to use smtp.office365.com as an external mailserver.
We have a client that is using a Sophos XG 210 running firmware version "SFOS 16.01.1", using the 'Built-in Email server' works fine for notification purposes. So I decided to configure this Sophos XG 105 the exact same way (using the same from/to email addresses) but to my amazement even this doesn't work --- with the 'Built-in email server' selected on our Sophos the emails get stuck in the SMTP queue on the device regardless of the MTA / Legacy mode settings. No matter what settings I put into the email scanning section of the sophos it continues to hold and queue notification emails I attempt to send, as if though it is trying to scan them. Another factor that may be contributing to this is I have not registered the device yet since I belive the actual installation date is a little over 30 days out and I don't want to waste a month+ off their license, so technically many of those additional services are configurable/running to some extent, but not fully functioning.

What is really weird is when I look at the email log, the queued emails are coming from a random port on loopback address for the source (that makes sense well enough) but the DESTINATION address is ":: :24"

I've kept a window open just running tail -f /var/tslog/awarrenmta.log just to see what was happening every time i click the 'test email' button and to my amazement i see these sorts of lines:

 

Mail Transaction Started from 172.0.0.1:41366 to 216.32.181.42:24



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

    I've got 1 XG that works and one that doesn't. The one that does work with O365 is one with a static IP on the WAN connection, so I have a connection filter in O365 to allow everything from that IP address.  The one that doesn't work, doesn't have a static IP, so I'm trying to use it with authentication.  I've tried every which way with TLS and SSL and ports, but I'm unable to get it working.  I came across another thread here that indicated that the SFOS couldn't handle the authentication, but I refuse to believe that, especially when its several revisions since that post.

    If anyone has any advice, I think we all would greatly benefit. My next step is to open a support ticket.

  • 0 in reply to JamesGolden

    You can relay via port 25 through O365 using your MX record as the SMTP server. I know, crazy right, but it's true.

  • 0 in reply to MrMojoRisin76

    Neither option works for me - has anyone else managed to get the Mail Server Settings to work with Office 365?

     

    Have tried using our MX record on port 25, but get error:

    Authentication method mismatch. Please confirm the authentication method support for LOGIN or PLAIN on the mail server

     

    Also tried using the settings, as recommended by Microsoft for sending messages from network devices, but without success.
    https://support.office.com/en-us/article/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-365-69f58e99-c550-4274-ad18-c805d654b4c4

    smtp.office365.com, port 587, StartTLS

     

    We have an account setup on Office 365 specifically to process auto-messages from devices like a firewall, and this system works with various printers, and even other firewalls (Watchg****d, ZyXEL, SonicWall), but it won't work with the simple parameters available on the XG.

    Can anyone offer any solution to this?

  • 0 in reply to mnorfolk

    We tried to set this up for a new client (XG125v3 SFOS 17.1.1 MR-1) doesn't work.

    Setup it up to use non Office 365 POP3 account and works every time.

    Tried using the "Inbuilt Server" didn't work. Rang Sophos support who advised that it didn't really mean inbuilt but it means an in house Exchange Server - Go Figure!!

    365 is so intrinsic to so many of us now and yet the XG boxes hardly seem aware of it - seem to prefer Google for everything. Lost a client due to this.

    Come on Sophos - You CAN do better!

  • 0 in reply to Ron Foster

    Out of frustration, I finally opened a ticket about this back in January. Here is the response I received:

    >  XG only supports AUTH plain for authentication. 

    > XG authentication to office365 is not possible. We would request you to post your request on site https://ideas.sophos.com/  which will be taken care directly with development team.  Idea already shared :ideas.sophos.com/.../32012101-email-notification (Kindly vote for this idea)

Reply Children
No Data