On 2017-07-25 13:56, Ted Roche wrote:
On Tue, Jul 25, 2017 at 1:12 PM,
<[email protected]> 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.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
