Ken,
If you're open to an "out of the box thinking" solution, I suggest
considering an external web page with authentication. I think you're
hitting the myriad of security settings that surround email and network
communication and it's driving you crazy like it drove me crazy. In a
past job of mine that deployed a VFP solution out to the field, we never
knew what security measures we'd hit, and so we came up with this
solution...
[1] VFP application makes a POST to a PHP page that was hosted at
https://ourcontrolleddomain.com
[1a.] Part of that post was an encrypted token that authenticated the
post was from our VFP application and which installation.
[1b.] The rest of the values were the txtTo, txtCC, txtBCC, txtFrom,
txtSubject, txtBody values. We didn't allow for attachments.
[3] The PHP page sent the email on the behalf of the application and
logged the results.
[4] The PHP page responded (simply) whether Successful, or Unsuccessful
with reasons.
We found that almost every workstation has the ports open for SSL and we
could focus on making the PHP page securely send the emails on the
behalf of the application.
I hope this is of some use.
-Kevin
On 09/22/2014 11:04 AM, Ken Dibble wrote:
So what are my options for an as-native-as-possible solution?
Is there better VFP-native SMTP sending code out there?
_______________________________________________
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.
