The issue appears when using port 465 - as described in the original thread.