So, here at work - my IT guy let us know there is this big Looming Deadline by Micro$oft - to kill off a bunch of older applications. Including older Windows servers, and other older Windows apps - including Win10. And, now it's become a little bit of a Scramble. Even just upgrading my work PC from 10 to 11 was a bit of a nightmare the past few days - taking most of Fri. & Today to try and solve issues that were causing the Upgrade to Fail. I would NOT be exaggerating to say that I had to try the install somewhere between 7 - 10 times in the past 2 days before we got success.
It was very frustrating to say the least.
And, now others on the IT team here are also going to be going thru the process of upgrading. Of course, we are upgrading 1st before the whole co. - as we need to find out where some problems reside.
For instance, we do email transmissions as part of our database system applications. Most of the emails are transmitted internally. A lot of the emails are done via Office Automation. However, that requires Outlook being installed on a PC. That being said, there are a number of computers in the production facility that have this kind of TimeClock app on it - which is used to track production of parts - and allows the folks working on the parts to submit their hours into the system. As such, many different people would use a single computer. So, in fact - no One person actually logs into the PC with the Timeclock. As such, the Timeclock machines do NOT have Outlook. So, for the Timeclock application we used VFPWinSock to transmit emails instead of office automation.
Now, with the conversion to Win11 - it seems the VFPWinSock application code is throwing an error. And, we may need to find another method for sending emails.
I'm sure other folks here in the forum, that have older VFP apps - and are running on Win10 machines that soon need to switch to Win11 - especially in regards to businesses.
As such, I wanted to start this thread - not only for input on our own issue w/Emails & VFPWinSock. But, I'd also like to know the experiences of others here - in regards to Switching from Win10 to Win11 - and find out if there are other Gotchas out there that I should be made aware of!
Thanks in advance for the input!
-Kurt
- And, we may need to find another method for sending emails.*<<
Chilkat, and perhaps ChilkatVFP to facilitate.
Contact me.
Bill Anderson
On Mon, Jul 21, 2025 at 2:28 PM Kurt Wendt kwendt@pakoinc.com wrote:
So, here at work - my IT guy let us know there is this big Looming Deadline by Micro$oft - to kill off a bunch of older applications. Including older Windows servers, and other older Windows apps - including Win10. And, now it's become a little bit of a Scramble. Even just upgrading my work PC from 10 to 11 was a bit of a nightmare the past few days - taking most of Fri. & Today to try and solve issues that were causing the Upgrade to Fail. I would NOT be exaggerating to say that I had to try the install somewhere between 7 - 10 times in the past 2 days before we got success.
It was very frustrating to say the least.
And, now others on the IT team here are also going to be going thru the process of upgrading. Of course, we are upgrading 1st before the whole co.
- as we need to find out where some problems reside.
For instance, we do email transmissions as part of our database system applications. Most of the emails are transmitted internally. A lot of the emails are done via Office Automation. However, that requires Outlook being installed on a PC. That being said, there are a number of computers in the production facility that have this kind of TimeClock app on it - which is used to track production of parts - and allows the folks working on the parts to submit their hours into the system. As such, many different people would use a single computer. So, in fact - no One person actually logs into the PC with the Timeclock. As such, the Timeclock machines do NOT have Outlook. So, for the Timeclock application we used VFPWinSock to transmit emails instead of office automation.
Now, with the conversion to Win11 - it seems the VFPWinSock application code is throwing an error. And, we may need to find another method for sending emails.
I'm sure other folks here in the forum, that have older VFP apps - and are running on Win10 machines that soon need to switch to Win11 - especially in regards to businesses.
As such, I wanted to start this thread - not only for input on our own issue w/Emails & VFPWinSock. But, I'd also like to know the experiences of others here - in regards to Switching from Win10 to Win11 - and find out if there are other Gotchas out there that I should be made aware of!
Thanks in advance for the input!
-Kurt
[excessive quoting removed by server]
We're still using WestWind for email and SFTP in VFP9, on Windows 10 and 11, with no issues.
On Monday, July 21st, 2025 at 5:41 PM, Bill Anderson billand88@gmail.com wrote:
- And, we may need to find another method for sending emails.*<<
Chilkat, and perhaps ChilkatVFP to facilitate.
Contact me.
Bill Anderson
On Mon, Jul 21, 2025 at 2:28 PM Kurt Wendt kwendt@pakoinc.com wrote:
So, here at work - my IT guy let us know there is this big Looming Deadline by Micro$oft - to kill off a bunch of older applications. Including older Windows servers, and other older Windows apps - including Win10. And, now it's become a little bit of a Scramble. Even just upgrading my work PC from 10 to 11 was a bit of a nightmare the past few days - taking most of Fri. & Today to try and solve issues that were causing the Upgrade to Fail. I would NOT be exaggerating to say that I had to try the install somewhere between 7 - 10 times in the past 2 days before we got success.
It was very frustrating to say the least.
And, now others on the IT team here are also going to be going thru the process of upgrading. Of course, we are upgrading 1st before the whole co.
- as we need to find out where some problems reside.
For instance, we do email transmissions as part of our database system applications. Most of the emails are transmitted internally. A lot of the emails are done via Office Automation. However, that requires Outlook being installed on a PC. That being said, there are a number of computers in the production facility that have this kind of TimeClock app on it - which is used to track production of parts - and allows the folks working on the parts to submit their hours into the system. As such, many different people would use a single computer. So, in fact - no One person actually logs into the PC with the Timeclock. As such, the Timeclock machines do NOT have Outlook. So, for the Timeclock application we used VFPWinSock to transmit emails instead of office automation.
Now, with the conversion to Win11 - it seems the VFPWinSock application code is throwing an error. And, we may need to find another method for sending emails.
I'm sure other folks here in the forum, that have older VFP apps - and are running on Win10 machines that soon need to switch to Win11 - especially in regards to businesses.
As such, I wanted to start this thread - not only for input on our own issue w/Emails & VFPWinSock. But, I'd also like to know the experiences of others here - in regards to Switching from Win10 to Win11 - and find out if there are other Gotchas out there that I should be made aware of!
Thanks in advance for the input!
-Kurt
[excessive quoting removed by server]
No issues so far - with VFP9/VFP10 on Windows 11.
On 22/07/2025 05:27, Vincent Teachout wrote:
We're still using WestWind for email and SFTP in VFP9, on Windows 10 and 11, with no issues.
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
We have several applications running on VFP9, and started installing them a few years ago as clients began switching to Win 11 laptops and servers. No problems at all, aside from having to use ODBCAD32 if you're using ODBC.
On Monday, July 21st, 2025 at 5:02 PM, Kurt Wendt kwendt@pakoinc.com wrote:
So, here at work - my IT guy let us know there is this big Looming Deadline by Micro$oft - to kill off a bunch of older applications. Including older Windows servers, and other older Windows apps - including Win10. And, now it's become a little bit of a Scramble. Even just upgrading my work PC from 10 to 11 was a bit of a nightmare the past few days - taking most of Fri. & Today to try and solve issues that were causing the Upgrade to Fail. I would NOT be exaggerating to say that I had to try the install somewhere between 7 - 10 times in the past 2 days before we got success.
It was very frustrating to say the least.
And, now others on the IT team here are also going to be going thru the process of upgrading. Of course, we are upgrading 1st before the whole co. - as we need to find out where some problems reside.
For instance, we do email transmissions as part of our database system applications. Most of the emails are transmitted internally. A lot of the emails are done via Office Automation. However, that requires Outlook being installed on a PC. That being said, there are a number of computers in the production facility that have this kind of TimeClock app on it - which is used to track production of parts - and allows the folks working on the parts to submit their hours into the system. As such, many different people would use a single computer. So, in fact - no One person actually logs into the PC with the Timeclock. As such, the Timeclock machines do NOT have Outlook. So, for the Timeclock application we used VFPWinSock to transmit emails instead of office automation.
Now, with the conversion to Win11 - it seems the VFPWinSock application code is throwing an error. And, we may need to find another method for sending emails.
I'm sure other folks here in the forum, that have older VFP apps - and are running on Win10 machines that soon need to switch to Win11 - especially in regards to businesses.
As such, I wanted to start this thread - not only for input on our own issue w/Emails & VFPWinSock. But, I'd also like to know the experiences of others here - in regards to Switching from Win10 to Win11 - and find out if there are other Gotchas out there that I should be made aware of!
Thanks in advance for the input!
-Kurt
[excessive quoting removed by server]
As such, I wanted to start this thread - not only for input on our own issue w/Emails & VFPWinSock. But, I'd also like to know the experiences of others here - in regards to Switching from Win10 to Win11 - and find out if there are other Gotchas out there that I should be made aware of!
I’ve been on Windows 11 for a while, but haven’t noticed major issues when moving from Windows 10.
We use different libraries for sending mail. Recently we added MailKit with the Microsoft MSAL library when Microsoft disabled SMTP with user name and password. Instead they are requiring OAuth2 now. We have a little helper class written in C# and use wwDotNetBridge to call it. You could probably do it entirely in wwDotNetBridge, though. MailKit allows for synchronous operations. MSAL is asynchronous only.
— Christof
We've had out own fleet of hardware on Windows 11 for years, as have most of our customers. No issues. It's an iteration of Windows 10, nothing like the re-engineering between XP and 7 for example.
Thank you to EVERYONE for all your input on this - I Really appreciate it!!!
One thing I didn't mention in my original posting - was that a Free email solution is better, since, at this point - putting money towards VFP is not a great idea - as we prefer to put money towards converting our systems out of FoxPro. As is, they have been putting money into converting things out - including things like reports in C# by purchasing a 3rd party library, QuestPDF.
Folks here are discussing this right now - in regards to all the replies and how to handle email...
________________________________________ From: ProFox profox-bounces@leafe.com on behalf of Alan Bourke alanpbourke@fastmail.fm Sent: Tuesday, July 22, 2025 4:29 AM To: profox@leafe.com profox@leafe.com; profoxtech@leafe.com profoxtech@leafe.com Subject: Re: Win11 Deadline & FoxPro Apps!
We've had out own fleet of hardware on Windows 11 for years, as have most of our customers. No issues. It's an iteration of Windows 10, nothing like the re-engineering between XP and 7 for example. -- Alan Bourke alanpbourke (at) fastmail (dot) fm
I think it's clear that your issue is not really W10 vs W11; it's how to handle SMTP in the modern world. 😊
Many, if not all, of the email providers are now requiring authentication methods that are more stringent then the wild west of open relaying, or even basic authentication with creds. This means calling APIs, using secrets, etc. All that modern stuff that we have not historically needed. And many now require proper SPF, DMARC, & DKIM just to make it more fun.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Kurt Wendt Sent: Tuesday, July 22, 2025 9:04 AM To: profoxtech@leafe.com Subject: Re: Win11 Deadline & FoxPro Apps!
Thank you to EVERYONE for all your input on this - I Really appreciate it!!!
One thing I didn't mention in my original posting - was that a Free email solution is better, since, at this point - putting money towards VFP is not a great idea - as we prefer to put money towards converting our systems out of FoxPro. As is, they have been putting money into converting things out - including things like reports in C# by purchasing a 3rd party library, QuestPDF.
Folks here are discussing this right now - in regards to all the replies and how to handle email...
V2VsbCAtIFJLIC0gdGhlcmUgZGVmaW5pdGVseSBpcyBhIFdpbjExIHJlbGF0aW9uIHRvIHRoZSBwcm9ibGVtLiBCZWNhdXNlLCBzYW1lIGNvZGUgdGhhdCByYW4gdW5kZXIgV2luMTAgLSBpdCBmYWlscyB0byBydW4gdW5kZXIgV2luMTEgLSBhcyBpdCBzZWVtcyB0aGF0IFdpbjExIGJyb2tlIHRoZSBWRlBXaW5Tb2NrIGNvZGUuDQoNCkEgY291cGxlIG9mIHdlZWtzIGFnbywgd2hlbiB0aGlzIGFsbCBzdGFydGVkIC0gSSBhY3R1YWxseSBhc2tlZCBDbGF1ZGUgZm9yIGhlbHAuIEhlIGdhdmUgbWUgYSBidW5jaCBvZiBkaWZmZXJlbnQgb3B0aW9ucy4gSSB0cmllZCB0aGlzIG9wdGlvbiB0aGF0IHVzZXMgQ0RPIC0gYnV0LCB0aGUgY29kZSB3YXNuJ3Qgd29ya2luZy4gVG9kYXkgSSB3ZW50IGJhY2sgdG8gdGhhdCBjb2RlLCBwbGF5ZWQgYXJvdW5kIHdpdGggaXQgYW5kIGNoYW5nZSBzb21lIHBhcmFtZXRlcnMgLSBhbmQgbm93IGl0J3Mgd29ya2luZy4gVGhpcyBpcyBlc3NlbnRpYWxseSB0aGF0IGNvZGU6DQoqIFRoZSBjb2RlIGZyb20gdGhpcyBUZXN0IHdhcyBvcmlnaW5hbGx5IGdpdmVuIHRvIG1lIGZyb20gQ2xhdWRlIC0gdGhlbiBJIHVwZGF0ZWQgc29tZSBTZXR0aW5ncyAgLSBLSFcgLSA3LzIyLzI1DQoNCkxPQ0FMIG9NZXNzYWdlLCBvQ29uZmlnDQpvTWVzc2FnZSA9IENSRUFURU9CSkVDVCgiQ0RPLk1lc3NhZ2UiKQ0Kb0NvbmZpZyA9IENSRUFURU9CSkVDVCgiQ0RPLkNvbmZpZ3VyYXRpb24iKQ0KDQoqIENvbmZpZ3VyZSBTTVRQIHNldHRpbmdzDQpXSVRIIG9Db25maWcuRmllbGRzDQogICAgLkl0ZW0oImh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vY2RvL2NvbmZpZ3VyYXRpb24vc2VuZHVzaW5nIikgPSAyICYmIFdhcy4uLiAyDQogICAgLkl0ZW0oImh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vY2RvL2NvbmZpZ3VyYXRpb24vc210cHNlcnZlciIpID0gIm1haWwucGFrb2luYy5jb20iDQogICAgLkl0ZW0oImh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vY2RvL2NvbmZpZ3VyYXRpb24vc210cHNlcnZlcnBvcnQiKSA9IDI1ICYmIFdhcyAuLi41ODcNCiAgICAuSXRlbSgiaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9jZG8vY29uZmlndXJhdGlvbi9zbXRwYXV0aGVudGljYXRlIikgPSAxDQogICAgLkl0ZW0oImh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5jb20vY2RvL2NvbmZpZ3VyYXRpb24vc2VuZHVzZXJuYW1lIikgPSAiIg0KICAgIC5JdGVtKCJodHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL2Nkby9jb25maWd1cmF0aW9uL3NlbmRwYXNzd29yZCIpID0gIiINCiAgICAuSXRlbSgiaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9jZG8vY29uZmlndXJhdGlvbi9zbXRwdXNlc3NsIikgPSAuRi4gICYmIFdhcyAuVC4NCiAgICAuVXBkYXRlKCkNCkVORFdJVEgNCg0KKiBTZW5kIHRoZSBlbWFpbA0KV0lUSCBvTWVzc2FnZQ0KICAgIC5Db25maWd1cmF0aW9uID0gb0NvbmZpZw0KICAgIC5UbyA9ICJhYmxhY2ttb25AcGFrb2luYy5jb20iDQogICAgLkZyb20gPSAia3dlbmR0QHBha29pbmMuY29tIg0KICAgIC5TdWJqZWN0ID0gIkNETyBUZXN0IFN1YmplY3QiDQogICAgLlRleHRCb2R5ID0gIkNETyBFbWFpbCBUZXN0IG1lc3NhZ2UgYm9keSINCiAgICAuU2VuZCgpDQpFTkRXSVRIDQoNCkJ1dCwgeWVzIC0gaW4gcmVnYXJkcyB0byBhdXRoZW50aWNhdGlvbiAtIHdoZW4gd2UgZnVydGhlciB1cGdyYWRlIHRoaW5ncyBsaWtlIEVtYWlsIHNlcnZlciAtIHRoaW5ncyBtYXliZSBicmVhayBhZ2Fpbi4gU2luY2UsIGFzIHlvdSBzYWlkIC0gImF1dGhlbnRpY2F0aW9uIG1ldGhvZHMgdGhhdCBhcmUgbW9yZSBzdHJpbmdlbnQiIC0gYW5kIG15IElUIGd1eSBhbHNvIG1hZGUgbWUgYXdhcmUgb2YgdGhpcy4gVGhhdCB0aGlzIGNvZGUgY291bGQgc3RpbGwgYnJlYWsgYWdhaW4uDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiBQcm9Gb3ggPHByb2ZveC1ib3VuY2VzQGxlYWZlLmNvbT4gb24gYmVoYWxmIG9mIFJpY2hhcmQgS2F5ZSA8cmtheWVAaW52YWx1YWJsZS5jb20+DQpTZW50OiBUdWVzZGF5LCBKdWx5IDIyLCAyMDI1IDE6MDAgUE0NClRvOiBwcm9mb3hAbGVhZmUuY29tIDxwcm9mb3hAbGVhZmUuY29tPg0KU3ViamVjdDogUkU6IFdpbjExIERlYWRsaW5lICYgRm94UHJvIEFwcHMhDQoNCkkgdGhpbmsgaXQncyBjbGVhciB0aGF0IHlvdXIgaXNzdWUgaXMgbm90IHJlYWxseSBXMTAgdnMgVzExOyBpdCdzIGhvdyB0byBoYW5kbGUgU01UUCBpbiB0aGUgbW9kZXJuIHdvcmxkLiDwn5iKDQoNCk1hbnksIGlmIG5vdCBhbGwsIG9mIHRoZSBlbWFpbCBwcm92aWRlcnMgYXJlIG5vdyByZXF1aXJpbmcgYXV0aGVudGljYXRpb24gbWV0aG9kcyB0aGF0IGFyZSBtb3JlIHN0cmluZ2VudCB0aGVuIHRoZSB3aWxkIHdlc3Qgb2Ygb3BlbiByZWxheWluZywgb3IgZXZlbiBiYXNpYyBhdXRoZW50aWNhdGlvbiB3aXRoIGNyZWRzLiBUaGlzIG1lYW5zIGNhbGxpbmcgQVBJcywgdXNpbmcgc2VjcmV0cywgZXRjLiBBbGwgdGhhdCBtb2Rlcm4gc3R1ZmYgdGhhdCB3ZSBoYXZlIG5vdCBoaXN0b3JpY2FsbHkgbmVlZGVkLiBBbmQgbWFueSBub3cgcmVxdWlyZSBwcm9wZXIgU1BGLCBETUFSQywgJiBES0lNIGp1c3QgdG8gbWFrZSBpdCBtb3JlIGZ1bi4NCg0KLS0NCg0KcmsNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFByb2ZveFRlY2ggPHByb2ZveHRlY2gtYm91bmNlc0BsZWFmZS5jb20+IE9uIEJlaGFsZiBPZiBLdXJ0IFdlbmR0DQpTZW50OiBUdWVzZGF5LCBKdWx5IDIyLCAyMDI1IDk6MDQgQU0NClRvOiBwcm9mb3h0ZWNoQGxlYWZlLmNvbQ0KU3ViamVjdDogUmU6IFdpbjExIERlYWRsaW5lICYgRm94UHJvIEFwcHMhDQoNClRoYW5rIHlvdSB0byBFVkVSWU9ORSBmb3IgYWxsIHlvdXIgaW5wdXQgb24gdGhpcyAtIEkgUmVhbGx5IGFwcHJlY2lhdGUgaXQhISENCg0KT25lIHRoaW5nIEkgZGlkbid0IG1lbnRpb24gaW4gbXkgb3JpZ2luYWwgcG9zdGluZyAtIHdhcyB0aGF0IGEgRnJlZSBlbWFpbCBzb2x1dGlvbiBpcyBiZXR0ZXIsIHNpbmNlLCBhdCB0aGlzIHBvaW50IC0gcHV0dGluZyBtb25leSB0b3dhcmRzIFZGUCBpcyBub3QgYSBncmVhdCBpZGVhIC0gYXMgd2UgcHJlZmVyIHRvIHB1dCBtb25leSB0b3dhcmRzIGNvbnZlcnRpbmcgb3VyIHN5c3RlbXMgb3V0IG9mIEZveFByby4gQXMgaXMsIHRoZXkgaGF2ZSBiZWVuIHB1dHRpbmcgbW9uZXkgaW50byBjb252ZXJ0aW5nIHRoaW5ncyBvdXQgLSBpbmNsdWRpbmcgdGhpbmdzIGxpa2UgcmVwb3J0cyBpbiBDIyBieSBwdXJjaGFzaW5nIGEgM3JkIHBhcnR5IGxpYnJhcnksIFF1ZXN0UERGLg0KDQpGb2xrcyBoZXJlIGFyZSBkaXNjdXNzaW5nIHRoaXMgcmlnaHQgbm93IC0gaW4gcmVnYXJkcyB0byBhbGwgdGhlIHJlcGxpZXMgYW5kIGhvdyB0byBoYW5kbGUgZW1haWwuLi4NCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KUG9zdCBNZXNzYWdlcyB0bzogUHJvRm94QGxlYWZlLmNvbQ0KU3Vic2NyaXB0aW9uIE1haW50ZW5hbmNlOiBodHRwczovL21haWwubGVhZmUuY29tL21haWxtYW4vbGlzdGluZm8vcHJvZm94DQpPVC1mcmVlIHZlcnNpb24gb2YgdGhpcyBsaXN0OiBodHRwczovL21haWwubGVhZmUuY29tL21haWxtYW4vbGlzdGluZm8vcHJvZm94dGVjaA0KU2VhcmNoYWJsZSBBcmNoaXZlOiBodHRwczovL2xlYWZlLmNvbS9hcmNoaXZlcw0KVGhpcyBtZXNzYWdlOiBodHRwczovL2xlYWZlLmNvbS9hcmNoaXZlcy9ieU1JRC9NVzRQUjEwTUI2NTg0RTFDOUY1NzQ3NEU2MkUzNTM5MjZEMjVDQUBNVzRQUjEwTUI2NTg0Lm5hbXByZDEwLnByb2Qub3V0bG9vay5jb20NCioqIEFsbCBwb3N0aW5ncywgdW5sZXNzIGV4cGxpY2l0bHkgc3RhdGVkIG90aGVyd2lzZSwgYXJlIHRoZSBvcGluaW9ucyBvZiB0aGUgYXV0aG9yLCBhbmQgZG8gbm90IGNvbnN0aXR1dGUgbGVnYWwgb3IgbWVkaWNhbCBhZHZpY2UuIFRoaXMgc3RhdGVtZW50IGlzIGFkZGVkIHRvIHRoZSBtZXNzYWdlcyBmb3IgdGhvc2UgbGF3eWVycyB3aG8gYXJlIHRvbyBzdHVwaWQgdG8gc2VlIHRoZSBvYnZpb3VzLg0K--- StripMime Report -- processed MIME parts ---multipart/alternative text/plain (text body -- kept) text/html---
Darn - Oops - trying again...
Well - RK - there definitely is a Win11 relation to the problem. Because, same code that ran under Win10 - it fails to run under Win11 - as it seems that Win11 broke the VFPWinSock code.
A couple of weeks ago, when this all started - I actually asked Claude for help. He gave me a bunch of different options. I tried this option that uses CDO - but, the code wasn't working. Today I went back to that code, played around with it and change some parameters - and now it's working. This is essentially that code: * The code from this Test was originally given to me from Claude - then I updated some Settings - KHW - 7/22/25
LOCAL oMessage, oConfig oMessage = CREATEOBJECT("CDO.Message") oConfig = CREATEOBJECT("CDO.Configuration")
* Configure SMTP settings WITH oConfig.Fields .Item("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2 && Was... 2 .Item("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "mail.pakoinc.com" .Item("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25 && Was ...587 .Item("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate") = 1 .Item("http://schemas.microsoft.com/cdo/configuration/sendusername") = "" .Item("http://schemas.microsoft.com/cdo/configuration/sendpassword") = "" .Item("http://schemas.microsoft.com/cdo/configuration/smtpusessl") = .F. && Was .T. .Update() ENDWITH
* Send the email WITH oMessage .Configuration = oConfig .To = "ablackmon@pakoinc.com" .From = "kwendt@pakoinc.com" .Subject = "CDO Test Subject" .TextBody = "CDO Email Test message body" .Send() ENDWITH
But, yes - in regards to authentication - when we further upgrade things like Email server - things maybe break again. Since, as you said - "authentication methods that are more stringent" - and my IT guy also made me aware of this. That this code could still break again.
________________________________________ From: ProFox profox-bounces@leafe.com on behalf of Richard Kaye rkaye@invaluable.com Sent: Tuesday, July 22, 2025 1:00 PM To: profox@leafe.com profox@leafe.com Subject: RE: Win11 Deadline & FoxPro Apps!
I think it's clear that your issue is not really W10 vs W11; it's how to handle SMTP in the modern world. 😊
Many, if not all, of the email providers are now requiring authentication methods that are more stringent then the wild west of open relaying, or even basic authentication with creds. This means calling APIs, using secrets, etc. All that modern stuff that we have not historically needed. And many now require proper SPF, DMARC, & DKIM just to make it more fun. -- rk
Sorry, Kurt, I don't use CDO. I do know that besides the OS changes impacting you, email handling is rapidly changing as well.
Personally I think w00dy or Christof or any of the rest of the fine folk on this list are better sources for VFP expertise than Claude. 😊 Maybe not quite as available, though...
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Kurt Wendt Sent: Tuesday, July 22, 2025 1:13 PM To: profoxtech@leafe.com Subject: Re: Win11 Deadline & FoxPro Apps!
Darn - Oops - trying again...
Well - RK - there definitely is a Win11 relation to the problem. Because, same code that ran under Win10 - it fails to run under Win11 - as it seems that Win11 broke the VFPWinSock code.
A couple of weeks ago, when this all started - I actually asked Claude for help. He gave me a bunch of different options. I tried this option that uses CDO - but, the code wasn't working. Today I went back to that code, played around with it and change some parameters - and now it's working. This is essentially that code: * The code from this Test was originally given to me from Claude - then I updated some Settings - KHW - 7/22/25
LOCAL oMessage, oConfig oMessage = CREATEOBJECT("CDO.Message") oConfig = CREATEOBJECT("CDO.Configuration")
* Configure SMTP settings WITH oConfig.Fields .Item("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2 && Was... 2 .Item("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "mail.pakoinc.com" .Item("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25 && Was ...587 .Item("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate") = 1 .Item("http://schemas.microsoft.com/cdo/configuration/sendusername") = "" .Item("http://schemas.microsoft.com/cdo/configuration/sendpassword") = "" .Item("http://schemas.microsoft.com/cdo/configuration/smtpusessl") = .F. && Was .T. .Update() ENDWITH
* Send the email WITH oMessage .Configuration = oConfig .To = "ablackmon@pakoinc.com" .From = "kwendt@pakoinc.com" .Subject = "CDO Test Subject" .TextBody = "CDO Email Test message body" .Send() ENDWITH
But, yes - in regards to authentication - when we further upgrade things like Email server - things maybe break again. Since, as you said - "authentication methods that are more stringent" - and my IT guy also made me aware of this. That this code could still break again.
________________________________________ From: ProFox profox-bounces@leafe.com on behalf of Richard Kaye rkaye@invaluable.com Sent: Tuesday, July 22, 2025 1:00 PM To: profox@leafe.com profox@leafe.com Subject: RE: Win11 Deadline & FoxPro Apps!
I think it's clear that your issue is not really W10 vs W11; it's how to handle SMTP in the modern world. 😊
Many, if not all, of the email providers are now requiring authentication methods that are more stringent then the wild west of open relaying, or even basic authentication with creds. This means calling APIs, using secrets, etc. All that modern stuff that we have not historically needed. And many now require proper SPF, DMARC, & DKIM just to make it more fun. -- rk
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/BY5PR13MB3843686F5A5E18EA368FE15DC35CA@BY5P... ** 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.
Thanks again RK for the follow up. Yes, the emailing handling and more stringent authentication has indeed been discussed by Tony our IT guy. I looking for OAuth2 related coding for VFP - he actually stumbled upon ChilKat - and discussed the potential need of ChilKat with our manager. So, it is indeed possible we may go the ChilKat route as a better more solid solution - since that CDO code below will most probably break during the email server upgrading.
-K ________________________________ From: ProFox profox-bounces@leafe.com on behalf of Richard Kaye rkaye@invaluable.com Sent: Tuesday, July 22, 2025 3:02 PM To: profox@leafe.com profox@leafe.com Subject: RE: Win11 Deadline & FoxPro Apps!
Sorry, Kurt, I don't use CDO. I do know that besides the OS changes impacting you, email handling is rapidly changing as well.
Personally I think w00dy or Christof or any of the rest of the fine folk on this list are better sources for VFP expertise than Claude. 😊 Maybe not quite as available, though...
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Kurt Wendt Sent: Tuesday, July 22, 2025 1:13 PM To: profoxtech@leafe.com Subject: Re: Win11 Deadline & FoxPro Apps!
Darn - Oops - trying again...
Well - RK - there definitely is a Win11 relation to the problem. Because, same code that ran under Win10 - it fails to run under Win11 - as it seems that Win11 broke the VFPWinSock code.
A couple of weeks ago, when this all started - I actually asked Claude for help. He gave me a bunch of different options. I tried this option that uses CDO - but, the code wasn't working. Today I went back to that code, played around with it and change some parameters - and now it's working. This is essentially that code: * The code from this Test was originally given to me from Claude - then I updated some Settings - KHW - 7/22/25
LOCAL oMessage, oConfig oMessage = CREATEOBJECT("CDO.Message") oConfig = CREATEOBJECT("CDO.Configuration")
* Configure SMTP settings WITH oConfig.Fields .Item("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2 && Was... 2 .Item("http://schemas.microsoft.com/cdo/configuration/smtpserver") = "mail.pakoinc.com" .Item("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25 && Was ...587 .Item("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate") = 1 .Item("http://schemas.microsoft.com/cdo/configuration/sendusername") = "" .Item("http://schemas.microsoft.com/cdo/configuration/sendpassword") = "" .Item("http://schemas.microsoft.com/cdo/configuration/smtpusessl") = .F. && Was .T. .Update() ENDWITH
* Send the email WITH oMessage .Configuration = oConfig .To = "ablackmon@pakoinc.com" .From = "kwendt@pakoinc.com" .Subject = "CDO Test Subject" .TextBody = "CDO Email Test message body" .Send() ENDWITH
But, yes - in regards to authentication - when we further upgrade things like Email server - things maybe break again. Since, as you said - "authentication methods that are more stringent" - and my IT guy also made me aware of this. That this code could still break again.
________________________________________ From: ProFox profox-bounces@leafe.com on behalf of Richard Kaye rkaye@invaluable.com Sent: Tuesday, July 22, 2025 1:00 PM To: profox@leafe.com profox@leafe.com Subject: RE: Win11 Deadline & FoxPro Apps!
I think it's clear that your issue is not really W10 vs W11; it's how to handle SMTP in the modern world. 😊
Many, if not all, of the email providers are now requiring authentication methods that are more stringent then the wild west of open relaying, or even basic authentication with creds. This means calling APIs, using secrets, etc. All that modern stuff that we have not historically needed. And many now require proper SPF, DMARC, & DKIM just to make it more fun. -- rk
_______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/BY5PR13MB3843686F5A5E18EA368FE15DC35CA@BY5P... ** 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. _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/MW4PR10MB6584D4D18EC531EEE57E148FD25CA@MW4P... ** 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.
I'd recommend segregating the email sending from your core code altogether. Create a queueing table with your messages in it and have one machine responsible for actually passing that along to SMTP.
E
On Tue, Jul 22, 2025 at 2:07 PM Kurt Wendt kwendt@pakoinc.com wrote:
Thanks again RK for the follow up. Yes, the emailing handling and more stringent authentication has indeed been discussed by Tony our IT guy. I looking for OAuth2 related coding for VFP - he actually stumbled upon ChilKat - and discussed the potential need of ChilKat with our manager. So, it is indeed possible we may go the ChilKat route as a better more solid solution - since that CDO code below will most probably break during the email server upgrading.
-K ________________________________ From: ProFox profox-bounces@leafe.com on behalf of Richard Kaye < rkaye@invaluable.com> Sent: Tuesday, July 22, 2025 3:02 PM To: profox@leafe.com profox@leafe.com Subject: RE: Win11 Deadline & FoxPro Apps!
Sorry, Kurt, I don't use CDO. I do know that besides the OS changes impacting you, email handling is rapidly changing as well.
Personally I think w00dy or Christof or any of the rest of the fine folk on this list are better sources for VFP expertise than Claude. 😊 Maybe not quite as available, though...
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Kurt Wendt Sent: Tuesday, July 22, 2025 1:13 PM To: profoxtech@leafe.com Subject: Re: Win11 Deadline & FoxPro Apps!
Darn - Oops - trying again...
Well - RK - there definitely is a Win11 relation to the problem. Because, same code that ran under Win10 - it fails to run under Win11 - as it seems that Win11 broke the VFPWinSock code.
A couple of weeks ago, when this all started - I actually asked Claude for help. He gave me a bunch of different options. I tried this option that uses CDO - but, the code wasn't working. Today I went back to that code, played around with it and change some parameters - and now it's working. This is essentially that code:
- The code from this Test was originally given to me from Claude - then I
updated some Settings - KHW - 7/22/25
LOCAL oMessage, oConfig oMessage = CREATEOBJECT("CDO.Message") oConfig = CREATEOBJECT("CDO.Configuration")
- Configure SMTP settings
WITH oConfig.Fields .Item("http://schemas.microsoft.com/cdo/configuration/sendusing") = 2 && Was... 2 .Item("http://schemas.microsoft.com/cdo/configuration/smtpserver") = " mail.pakoinc.com" .Item("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25 && Was ...587 .Item("http://schemas.microsoft.com/cdo/configuration/smtpauthenticate") = 1 .Item("http://schemas.microsoft.com/cdo/configuration/sendusername") = "" .Item("http://schemas.microsoft.com/cdo/configuration/sendpassword") = "" .Item("http://schemas.microsoft.com/cdo/configuration/smtpusessl") = .F. && Was .T. .Update() ENDWITH
- Send the email
WITH oMessage .Configuration = oConfig .To = "ablackmon@pakoinc.com" .From = "kwendt@pakoinc.com" .Subject = "CDO Test Subject" .TextBody = "CDO Email Test message body" .Send() ENDWITH
But, yes - in regards to authentication - when we further upgrade things like Email server - things maybe break again. Since, as you said - "authentication methods that are more stringent" - and my IT guy also made me aware of this. That this code could still break again.
From: ProFox profox-bounces@leafe.com on behalf of Richard Kaye < rkaye@invaluable.com> Sent: Tuesday, July 22, 2025 1:00 PM To: profox@leafe.com profox@leafe.com Subject: RE: Win11 Deadline & FoxPro Apps!
I think it's clear that your issue is not really W10 vs W11; it's how to handle SMTP in the modern world. 😊
Many, if not all, of the email providers are now requiring authentication methods that are more stringent then the wild west of open relaying, or even basic authentication with creds. This means calling APIs, using secrets, etc. All that modern stuff that we have not historically needed. And many now require proper SPF, DMARC, & DKIM just to make it more fun. -- rk
[excessive quoting removed by server]
On Tue, 22 Jul 2025, at 8:24 PM, Eric Selje wrote:
I'd recommend segregating the email sending from your core code altogether.
+1 for this. If you're strictly in Microsoft land, I would also consider sending via the Graph API. That way users can see the messages in their Outlook 'Sent Items'
I looked into Graph as a replacement for SMTP here at the office. We currently drop in SMTP details on way too many different systems, so conversion to an API is probably not feasible.
On Wed, Jul 23, 2025 at 3:03 AM Alan Bourke alanpbourke@fastmail.fm wrote:
On Tue, 22 Jul 2025, at 8:24 PM, Eric Selje wrote:
I'd recommend segregating the email sending from your core code
altogether.
+1 for this. If you're strictly in Microsoft land, I would also consider sending via the Graph API. That way users can see the messages in their Outlook 'Sent Items'
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
[excessive quoting removed by server]
First: you can upgrade almost any decent PC to Win11 if it has Win10 running. (Win 7 & 8 may not do an automatic licensing anymore, depends on your Bios; but can also get upgraded this way)
Copy the Win11.ISO (download from Microsoft directly!) onto the PC, mount it with Doubleclick. Then open CMD with Admin-privilege, change to the mounted drive and then do SETUP /PRODUCT SERVER This switch disables all checks for TPM etc and then installs a Win11 Home or Pro (depending of your existing Windows variant). Works with all x64 CPUs from 2008 onwards. This commandline switch doesn't work with Win11 version 27xxx anymore, thus grab your Win11 ISO now!. Even if you install an older ISO, the regular Win-updates will still get you to the current version.
If there are problems with the Upgrade, Windows either reverts itself to the original version, or you can manually go back. If everything is working ok, then run CleanMgr with Admin-privilege, and select all options to get rid of that OldWin-backups..
I have successfully upgraded more than 10 PCs (even 15 year old DELLs) this way; sometimes added RAM to get at least 4GB and changed to an SSD, those boxes are then still useful for Students and Officework.
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Kurt Wendt Gesendet: Montag, 21. Juli 2025 23:02 An: ProFox Email List profox@leafe.com profox@leafe.com Betreff: *** Spam *** Win11 Deadline & FoxPro Apps!
So, here at work - my IT guy let us know there is this big Looming Deadline by Micro$oft - to kill off a bunch of older applications.
[excessive quoting removed by server]
wOOdy,
Thanks for this! I've tried to upgrade my older PC a couple of times but couldn't get past the TPM check. Your command line trick did it!
Much appreciated.
Ken Watkins
------ Original Message ------ From: juergen@wondzinski.de To: "ProFox Email List" profox@leafe.com Sent: 7/22/2025 4:44:52 AM Subject: RE: Win11 Deadline & FoxPro Apps!
First: you can upgrade almost any decent PC to Win11 if it has Win10 running. (Win 7 & 8 may not do an automatic licensing anymore, depends on your Bios; but can also get upgraded this way)
Copy the Win11.ISO (download from Microsoft directly!) onto the PC, mount it with Doubleclick. Then open CMD with Admin-privilege, change to the mounted drive and then do SETUP /PRODUCT SERVER This switch disables all checks for TPM etc and then installs a Win11 Home or Pro (depending of your existing Windows variant). Works with all x64 CPUs from 2008 onwards. This commandline switch doesn't work with Win11 version 27xxx anymore, thus grab your Win11 ISO now!. Even if you install an older ISO, the regular Win-updates will still get you to the current version.
If there are problems with the Upgrade, Windows either reverts itself to the original version, or you can manually go back. If everything is working ok, then run CleanMgr with Admin-privilege, and select all options to get rid of that OldWin-backups..
I have successfully upgraded more than 10 PCs (even 15 year old DELLs) this way; sometimes added RAM to get at least 4GB and changed to an SSD, those boxes are then still useful for Students and Officework.
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Kurt Wendt Gesendet: Montag, 21. Juli 2025 23:02 An: ProFox Email List profox@leafe.com profox@leafe.com Betreff: *** Spam *** Win11 Deadline & FoxPro Apps!
So, here at work - my IT guy let us know there is this big Looming Deadline by Micro$oft - to kill off a bunch of older applications.
[excessive quoting removed by server]
Second:
Your Mailproblems may result from a unnoticed switch from "Outlook (Classic)" to "Outlook (New)". That one is FullStop-Crap: no OLE-automation anymore, less functionality and all your mail-accounts are now stored at MS cloud.. You stil can revert to the old Outlook 32Bit. And you can get rid of that Nagging for the NewOutlook with some registry keys:
----------------------------------------------------------------------- Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\office\16.0\Outlook\Preferences] "NewOutlookMigrationUserSetting"=dword:00000000 [HKEY_CURRENT_USER\Software\Microsoft\office\16.0\Outlook\Options\General] "DoNewOutlookAutoMigration"=dword:00000000 [HKEY_CURRENT_USER\Software\Microsoft\office\16.0\Outlook\Preferences] "UseNewOutlook"=dword:00000000 [HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Options\General] "NewOutlookAutoMigrationRetryIntervals"=dword:00000000 [HKEY_CURRENT_USER\Software\Microsoft\office\16.0\Outlook\Options\General] "HideNewOutlookToggle"=dword:00000001 -----------------------------------------------------------------------
wOOdy
-----Ursprüngliche Nachricht----- Von: ProFox profox-bounces@leafe.com Im Auftrag von Kurt Wendt Gesendet: Montag, 21. Juli 2025 23:02 An: ProFox Email List profox@leafe.com profox@leafe.com Betreff: *** Spam *** Win11 Deadline & FoxPro Apps!
So, here at work - my IT guy let us know there is this big Looming Deadline by Micro$oft - to kill off a bunch of older applications. Including older Windows servers, and other older Windows apps - including Win10. [excessive quoting removed by server]
-
Ajit Abraham -
Alan Bourke -
Bill Anderson -
Christof Wollenhaupt -
Eric Selje -
juergen＠wondzinski.de -
Ken Watkins -
Kurt Wendt -
Richard Kaye -
Stephen Russell -
Vincent Teachout