Small and medium business | Business Central, N...

NAV 2017 - Failure Sending mail.

(0) Share

Report

Posted on by kenthub

We started getting this error recently (within the past week) when sending out emails. Has anyone come across it yet. I've been googling it for a few days with no resolve.

8863.error.PNG

I suspect it's a TLS 1.2 issue but I'm unsure where/how to resolve it.

The server we are on is 2012R2 so TLS 1.2 is already enabled. I'm familiar with adding ServicePointManager.SecurityProtocol in visual studio but not C/AL.

When I try adding the dll to a dummy codeunit the option under DotNet > System.Net, the dll does not exist.

When I review our office365 settings online it shows most of the mailboxes we use on NAV are sending using 1.0

Any advice on how to force TLS 1.2 in NAV 2017?

I have the same question (0)

All responses (12)

Answers (0)

Suggested answer

Manan_Shah 1,459 on at

Like (0)

Report

Hello,

Please check your office 365 setting for define mail id on SMTP setup page. Need to enable 3rd party application permission, so when Nav try to send mail using office 365 mail id it's allow to send mail.

Verify your define ports and server details on SMTP setup page for reference please check below details.

Server Address: smtp.office365.com

Username: Your Office 365 Address (e.g. example@yourdomain.com)

Password: Your Office 365 Password

Port Number: 587 (With TLS)

Authentication: Required

Please verify the reply if it answers your query

Best Regards,

Manan Shah

Was this reply helpful? Yes No
kenthub on at

Like (0)

Report

We have all the settings entered for this. It's very random. Sometimes the emails go through, and then sometimes they don't.

Was this reply helpful? Yes No
Suggested answer

Marco Mels on at

Like (0)

Report

Hello,

Please do take a look here:

cloudblogs.microsoft.com/.../

Thanks.

Was this reply helpful? Yes No
kenthub on at

Like (0)

Report

Thanks, I've reviewed the article and turned off the TLS 1.0 & TLS 1.1 from internet options on the server to try and force it to go through TLS 1.2. Hopefully, that works.

Was this reply helpful? Yes No
Sivapragas 10 on at

Like (0)

Report

Did it work ?

Was this reply helpful? Yes No
Suggested answer

Marco Mels on at

Like (0)

Report

Hello,

If you are running latest CU for Dynamics NAV 2017 and you are still not able to send email via Dynamics NAV 2017, it may well be that Exchange Online deprecated basic authentication and you are required to use OAUTH as the authentication method for sending SMTP. Currently not all Dynamics NAV releases do support OAUTH for SMTP.

docs.microsoft.com/.../exchange-online-basic-auth-deprecated

Thanks.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,681 Super User 2025 Season 2 on at

Like (0)

Report

Hi, is it possible that the problem is with the Application Server OS? You can download the same CU of NAV, install it locally, and test it with the same settings.

Hope this will help.

Thanks.

ZHU

Was this reply helpful? Yes No
kenthub on at

Like (0)

Report

No that didn't solve the problem.

Was this reply helpful? Yes No
kenthub on at

Like (0)

Report

We are running the first version of 2017 so we plan to upgrade to the latest August Release. Hopefully, something in the dll for that codeunit will work. I'm not sure if calling and setting the security protocol to TLS 1.2 will do anything at this point. I appreciate the help in getting closer to the solution. I have high hopes this upgrade will work. We plan to migrate to the latest of business central, but that is a long way off :/

Was this reply helpful? Yes No
Suggested answer

Marco Mels on at

Like (0)

Report

Hello,

Tls1.2 is required when connecting to Exchange Online. We added support for Tls 1.2 in a later release. This sure is a requirement for this functionality.

RTM build of Dynamics NAV 2017 does not have this support built in. Another requirement is to also ensure your .NET Framework is up to date.

Thanks.

Was this reply helpful? Yes No