Ali or Monte - MimeEncodeAsMIMEMultipartDocument
monte at appisle.net
Sun Jan 3 21:49:09 EST 2021
The MIME lib is all my fault so don’t blame Ali ;-)
It may help you to read RFCs 2045-2049 to gain an understanding of MIME. With the exception of mimeEncodeFieldAsMIMEMultipartDocument you really need to understand MIME to use the library.
You probably want the mimeEncodeAsMIMEEmail command though.
For the body presuming plain text email then you want something like:
put "Content-Type: text/plain; charset=UTF-8" & crlf & \
"Content-Transfer-Encoding: quoted-printable" & crlf & crlf & \
mimeEncodeForMIMETransfer(tText, "quoted-printable”) into tBody
If you want html email then if you don’t know what you need as parameters for mimeEncodeAsMIMEMultipartDocument then best to see the code of mimeEncodeFieldAsMIMEMultipartDocument as an example which builds that from field content.
Regarding BCC that’s nothing to do with the library. See tsNet recipients list for that.
> On 29 Dec 2020, at 3:18 am, Sean Cole (Pi) via use-livecode <use-livecode at lists.runrev.com> wrote:
> Hi all,
> The dictionary, as usual, is a bit lacking in regards to the Mime Library.
> For MimeEncodeAsMIMEMultipartDocument we have parameters but no idea what
> the values (enum) for them could or should be.
> pContentA: How do we pre-encode parts including headers?
> pMultipartType: What MultiPart types are there?
> pParamA: What kind of parameters does ParamA take?
> There is a lesson that has a single use-case instance but it does not cover
> all attachment or part types so we are still left guessing. Perhaps this is
> where either Monte or Ali who coded this could help us out. (
> I'm trying to attach a pdf to an email and have bcc addresses too.
> Sean Cole
> *Pi Digital *
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode