Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 26 subscribers
  • Views 3894 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

SPX Setup in XG v17 Assistance

WKEIT

 

I'm having trouble getting SPX encryption to work correctly with a newly deployed XG 310 running v17.0.3 (MR3).

I have under Email > Encryption: Default SPX Template -> Customized SPX Template

 

In the SPX Templates section, I have : Customized SPX Template; customized to my liking. As far as I understood it, this global spx template should activate when it sees the x-sophos-spx-encryption value yes. I had setup the exchange server rules to trigger activation of this header value, but after sending the test emails - looking at the headers, I can see the values set to yes, however, SPX did not activate.

 

On the other hand - if I apply my customized SPX template to an SMTP policy, all emails gets sent with SPX enabled.



This thread was automatically locked due to age.
  • 0

    The XG is very particular (because I think it's buggy) at what it sees.  In your exchange server rules, you need to have EXACTLY: Set the message header 'X-Sophos-SPX-Encrypt' to the value 'yes'.

    The caps do matter.  Also, one thing I found out but haven't done much testing to resolve is that - if you start a new email and send it with SPX, it will work just fine.  If you respond to an email with the trigger words in it, it will not re-encrypt.  Do test thoroughly and let me know if you find anything new.  The screenshot below is my Exchange Rules that is working.  I had worked with support and they were unable to get it work, but found out afterwards it was cause of the case-sensitive wording in the header that caused it to not work.

     

     

    Also, not sure if you've configured AD Authentication/LDAP - but it's also one of those deals where it is very case sensitive.  What I mean is, inside the "Search Queries" box, you gotta have ou=My OU,dc=domain,dc=tld  --- if you do OU=My OU,DC=domain,DC=tld, it doesn't work.

     

    Not sure if there's a fix for later version of XG-OS, but i'm on 17MR3 and these issues exists.

     

    GL.