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 <[email protected]> on behalf of Richard Kaye <[email protected]> Sent: Tuesday, July 22, 2025 3:02 PM To: [email protected] <[email protected]> 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 <[email protected]> On Behalf Of Kurt Wendt Sent: Tuesday, July 22, 2025 1:13 PM To: [email protected] 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 = "[email protected]" .From = "[email protected]" .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 <[email protected]> on behalf of Richard Kaye <[email protected]> Sent: Tuesday, July 22, 2025 1:00 PM To: [email protected] <[email protected]> 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: [email protected] 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/by5pr13mb3843686f5a5e18ea368fe15dc3...@by5pr13mb3843.namprd13.prod.outlook.com ** 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: [email protected] 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/mw4pr10mb6584d4d18ec531eee57e148fd2...@mw4pr10mb6584.namprd10.prod.outlook.com ** 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: [email protected] 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/by5pr13mb38435b96fc3dbe38877629a4c3...@by5pr13mb3843.namprd13.prod.outlook.com ** 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.
