Re: RE: QtmmSendMail with Binary Attachments

[Scott Klement <klemscot@xxxxxxxxxxxx>]

>
> That's exactly what I have been doing. The attachment looks okay in the
> email, but when I try to open it, it tells me that the document has been
> corrupted. I can go into Ops Nav and find the original on the IFS, though,
> and from there it opens fine.
>

Forgive me, for I do not use this API, but do you have to base64 encode
the attachment?  It sounds like you're sending the file as-is, and not
encoding it.

I'll elaborate:

When internet e-mail was developed (mainly in the 1970's) it was designed
as a method of transporting simple text messages.   By that I mean, the
only thing that you can send via SMTP is human-readable symbols (letters,
numbers, etc) and the CR/LF to indicate an end-of-line.

MIME was created in the 90's (at least, I think it was the 90s) to
overcome the limitations of this format.   MIME does two things... it
breaks the message up into multiple "parts", and provides headers
describing each part... how it's encoded, what application can read it,
etc.

Then, base64 was devised as a method of encoding binary attachments (by
"binary" I mean files that are not text-only) so that it looks like
plain-text to the SMTP transport agent, but a user-agent (e-mail client
program) can decode the base64 back into the original binary object.

Okay, enough history.   My question is... does the QtmmSendMail API
do the MIME and base64 encoding for you?   Or do you have to do that
yourself?   If you're doing it yourself, have you done it?

Because, from your description, it sounds to me like the non-text
characters of your document are getting corrupted...