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?
Thanks.
Redemption? Haven't used it since Office 2007, so couldn't tell you if it works in 2016 or not,
Fred
On Tue, Jul 25, 2017 at 10:12 AM, < 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?
Thanks.
[excessive quoting removed by server]
It does.
You may be confusing this with when the Outlook security model started throwing up an 'allow/deny' confirmation when an external programme attempts to create a message using Simple MAPI. A kludgy way around that is to install a utility called ClickYes which silently closes the Outlook dialog. A better way is to use something other than Simple MAPI. SMTP has nothing to do with Outlook, you're just connecting directly to a mail server (Exchange, whatever). Hosted Exchange on Office 365 does have limits on the rate at which you can submit emails and the number of submissions. This is to stop bulk emailing. If you want to do that, use Sendgrid or Mailjet etc.
On 2017-07-25 13:35, Alan Bourke wrote:
You may be confusing this with when the Outlook security model started throwing up an 'allow/deny' confirmation when an external programme attempts to create a message using Simple MAPI. A kludgy way around that is to install a utility called ClickYes which silently closes the Outlook dialog. A better way is to use something other than Simple MAPI. SMTP has nothing to do with Outlook, you're just connecting directly to a mail server (Exchange, whatever). Hosted Exchange on Office 365 does have limits on the rate at which you can submit emails and the number of submissions. This is to stop bulk emailing. If you want to do that, use Sendgrid or Mailjet etc.
Update: client is using Exchange server it looks like, and locally Outlook 2016. When I researched ClickYes above, it looks like that is for OLDER versions of Outlook.
???
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?
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.
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]
On 2017-07-26 04:27, Dave Crozier wrote:
In Exchange you can set up a trusted adapter (IP address) that will accept SMTP directly into the mailserver either authenticated or unauthenticated.
...but this is for SENDING email OUT, Dave. What you're saying above sounds like something for INCOMING mail. Plus, I don't know if they're using MS Exchange.
Am I misunderstanding?
Mike, Trusted adapters are for sending OUT so yes, I think you are!!!
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: 26 July 2017 15:57 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-26 04:27, Dave Crozier wrote:
In Exchange you can set up a trusted adapter (IP address) that will accept SMTP directly into the mailserver either authenticated or unauthenticated.
...but this is for SENDING email OUT, Dave. What you're saying above sounds like something for INCOMING mail. Plus, I don't know if they're using MS Exchange.
Am I misunderstanding?
[excessive quoting removed by server]
Ok I'll look into that. Thanks.
My Plan A was to simply use something like Thunderbird and integrate her application with that, as I know that worked as some point in time.
--Mike
On 2017-07-26 11:02, Dave Crozier wrote:
Mike, Trusted adapters are for sending OUT so yes, I think you are!!!
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: 26 July 2017 15:57 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-26 04:27, Dave Crozier wrote:
In Exchange you can set up a trusted adapter (IP address) that will accept SMTP directly into the mailserver either authenticated or unauthenticated.
...but this is for SENDING email OUT, Dave. What you're saying above sounds like something for INCOMING mail. Plus, I don't know if they're using MS Exchange.
Am I misunderstanding?
[excessive quoting removed by server]
If they were using SQL Server you could enable SQL Mail and from VFP hit a sproc in SQL Server that sends everything you need.
We use it internally for SPAM to ourselves about all the stuff that should be happening and isn't. As well as an email that is an alert about last nights DW run is now available for use.
On Wed, Jul 26, 2017 at 9:57 AM, < mbsoftwaresolutions@mbsoftwaresolutions.com> wrote:
On 2017-07-26 04:27, Dave Crozier wrote:
In Exchange you can set up a trusted adapter (IP address) that will accept SMTP directly into the mailserver either authenticated or unauthenticated.
...but this is for SENDING email OUT, Dave. What you're saying above sounds like something for INCOMING mail. Plus, I don't know if they're using MS Exchange.
Am I misunderstanding?
[excessive quoting removed by server]
On 2017-07-26 11:07, Stephen Russell wrote:
If they were using SQL Server you could enable SQL Mail and from VFP hit a sproc in SQL Server that sends everything you need.
We use it internally for SPAM to ourselves about all the stuff that should be happening and isn't. As well as an email that is an alert about last nights DW run is now available for use.
It's not SQLServer; it's a VFP9 app.
What Stephen was getting at was that whether you're using SQL Server as the database or not you can call a stored procedure in it to send emails.
On 2017-07-26 04:27, Dave Crozier wrote:
In Exchange you can set up a trusted adapter (IP address) that will accept SMTP directly into the mailserver either authenticated or unauthenticated.
Dave
Dave -- this is out of my normal zone. Is that IP address the workstation's IP address, or what/where?
tia, --Mike
The workstation IP address... it becomes trusted by Exchange.
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: 01 August 2017 20:05 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-26 04:27, Dave Crozier wrote:
In Exchange you can set up a trusted adapter (IP address) that will accept SMTP directly into the mailserver either authenticated or unauthenticated.
Dave
Dave -- this is out of my normal zone. Is that IP address the workstation's IP address, or what/where?
tia, --Mike
[excessive quoting removed by server]
On 2017-07-26 11:06, Alan Bourke wrote:
It offered SMTP, MAPI, and Extended MAPI.
If you can make it use Extended MAPI then you shouldn't have an issue sending with Outlook.
computer specs: Windows 10 Professional, 64-bit
I tried using Simple OR Extended MAPI but I get this error: https://www.screencast.com/t/OR1m3sOj4I
I also get that error OUTSIDE of the application trying to email. I created a test.txt file on the desktop, right-click and say "Send to Mail Recipient" and I get this message. I go into the Default Programs and Outlook 2016 is listed as the default mail program, so not sure why it's saying there is none.
Perhaps I should try CCleaner to clean up the registry?
CCleaner to me is the nuclear option with any problem.
It's more likely Win 10 trying to pimp it's crappy Windows Store apps.
Is it 32-bit Outlook?
Have you tried http://www.officetooltips.com/office/tips/how_to_modify_default_mail_client_...
On 2017-08-01 15:42, Alan Bourke wrote:
CCleaner to me is the nuclear option with any problem.
It's more likely Win 10 trying to pimp it's crappy Windows Store apps.
Is it 32-bit Outlook?
Have you tried http://www.officetooltips.com/office/tips/how_to_modify_default_mail_client_...
Not sure if 32- or 64-bit Outlook. Yes, I did try the File Association in Default Programs/Apps a few times. It says "Outlook 2016" yet when I right-click on a file in Explorer and say "Send to Mail Recipient" it still says that nothing is defined as the mail program as that screenshot showed.
On Tue, Aug 1, 2017 at 2:45 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
I also get that error OUTSIDE of the application trying to email. I created a test.txt file on the desktop, right-click and say "Send to Mail Recipient" and I get this message. I go into the Default Programs and Outlook 2016 is listed as the default mail program, so not sure why it's saying there is none.
Ace troubleshooting, there, Mike! Not a Fox problem. Searching on that exact error message on Google yields a number of good suggestions.
-- Ted Roche & Associates, LLC http://www.tedroche.com
On 2017-08-01 15:58, Ted Roche wrote:
On Tue, Aug 1, 2017 at 2:45 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
I also get that error OUTSIDE of the application trying to email. I created a test.txt file on the desktop, right-click and say "Send to Mail Recipient" and I get this message. I go into the Default Programs and Outlook 2016 is listed as the default mail program, so not sure why it's saying there is none.
Ace troubleshooting, there, Mike! Not a Fox problem. Searching on that exact error message on Google yields a number of good suggestions.
Thanks! I know the code behind the scenes is using a ShellExecute to launch the native Mailing program. I tried the Default Programs tip already as mentioned above. Will see if some others apply.
On 2017-08-01 15:58, Ted Roche wrote:
On Tue, Aug 1, 2017 at 2:45 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
I also get that error OUTSIDE of the application trying to email. I created a test.txt file on the desktop, right-click and say "Send to Mail Recipient" and I get this message. I go into the Default Programs and Outlook 2016 is listed as the default mail program, so not sure why it's saying there is none.
Ace troubleshooting, there, Mike! Not a Fox problem. Searching on that exact error message on Google yields a number of good suggestions.
Well, uninstalled (unintentionally! I tried to run a Repair and it just removed all of it apparently...ugh) and reinstalled Office365 and now I can right-click and the Send to Mail Recipient works; however, the non-MS app still fails. See https://www.screencast.com/t/na2eAK0FtB
This failed using Simple MAPI and Extended MAPI. (Those are my only 2 choices and 1 other which is directly with SMTP, but that fails too.)
Next step I guess is to use the "Trusted Adapter" tip that Dave gave. I'm just waiting for the user to call me back. Apparently there's no internet connection on that machine so I can't remotely connect. She's going to do a FaceTime call with me. Ugh. This sounds like I'll need a beer tonight.
On Fri, Aug 4, 2017 at 2:09 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Next step I guess is to use the "Trusted Adapter" tip that Dave gave. I'm just waiting for the user to call me back. Apparently there's no internet connection on that machine so I can't remotely connect.
Wait, wait! There's no internet connection on the machine, and... they're having trouble sending email?
Hmmm...
She's going to do a FaceTime call with me. Ugh. This sounds like I'll need a beer tonight.
Yep!
On 2017-08-04 15:17, Ted Roche wrote:
On Fri, Aug 4, 2017 at 2:09 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Next step I guess is to use the "Trusted Adapter" tip that Dave gave. I'm just waiting for the user to call me back. Apparently there's no internet connection on that machine so I can't remotely connect.
Wait, wait! There's no internet connection on the machine, and... they're having trouble sending email?
Hmmm...
She's going to do a FaceTime call with me. Ugh. This sounds like I'll need a beer tonight.
Yep!
Network buddy of mine at hockey tonight said that they've probably got port 80 blocked on that server (Small Business 2003 Server, I found out) as most savvy shops don't let people surf the web on the server. Makes sense. Plan next week is to get its IP address, and then use RDP from her workstation to remotely connect that way (all the while I'm using TeamViewer from my machine).
Trying to get this fixed, because her current vendor is a do-nothing kind of guy, and Corporate doesn't want to bother with this old app; but I say "Yes, it CAN work!" Her pain currently is that she has to MANUALLY EMAIL 78+ INVOICES WEEKLY (or Monthly? can't recall at this moment) whereas if this was working again, she could send all 78+ out of the app with just a couple clicks.
Hi Mike
I've seen that error before in my MAPI emailing programs on new workstations.
When Office is installed via a non-DVD method, then the WIN.INI file does not always get updated for MAPI.
Try adding this to that Windows 10 file:
C:\Windows\win.ini
[Mail] CMCDLLNAME32=mapi32.dll CMC=1 MAPI=1 MAPIX=1 MAPIXVER=1.0.0.1 OLEMessaging=1
On 8/1/2017 2:45 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
On 2017-07-26 11:06, Alan Bourke wrote:
It offered SMTP, MAPI, and Extended MAPI.
If you can make it use Extended MAPI then you shouldn't have an issue sending with Outlook.
computer specs: Windows 10 Professional, 64-bit
I tried using Simple OR Extended MAPI but I get this error: https://www.screencast.com/t/OR1m3sOj4I
I also get that error OUTSIDE of the application trying to email. I created a test.txt file on the desktop, right-click and say "Send to Mail Recipient" and I get this message. I go into the Default Programs and Outlook 2016 is listed as the default mail program, so not sure why it's saying there is none.
Perhaps I should try CCleaner to clean up the registry?
[excessive quoting removed by server]
Also Craig Boyd's Vfpexmapi.fll will quite happily send messages via Outlook because it uses Extended MAPI. The problem is with Simple MAPI.
Hi Mike,
Is the application you're referring to Sage PRO ERP (Accpac Pro Series, SBT Pro Series?)
If so, we ran into this same problem here with some installations of Outlook 2016.
i simply changed the automatically send SMTP commands to prompt for the mail and it worked.
.olemessage.Send(.T.)
It's a little bit slower than being able to automatically send the email but it was a solution.
Let me know if it is and I can help.
Philip B. Vicksburg, MI
On 7/25/2017 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?
Thanks.
[excessive quoting removed by server]
On 2017-07-31 10:41, Philip Borkholder wrote:
Hi Mike,
Is the application you're referring to Sage PRO ERP (Accpac Pro Series, SBT Pro Series?)
If so, we ran into this same problem here with some installations of Outlook 2016.
i simply changed the automatically send SMTP commands to prompt for the mail and it worked.
.olemessage.Send(.T.)
It's a little bit slower than being able to automatically send the email but it was a solution.
Let me know if it is and I can help.
Hi Philip,
No, it's not that app. It's an app from Sylvan Learning that I worked on back in 2007-2010.
-
Alan Bourke -
Dave Crozier -
Fred Taylor -
mbsoftwaresolutions＠mbsoftwaresolutions.com -
Philip Borkholder -
Stephen Russell -
Ted Roche