Re: Modern email library

2016-11-30 Thread William Prothero
Folks, In case anybody wants to look at my version of email with attachments, sent using a remote email server, you can download a sample stack at: http://es.earthlearningsolutions.org/SoftwareForEducation It uses php on the server side.

Re: Modern email library

2016-11-30 Thread Ben Rubinstein
On 30/11/2016 17:07, Matthias Rebbe wrote: have a look at the sample stack Charles Warwick provided https://downloads.techstrategies.com.au/tsnet/LCMail.livecode It contains functions to create smtp header and body (including attachments). Thanks Matthias, I've grabbed that and will take a lo

Re: Evils of client-side SMTP (Re: Modern email library)

2016-11-30 Thread Richard Gaskin
Ben Rubinstein wrote: > I can see why, as a user, you might be uncomfortable about giving > your email account details to an app so that it can send emails > in your name, invisibly and unreviewed by you. Quite right too! > And if you're developing software for consumers, you need to take > that

Evils of client-side SMTP (Re: Modern email library)

2016-11-30 Thread Ben Rubinstein
I'm a bit confused, Richard. FWIW, my long-time use-case is an app that runs unattended on a regular schedule on a faceless VM, doing a whole bunch of data processing and updating databases, and sends alerts by email if something goes wrong. When the app is installed, it has to be set up with

Re: Modern email library

2016-11-30 Thread Richard Gaskin
Bob Sneidar wrote: > I can provide you with scenarios where client side SMTP is a must. There are many. But hopefully they're an explicit decision by the user, and require the user to supply their own SMTP credentials. -- Richard Gaskin Fourth World Systems Software Design and Development

Re: Modern email library

2016-11-30 Thread Matthias Rebbe
It always depends on how you use such libraries or externals. The new tsNET external allows us for example to send notification emails from our scheduled unattended maintenance tools using our own in-house mailserver. Our mailserver requests authentication from our apps before sending out to e

Re: Modern email library

2016-11-30 Thread Matthias Rebbe
Ben, have a look at the sample stack Charles Warwick provided https://downloads.techstrategies.com.au/tsnet/LCMail.livecode It contains functions to create smtp header and body (including attachments). Matthias > Am 30.11.2016 u

Re: Modern email library

2016-11-30 Thread Bob Sneidar
I can provide you with scenarios where client side SMTP is a must. Embedded systems which send alerts, such as managed switches, routers, UPS systems, etc. REQUIRE client side SMTP to work. Further, software systems like a managed AV system or a centralized backup system which sends reports to t

Re: Modern email library

2016-11-30 Thread Bob Sneidar
Hmmm... I am logged in but I cannot seem to find any files to DL here. I may misunderstand. Bob S On Nov 30, 2016, at 05:44 , Peter TB Brett mailto:peter.br...@livecode.com>> wrote: As part of the LiveCode for FM project, Monte has been developing a MIME library for constructing e-mail bodie

Re: Modern email library

2016-11-30 Thread Richard Gaskin
Ben Rubinstein wrote: > I've one app that's been in existence for over a decade, which uses > Shao Sean's libSmtp. It works fine. > > Now I find myself wanting to send email from a new stack I'm working > on. I could just drag that library out again, but I suspect that a > more modern way is to u

Re: Modern email library

2016-11-30 Thread Peter TB Brett
On 30/11/2016 13:16, Ben Rubinstein wrote: I've one app that's been in existence for over a decade, which uses Shao Sean's libSmtp. It works fine. Now I find myself wanting to send email from a new stack I'm working on. I could just drag that library out again, but I suspect that a more modern w

Modern email library

2016-11-30 Thread Ben Rubinstein
I've one app that's been in existence for over a decade, which uses Shao Sean's libSmtp. It works fine. Now I find myself wanting to send email from a new stack I'm working on. I could just drag that library out again, but I suspect that a more modern way is to use tsNet. AFAICT tsNet handle