In Exchange you can set up a trusted adapter (IP address) that will accept SMTP directly into the mailserver either authenticated or unauthenticated.
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: 25 July 2017 21:42 To: ProFox Email List profox@leafe.com Subject: Re: Outlook 2016 security no longer allowing VFP app to send emails as it did in the past
On 2017-07-25 13:56, Ted Roche wrote:
On Tue, Jul 25, 2017 at 1:12 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
My client has Outlook 2016. At some point in the past, the Outlook version they had prior worked with the application that uses SMTP to send emails from it. I thought I recalled Microsoft tightening security over the years but that there was some (3rd party?) utility to get around the increased security blockage. Does anyone remember that and can comment on it?
I do remember it. In fact, I wrote about it quite a bit, a while ago, and even presented it at conferences. After teaching Outlook Automation, I then did a series on Email Without Outlook, since automating outlook is indistinguishable, in MSFT's view, from malware.
If your app is using SMTP, it shouldn't need Outlook, so what are you really doing, and what are you getting for error messages?
This isn't my app. It's from their Corporate affiliate. However, I used to work for that Corporate entity at one time and as such, I recall vaguely the idea behind the code. It offered SMTP, MAPI, and Extended MAPI. I'm not sure at this time of writing what the client is using but will find out.
So in short: this isn't code I can change. I am trying to make it work with the code from nearly 8 years ago.
[excessive quoting removed by server]