I wouldn't make anyone fill out anything. I'd just present a window for them to
review, and POST it to my web site. The receiving CGI can do whatever I need.
If the diagnostic info is for a support issue, you may be able to use your
support tracking DB's API to automate creating the ticket.
Ri
Von meinem iPad gesendet
> Am 26.06.2024 um 15:01 schrieb Paul Dupuis via use-livecode
> :
>
> So this tsNet example for sending an email look great IF you are using it in
> an corporate or institutional setting. One where you have a known SMTP server
> and you know whether or not that SMTP
You would need to present the user with an interface where they can enter their
corporate or business SMTP information, then use that. But more mail providers
are forcing MFA these days (as I mentioned) and Microsoft has even gone so far
as to completely disable ALL SMTP relaying when Modern Sec
Have you tried trashing the LC preferences?
Have you tried the recent stack with a different data stack, or perhaps one
with less data?
Craig
> On Jun 26, 2024, at 4:35 AM, Neville Smythe via use-livecode
> wrote:
>
> I am plagued by a new problem which has arisen in an old stack that I have
So this tsNet example for sending an email look great IF you are using
it in an corporate or institutional setting. One where you have a known
SMTP server and you know whether or not that SMTP server requires
authentication.
However, in the "wild" of a distributed application that could be on
I am plagued by a new problem which has arisen in an old stack that I have been
using for years with hundreds of modifications over that time. It was still
working well until suddenly in the last few week most of its data processing
handlers have slowed to a crawl. A button that gathers text dat
I am not sure how many smtp servers support 2FA yet.
If the mail client can connect to a mailserver then tsNET should also be able
to.
tsNET external uses a curl library.
And if 2FA for SMTP gets more common, I am sure tsNet will be updated to
support it.
I am using tsNET in several projects fo
The url is right.
The prefixes smtp:// smtps://, http:// https:// ftp:// ftps:// sftp:// and so
tell the underlying tool which establish the connection to use that protocol.
A trailing :587 means the connection should be established with port 587
If you are running for example a webserver on an o
