Re: eMail attachment: best practice?
Paul: > I wish there was a better option. in your case - simply upload the file. Best wishes, Curry Kenworthy Radically Innovative Christian LiveCode Development "PASSION for Elegant, Efficient Code!" https://livecodeconsulting.com/ ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
Matthias wrote: > Am 27.06.2024 um 02:48 schrieb Richard Gaskin>: >> 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. > > I would say this always depends on the purpose the app is > supposed to fulfill. Every good app does. :) > In my private projects I am using quite often Livecode Server > as the backend for my LC apps, but I had some customer projects > in the past where the customer wanted an app to send out e-mails > with special attachments, like logfiles or reports or whatever > and it had to be without user interaction. I think we're on the same page. I tend to prefer open disclosure for users to review data before sending from their local machine to a server, but it's not functionally necessary. Most apps don't bother, and of course a POST command can be sent without any user interaction. > In the days before tsNET I either used Shao Sean's e-mail > library, Chip Walter's altEmailHarness or I called command > line tools using shell function to get this done. If the final reciever *needs* to be an email client, nearly any method will require a mime wrapper for the payload. The nice thing about doing that for sendmail on the server, rather than for whatever the user uses for email on the client, is we don't know what the user is using. Things can get tricky with all the possible options one might discover a need to support (native email apps, webmail like GMail or Nextcloud, gawdonlyknows what special handling may be needed for monsters like Office 365, etc.). Sendmail gives us one one well-documented compatibility target to build for and test against. And it's already available; I don't need to set up half a dozen client email options just to get started. But the other benefit with POSTing to the server is you can change your mind easily about how you want to handle it. Maybe today the reciever is a support person's email In Box, but if so that's really an intermediary place, where the final destination will be some form of issue tracking DB. So one can go ahead and use sendmail to get the info to support in email today, and later revise the CGI handler to post directly into the issue tracker DB API, saving the payroll cost and error rate that comes with rote human intermediation. Another consideration is trust, esp. when the method used requires users to enter their server credentials. With a simple POST, no interaction is needed, no information the app doesn't already have in the course of normal use is obtained. The situation is trustless, in the sense of trust not being a requirement to proceed. The moment any app asks me for any server credentiails, I need to stop and consider the implications. If the app is my email client, of course I expect that, and I only use email clients I already trust. With anything else I'm going to think it through carefully, and probably contact the vendor to seek a different method, if I bother continuing using the product at all. Imagine if you went to a web site and the Contact form required your server creds. Would you hand those over? Do your users know you intimately enough to have complete confidence they can give you the keys to their kingdom in an app form? I can imagine maybe some enterprise environments where that level of trust *might* be available. But the same security awareness that makes the environment trustable probably wouldn't ask for server credentials. Good IT staff regard all networks as hostile, even LAN. In short: - POST requires no more work for mime-wrapping the payload than client email; - sendmail on the server is a simpler target than all possible email clints; - can have a UI or not, as desired; - leaves the door open for easy re-routing later on if needed; - requires no trust from the user beyond what they might expect with any web form. -- Richard Gaskin FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
> Am 27.06.2024 um 02:48 schrieb Richard Gaskin via use-livecode > : > > 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. > I would say this always depends on the purpose the app is supposed to fulfill. In my private projects I am using quite often Livecode Server as the backend for my LC apps, but I had some customer projects in the past where the customer wanted an app to send out e-mails with special attachments, like logfiles or reports or what ever and it had to be without user interaction. In the days before tsNET I either used Shao Sean's e-mail library, Chip Walter's altEmailHarness or I called command line tools using shell function to get this done. > 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. > > Richard Gaskin > FourthWorld.com > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
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. Richard Gaskin FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
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 server requires authentication. > However, in the "wild" of a distributed application that could be on any > customer's computer in any setting, how do you know what the customer's SMTP > server is or whether it requires authentication. If it does require > authentication, most people set Your app needs to have a card or substack where the customers can add their mail account login data and the server ip or name and all the other information they would enter when adding an email account to their e-mail client. > this up in their email client ONCE (or rarely) and may not know or remember > what the credentials are. > Those people would also run into trouble if they switch to another e-mail client or if they get a new computer where they have to setup the e-mail client again. This is not an email problem per se, but rather the problem that users are not doing proper password management. > So I considered using our company SMTP server, but increasingly, SMTP servers > will reject messages if they are from a client computer that is not in the > same domain, as is the case with ours (for anti-spamming/spoofing), so that > it out as an option. > What exactly did you want to do? Use the server to send e-mails to internal accounts on that server? Or did you want to use that server as a relay server to send emails to external e-mail addresses? To do that you normally need an e-mail account on that server and your account needs to have the right to send external e-mails and you need to have to authenticate on that server when sending the e-mails to external users. > I kinda need a solution that uses the clients own email client (and server). tsNet behaves like an e-mail client. If the customer now there e-mail credentials and other information for setting up an e-mail client and if your app allows to enter those information, then tsNet will work without a problem. Maybe with one exception. If the server only allows 2FA for the e-mail clients, then tsNet needs to support this. Maybe this is already the case, maybe not. This is a question Charles Warwick or Livecode Support could answer > Maybe I should look at how to encode the array in a pure text form that can > be part of the email body and send it that way. The problem there is that > some email clients (like gMail) limit the size of the message body that can > be generated from their APIs. If you use revMail with someone with gMail as > their default mail, the message body can only be about 2500 characters (or > maybe 5000, I forget the exact limit). > > I suppose I could output the array as an encoded file to the customer's > desktop and ASK them to manually attach it to the generated email? I wish > there was a better option. > > >> On 6/25/2024 6:15 PM, matthias rebbe via use-livecode wrote: >> Instead of using revMail which opens the default mail client app you could >> use tsNET external, which is availlable for Win/Mac/Linux/iOS and Android. >> >> The only thing you have to keep in mind is that tsNet directly sends the >> email instead of opening the default email client. >> >> Here you can find an sample stack >> https://downloads.techstrategies.com.au/tsnet/smtpexample.livecode >> >> And here is a link to a Livecode Lesson >> https://lessons.livecode.com/m/4071/l/685661-how-to-send-e-mail-using-the-tsnet-external >> >> >> Am 25.06.2024 um 22:35 schrieb Paul Dupuis via use-livecode : >>> >>> Under a specific condition, my app creates an email with some pre-populated >>> information using revMail: >>> >>> revMail address, [ccAddress, [mailSubject, [messageBody]]] >>> >>> So, my call is: revMail tSupportEmail, , "Diagnostic Report Information", >>> tEmailBody >>> Where tSupportEmail contains a valid email address and tEmailBody contain >>> the information I want to send. >>> >>> I realize the user still has to click their send button in their email >>> client, but I have 2 questions: >>> >>> 1) I see the Dictionary still lists "revMailUnicode" with the same >>> parameters. If tEmailBody contains Unicode characters do I need to >>> textEncode(tEmailBody, "UTF-16") and use revMailUnicode OR is plain old >>> revMail now Unicode aware >>> >>> 2) My more important question is how does one create an email with an >>> attached file? I see no feature of revMail to include an attachment. Is >>> there some other way? If there is no way to add an attachment, what might >>> the best practice for sending the contents and structure of a Livecode >>> array be? >>> >>> >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please vis
Re: eMail attachment: best practice?
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 Security is enabled, and are progressively enforcing Modern Security permanently. Mail Clients that communicate with Office365 do not use SMTP, they use MAPI so they are not effected. The only thing I can suggest is to subscribe to a web based SMTP relay. Bundle the cost of that (which isn’t very much) into the price of your product. Bob S > On Jun 26, 2024, at 6:00 AM, Paul Dupuis via use-livecode > wrote: > > 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 any > customer's computer in any setting, how do you know what the customer's SMTP > server is or whether it requires authentication. If it does require > authentication, most people set this up in their email client ONCE (or > rarely) and may not know or remember what the credentials are. > > So I considered using our company SMTP server, but increasingly, SMTP servers > will reject messages if they are from a client computer that is not in the > same domain, as is the case with ours (for anti-spamming/spoofing), so that > it out as an option. > > I kinda need a solution that uses the clients own email client (and server). > Maybe I should look at how to encode the array in a pure text form that can > be part of the email body and send it that way. The problem there is that > some email clients (like gMail) limit the size of the message body that can > be generated from their APIs. If you use revMail with someone with gMail as > their default mail, the message body can only be about 2500 characters (or > maybe 5000, I forget the exact limit). > > I suppose I could output the array as an encoded file to the customer's > desktop and ASK them to manually attach it to the generated email? I wish > there was a better option. > > > On 6/25/2024 6:15 PM, matthias rebbe via use-livecode wrote: >> Instead of using revMail which opens the default mail client app you could >> use tsNET external, which is availlable for Win/Mac/Linux/iOS and Android. >> >> The only thing you have to keep in mind is that tsNet directly sends the >> email instead of opening the default email client. >> >> Here you can find an sample stack >> https://downloads.techstrategies.com.au/tsnet/smtpexample.livecode >> >> And here is a link to a Livecode Lesson >> https://lessons.livecode.com/m/4071/l/685661-how-to-send-e-mail-using-the-tsnet-external >> >> >> >>> Am 25.06.2024 um 22:35 schrieb Paul Dupuis via use-livecode >>> : >>> >>> Under a specific condition, my app creates an email with some pre-populated >>> information using revMail: >>> >>> revMail address, [ccAddress, [mailSubject, [messageBody]]] >>> >>> So, my call is: revMail tSupportEmail, , "Diagnostic Report Information", >>> tEmailBody >>> Where tSupportEmail contains a valid email address and tEmailBody contain >>> the information I want to send. >>> >>> I realize the user still has to click their send button in their email >>> client, but I have 2 questions: >>> >>> 1) I see the Dictionary still lists "revMailUnicode" with the same >>> parameters. If tEmailBody contains Unicode characters do I need to >>> textEncode(tEmailBody, "UTF-16") and use revMailUnicode OR is plain old >>> revMail now Unicode aware >>> >>> 2) My more important question is how does one create an email with an >>> attached file? I see no feature of revMail to include an attachment. Is >>> there some other way? If there is no way to add an attachment, what might >>> the best practice for sending the contents and structure of a Livecode >>> array be? >>> >>> >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.
Re: eMail attachment: best practice?
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 any customer's computer in any setting, how do you know what the customer's SMTP server is or whether it requires authentication. If it does require authentication, most people set this up in their email client ONCE (or rarely) and may not know or remember what the credentials are. So I considered using our company SMTP server, but increasingly, SMTP servers will reject messages if they are from a client computer that is not in the same domain, as is the case with ours (for anti-spamming/spoofing), so that it out as an option. I kinda need a solution that uses the clients own email client (and server). Maybe I should look at how to encode the array in a pure text form that can be part of the email body and send it that way. The problem there is that some email clients (like gMail) limit the size of the message body that can be generated from their APIs. If you use revMail with someone with gMail as their default mail, the message body can only be about 2500 characters (or maybe 5000, I forget the exact limit). I suppose I could output the array as an encoded file to the customer's desktop and ASK them to manually attach it to the generated email? I wish there was a better option. On 6/25/2024 6:15 PM, matthias rebbe via use-livecode wrote: Instead of using revMail which opens the default mail client app you could use tsNET external, which is availlable for Win/Mac/Linux/iOS and Android. The only thing you have to keep in mind is that tsNet directly sends the email instead of opening the default email client. Here you can find an sample stack https://downloads.techstrategies.com.au/tsnet/smtpexample.livecode And here is a link to a Livecode Lesson https://lessons.livecode.com/m/4071/l/685661-how-to-send-e-mail-using-the-tsnet-external Am 25.06.2024 um 22:35 schrieb Paul Dupuis via use-livecode : Under a specific condition, my app creates an email with some pre-populated information using revMail: revMail address, [ccAddress, [mailSubject, [messageBody]]] So, my call is: revMail tSupportEmail, , "Diagnostic Report Information", tEmailBody Where tSupportEmail contains a valid email address and tEmailBody contain the information I want to send. I realize the user still has to click their send button in their email client, but I have 2 questions: 1) I see the Dictionary still lists "revMailUnicode" with the same parameters. If tEmailBody contains Unicode characters do I need to textEncode(tEmailBody, "UTF-16") and use revMailUnicode OR is plain old revMail now Unicode aware 2) My more important question is how does one create an email with an attached file? I see no feature of revMail to include an attachment. Is there some other way? If there is no way to add an attachment, what might the best practice for sending the contents and structure of a Livecode array be? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
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 for sending e-mails with logfiles and reports. This works w/o problems. Von meinem iPad gesendet > Am 26.06.2024 um 01:02 schrieb Bob Sneidar via use-livecode > : > > I used a properly formatted “url” (it’s not actually a URL) for the server > and got a response from the server, so I am communicating, but it’s > generating an error even though the user name and password are correct (They > are my credentials.) > > Also, considering that almost all servers are forcing the use of 2 factor or > Multi-factor authentication these days, it’s probably just better to use the > local mail client. > > Bob S > > >> On Jun 25, 2024, at 3:53 PM, Bob Sneidar wrote: >> >> The demo stack URL in the script does not look right. I have never used a >> URL in the form of SMTP://:587/ before. That can’t be right! >> >> Bob S >> >> On Jun 25, 2024, at 3:15 PM, matthias rebbe via use-livecode wrote: >>> >>> Instead of using revMail which opens the default mail client app you could >>> use tsNET external, which is availlable for Win/Mac/Linux/iOS and Android. >>> >>> The only thing you have to keep in mind is that tsNet directly sends the >>> email instead of opening the default email client. >>> >>> Here you can find an sample stack >>> https://downloads.techstrategies.com.au/tsnet/smtpexample.livecode >>> >>> And here is a link to a Livecode Lesson >>> https://lessons.livecode.com/m/4071/l/685661-how-to-send-e-mail-using-the-tsnet-external >>> >>> >>> Am 25.06.2024 um 22:35 schrieb Paul Dupuis via use-livecode : Under a specific condition, my app creates an email with some pre-populated information using revMail: revMail address, [ccAddress, [mailSubject, [messageBody]]] So, my call is: revMail tSupportEmail, , "Diagnostic Report Information", tEmailBody Where tSupportEmail contains a valid email address and tEmailBody contain the information I want to send. I realize the user still has to click their send button in their email client, but I have 2 questions: 1) I see the Dictionary still lists "revMailUnicode" with the same parameters. If tEmailBody contains Unicode characters do I need to textEncode(tEmailBody, "UTF-16") and use revMailUnicode OR is plain old revMail now Unicode aware 2) My more important question is how does one create an email with an attached file? I see no feature of revMail to include an attachment. Is there some other way? If there is no way to add an attachment, what might the best practice for sending the contents and structure of a Livecode array be? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode >>> >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
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 other port than 80, e.g. 8080, you can would open use the following url in the web browser http://serverip:8080 Von meinem iPad gesendet > Am 26.06.2024 um 00:55 schrieb Bob Sneidar via use-livecode > : > > The demo stack URL in the script does not look right. I have never used a > URL in the form of SMTP://:587/ before. That can’t be right! > > Bob S > > >> On Jun 25, 2024, at 3:15 PM, matthias rebbe via use-livecode >> wrote: >> >> Instead of using revMail which opens the default mail client app you could >> use tsNET external, which is availlable for Win/Mac/Linux/iOS and Android. >> >> The only thing you have to keep in mind is that tsNet directly sends the >> email instead of opening the default email client. >> >> Here you can find an sample stack >> https://downloads.techstrategies.com.au/tsnet/smtpexample.livecode >> >> And here is a link to a Livecode Lesson >> https://lessons.livecode.com/m/4071/l/685661-how-to-send-e-mail-using-the-tsnet-external >> >> >> Am 25.06.2024 um 22:35 schrieb Paul Dupuis via use-livecode : >>> >>> Under a specific condition, my app creates an email with some pre-populated >>> information using revMail: >>> >>> revMail address, [ccAddress, [mailSubject, [messageBody]]] >>> >>> So, my call is: revMail tSupportEmail, , "Diagnostic Report Information", >>> tEmailBody >>> Where tSupportEmail contains a valid email address and tEmailBody contain >>> the information I want to send. >>> >>> I realize the user still has to click their send button in their email >>> client, but I have 2 questions: >>> >>> 1) I see the Dictionary still lists "revMailUnicode" with the same >>> parameters. If tEmailBody contains Unicode characters do I need to >>> textEncode(tEmailBody, "UTF-16") and use revMailUnicode OR is plain old >>> revMail now Unicode aware >>> >>> 2) My more important question is how does one create an email with an >>> attached file? I see no feature of revMail to include an attachment. Is >>> there some other way? If there is no way to add an attachment, what might >>> the best practice for sending the contents and structure of a Livecode >>> array be? >>> >>> >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
I should have mentioned that my app is for macOS and Windows - no iOS or Android version. On 6/25/2024 5:46 PM, Mark Smith wrote: I’ve not used revMail but it’s certainly well documented in mobileComposeHtmlMail. If you need an example PM me. Mark On 25 Jun 2024, at 9:35 PM, Paul Dupuis via use-livecode wrote: 2) My more important question is how does one create an email with an attached file? I see no feature of revMail to include an attachment. Is there some other way? If there is no way to add an attachment, what might the best practice for sending the contents and structure of a Livecode array be? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
I used a properly formatted “url” (it’s not actually a URL) for the server and got a response from the server, so I am communicating, but it’s generating an error even though the user name and password are correct (They are my credentials.) Also, considering that almost all servers are forcing the use of 2 factor or Multi-factor authentication these days, it’s probably just better to use the local mail client. Bob S > On Jun 25, 2024, at 3:53 PM, Bob Sneidar wrote: > > The demo stack URL in the script does not look right. I have never used a URL > in the form of SMTP://:587/ before. That can’t be right! > > Bob S > > >> On Jun 25, 2024, at 3:15 PM, matthias rebbe via use-livecode >> wrote: >> >> Instead of using revMail which opens the default mail client app you could >> use tsNET external, which is availlable for Win/Mac/Linux/iOS and Android. >> >> The only thing you have to keep in mind is that tsNet directly sends the >> email instead of opening the default email client. >> >> Here you can find an sample stack >> https://downloads.techstrategies.com.au/tsnet/smtpexample.livecode >> >> And here is a link to a Livecode Lesson >> https://lessons.livecode.com/m/4071/l/685661-how-to-send-e-mail-using-the-tsnet-external >> >> >> >>> Am 25.06.2024 um 22:35 schrieb Paul Dupuis via use-livecode >>> : >>> >>> Under a specific condition, my app creates an email with some pre-populated >>> information using revMail: >>> >>> revMail address, [ccAddress, [mailSubject, [messageBody]]] >>> >>> So, my call is: revMail tSupportEmail, , "Diagnostic Report Information", >>> tEmailBody >>> Where tSupportEmail contains a valid email address and tEmailBody contain >>> the information I want to send. >>> >>> I realize the user still has to click their send button in their email >>> client, but I have 2 questions: >>> >>> 1) I see the Dictionary still lists "revMailUnicode" with the same >>> parameters. If tEmailBody contains Unicode characters do I need to >>> textEncode(tEmailBody, "UTF-16") and use revMailUnicode OR is plain old >>> revMail now Unicode aware >>> >>> 2) My more important question is how does one create an email with an >>> attached file? I see no feature of revMail to include an attachment. Is >>> there some other way? If there is no way to add an attachment, what might >>> the best practice for sending the contents and structure of a Livecode >>> array be? >>> >>> >>> ___ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
The demo stack URL in the script does not look right. I have never used a URL in the form of SMTP://:587/ before. That can’t be right! Bob S > On Jun 25, 2024, at 3:15 PM, matthias rebbe via use-livecode > wrote: > > Instead of using revMail which opens the default mail client app you could > use tsNET external, which is availlable for Win/Mac/Linux/iOS and Android. > > The only thing you have to keep in mind is that tsNet directly sends the > email instead of opening the default email client. > > Here you can find an sample stack > https://downloads.techstrategies.com.au/tsnet/smtpexample.livecode > > And here is a link to a Livecode Lesson > https://lessons.livecode.com/m/4071/l/685661-how-to-send-e-mail-using-the-tsnet-external > > > >> Am 25.06.2024 um 22:35 schrieb Paul Dupuis via use-livecode >> : >> >> Under a specific condition, my app creates an email with some pre-populated >> information using revMail: >> >> revMail address, [ccAddress, [mailSubject, [messageBody]]] >> >> So, my call is: revMail tSupportEmail, , "Diagnostic Report Information", >> tEmailBody >> Where tSupportEmail contains a valid email address and tEmailBody contain >> the information I want to send. >> >> I realize the user still has to click their send button in their email >> client, but I have 2 questions: >> >> 1) I see the Dictionary still lists "revMailUnicode" with the same >> parameters. If tEmailBody contains Unicode characters do I need to >> textEncode(tEmailBody, "UTF-16") and use revMailUnicode OR is plain old >> revMail now Unicode aware >> >> 2) My more important question is how does one create an email with an >> attached file? I see no feature of revMail to include an attachment. Is >> there some other way? If there is no way to add an attachment, what might >> the best practice for sending the contents and structure of a Livecode array >> be? >> >> >> ___ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
Instead of using revMail which opens the default mail client app you could use tsNET external, which is availlable for Win/Mac/Linux/iOS and Android. The only thing you have to keep in mind is that tsNet directly sends the email instead of opening the default email client. Here you can find an sample stack https://downloads.techstrategies.com.au/tsnet/smtpexample.livecode And here is a link to a Livecode Lesson https://lessons.livecode.com/m/4071/l/685661-how-to-send-e-mail-using-the-tsnet-external > Am 25.06.2024 um 22:35 schrieb Paul Dupuis via use-livecode > : > > Under a specific condition, my app creates an email with some pre-populated > information using revMail: > > revMail address, [ccAddress, [mailSubject, [messageBody]]] > > So, my call is: revMail tSupportEmail, , "Diagnostic Report Information", > tEmailBody > Where tSupportEmail contains a valid email address and tEmailBody contain the > information I want to send. > > I realize the user still has to click their send button in their email > client, but I have 2 questions: > > 1) I see the Dictionary still lists "revMailUnicode" with the same > parameters. If tEmailBody contains Unicode characters do I need to > textEncode(tEmailBody, "UTF-16") and use revMailUnicode OR is plain old > revMail now Unicode aware > > 2) My more important question is how does one create an email with an > attached file? I see no feature of revMail to include an attachment. Is there > some other way? If there is no way to add an attachment, what might the best > practice for sending the contents and structure of a Livecode array be? > > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: eMail attachment: best practice?
I’ve not used revMail but it’s certainly well documented in mobileComposeHtmlMail. If you need an example PM me. Mark > On 25 Jun 2024, at 9:35 PM, Paul Dupuis via use-livecode > wrote: > > 2) My more important question is how does one create an email with an > attached file? I see no feature of revMail to include an attachment. Is there > some other way? If there is no way to add an attachment, what might the best > practice for sending the contents and structure of a Livecode array be? > ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
eMail attachment: best practice?
Under a specific condition, my app creates an email with some pre-populated information using revMail: revMail address, [ccAddress, [mailSubject, [messageBody]]] So, my call is: revMail tSupportEmail, , "Diagnostic Report Information", tEmailBody Where tSupportEmail contains a valid email address and tEmailBody contain the information I want to send. I realize the user still has to click their send button in their email client, but I have 2 questions: 1) I see the Dictionary still lists "revMailUnicode" with the same parameters. If tEmailBody contains Unicode characters do I need to textEncode(tEmailBody, "UTF-16") and use revMailUnicode OR is plain old revMail now Unicode aware 2) My more important question is how does one create an email with an attached file? I see no feature of revMail to include an attachment. Is there some other way? If there is no way to add an attachment, what might the best practice for sending the contents and structure of a Livecode array be? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
