Can't send Test Email from Server Settings to Office 365

[andrewstanton]

Hi,

I'm trying to configure Email Settings in Vault Standard 10 Server and am getting the following message when clicking Test Settings...

--------------------------------------------------------------------------------------------------
Exception: The transport failed to connect to the server.

Inner Exception: Exception has been thrown by the target of an invocation.
Inner Exception: The transport failed to connect to the server.
--------------------------------------------------------------------------------------------------

Google tells me Office 365's SMTP requires TLS encryption (not SSL) which may be the underlying cause, but I can't tell. I've tried the following both with and without "Use SSL" but with no luck:
- SMTP Server: smtp.office365.com
- SMTP Port: 587
- Use SSL: Yes | No
- SMTP Auth User: [My Office 365 / Exchange Online email address]
- SMTP Password: [My Office 365 / Exchange Online password]

Any ideas? Do you need to update the server code to support TLS?

Thanks!
Andy.

[Tonya]

Hi Andy,

We do have a special client that we can provide you with that supports TLS 1.2/2.0. If you have this version installed, please email support@sourcegear.com and refer to this forum post.

If the new Vault client doesn't resolve the problem, we can troubleshoot from there.

Thanks,

Tonya

[Tonya]

I just discovered that this issue may have already been resolved in a newer version of the Vault Server.

Can you please log into Vault with the GUI Client and provide us with the details shown in Help -> Technical Support? We'd like to know what Vault Server version you have installed.

Thanks,

Tonya

[andrewstanton]

Hi,

I've just updated my Vault server (and clients) to:

-------------------------------------------------
About SourceGear Vault Standard
Version 10.0.2.936
-------------------------------------------------

But the email settings on the server still produce the same error when trying to send via SMTP / TLS to an Office 365 account.

I'm not sure in your other comment what you mean about a client that supports TLS 1.2/2.0, as it's the server email settings I'm trying to configure here and not the client..

Thanks,
Andy.

[Tonya]

Andy,

Yes, I apologize for the confusion with the client. Once I realized this was a server issue that's when I followed up with the request on the version information. I should have been more clear to disregard my initial response.

Can you please log in with a Vault GUI client and report back Help -> Technical Support. We'd like to know the .Net Framework version being used by the Vault Server.

Thanks,

Tonya

[Tonya]

Andy,

One of our developers has been doing some research and discovered that it looks like there's some new handshaking requirements in the SMTP protocol that was added for TLS, and it appears as if the SmtpClient used in Vault notifications is unable to negotiate this TLS configuration.

We have logged a bug to replace the underlying MS libraries with an updated one which can use these newer protocols to be implemented in a later release of Vault. I will link your forum post to the bug so that we notify you when the release is available.

Tonya

[andrewstanton]

Hi Tonya,

Thanks for getting it added to the bug list. FYI here is the Help->Technical Support info you requested:

-----------------------------------------------------------------------------------------
Client Information
Vault Standard Client Version: 10.0.2.936
.NET Framework Version: 2.0.50727.9035
Operating System: Microsoft Windows 10 Pro
Service Pack: 0.0
OS Version: 10.0.17763
Total Physical Memory: 4 GB
Time Zone: (UTC+00:00) Dublin, Edinburgh, Lisbon, London

Server Information
Server Version: 10.0.2.936
.NET Framework Version: 4.0.30319.42000
Operating System: Microsoft Windows Server 2016 Standard
Service Pack: 0.0
OS Version: 10.0.14393
Timezone: (UTC+00:00) Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2016 (SP1-GDR) (KB4458842) - 13.0.4224.16 (X64)
-----------------------------------------------------------------------------------------

Thanks,
Andy.

[Tonya]

Thank you Andy. I will pass this information along.

Tonya

[leowalter]

Having the same problem.

Here is my info:
Client Information
Vault Standard Client Version: 10.0.2.936
.NET Framework Version: 2.0.50727.8806
Operating System: Microsoft Windows Server 2016 Standard
Service Pack: 0.0
OS Version: 10.0.14393
Total Physical Memory: 4 GB
Time Zone: (UTC-04:00) Georgetown, La Paz, Manaus, San Juan

Server Information
Server Version: 10.0.2.936
.NET Framework Version: 4.0.30319.42000
Operating System: Microsoft Windows Server 2016 Standard
Service Pack: 0.0
OS Version: 10.0.14393
Timezone: (UTC-04:00) Georgetown, La Paz, Manaus, San Juan
SQL Version: Microsoft SQL Server 2017 (RTM-GDR) (KB4494351) - 14.0.2014.14 (X64)

[Tonya]

Thank you for letting us know and providing us with your details. Currently Vault SMTP does not support Office 365 with TLS at the moment. This has been logged and we will update this forum post when a fix has been applied.

Tonya

[andrewstanton]

Hi Tonya,

Was this bug ever addressed?

Thanks,
Andy.

[Tonya]

Hi Andy,

Not yet. We are currently working on a new release, so it's possible it will be included. At the moment, it's not clear what bugs/feature requests will be addressed yet.

Thank you for checking back in.

Tonya

[DAWPage]

Been a year and a half, any news on Office 365 integration?

[Tonya]

Hello again,

It's still a feature we have logged but has not yet been implemented. I will pass along your concern again as we are currently working on Vault 11.

Thanks,

Tonya

[siniawski.jj]

Hi Tonya,

Curious if there have been any updates on this? I am migrating my SG Vault instance to a new server and upgrading to the latest version 10.2.0
I require TLS and it doesnt appear to be working.

Thanks,
Justin