× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I've used the QShell jar utility to create a zip file which has a code
page of 819.  If I use the SNDDST command to mail it to myself, I can
open the attachment and extract the contents.  If I look at the internet
header on the mail it includes the following:

Content-Type: application/octet-stream;name=QSYSPRT.ZIP
Content-Transfer-Encoding: base64
Content-Description:<QSYSPRT.ZIP>

I've just written a command that uses the QtmmSendMail API instead of
the SNDDST command because I wanted to include multiple attachments, cc
and bcc addresses etc.  It works fine for except for when I try to send
a zip file.

When I am building the MIME file, I open any attachment and add the
contents into the MIME stream, which I'd been using with:

Content-Type: application/octet-stream; name="QSYSPRT.ZIP"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="QSYSPRT.ZIP"

This works fine for csv, html, txt and pdf attachments but zips come
through as invalid archives.

I tried changing the MIME to the base64 encoding above for zips but
still got invalid archives.

Anyone know what I am doing wrong?  Both the MIME file and the zip are
code page 819.  Has it got anything to do with the way I am using the
open api (as follows)?

Eval      AttHdl     = open( %Addr( FullNam ):
                        O_RDONLY + O_TEXTDATA )



Regards,

Gerry Tucker
Senior Analyst Programmer
Technicolor Distribution Services
Wembley, U.K.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.