Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
How to setup SMTP Mail for Outlook in NAV 5.0 SP1
ovestergaard
Member Posts: 3
Hi,
We are running NAV 5.0 SP1 and I need to setup SMTP Mail for Outlook through T409, F409, CU400.
I cannot get it to work, get error: Failure sending mail. Authentication failed because the remote party has closed the transport stream.
I have installed and registered Microsoft Navision Mail automation v. 7.3, am using smtp.office365.com, port 587.
I think the problem is that the Mail.Send call does not use TLS 1.2.
Any suggestions on how to force that in the C/AL code?
Are any hotfixes available?
Best regards Ole
We are running NAV 5.0 SP1 and I need to setup SMTP Mail for Outlook through T409, F409, CU400.
I cannot get it to work, get error: Failure sending mail. Authentication failed because the remote party has closed the transport stream.
I have installed and registered Microsoft Navision Mail automation v. 7.3, am using smtp.office365.com, port 587.
I think the problem is that the Mail.Send call does not use TLS 1.2.
Any suggestions on how to force that in the C/AL code?
Are any hotfixes available?
Best regards Ole
0
Answers
We are a partner, but takes me into unknown territory, will try it. For now, I have downloaded and used dotPeek and created a VS solution. Basically, need to change the .NET Framework to 4.6, I think, which will use TLS 1.2.