|
Slava, It's all to do with the BOUNDARY statements which can be nested. If you happened to get the SNDEMAILSP code working then you can observe this in the complete mime header passed to the API for multiple attachments by debugging immediately before the call to the API ( the API deletes the header automatically when it's done). Cheers, Peter -----Original Message----- From: Slava Zharichenko [mailto:Slava.Zharichenko@exel.com] Sent: Tuesday, March 13, 2001 8:25 AM To: RPG400-L@midrange.com Subject: as400 RPG/Email multiple attachment question. Thanks group for helping me with email options . It is easy once you see sample code. The thing i can not figure out now is multiple attachement. For some reasone email client does not see my mime messsage with multiple attachements , it sees only one. Any idea? Sender: TEST@EXE.COM Date: From: <TEST@EXE.COM> MIME-Version: 1.0 To: SLAVA.ZHARICHENKO@EXEL.COM Subject: test Content-Type: multipart/mixed; boundary="--PART.BOUNDARY.1" Content-Disposition: inline This is a multi-part message in MIME format. ----PART.BOUNDARY.1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit test message ----PART.BOUNDARY.1 Content-Type: application/octet-stream; name="test.txt" Content-Disposition: attachment; filename="test.txt" Content-Transfer-Encoding: base64 VGhlIFNlcnZpY2UgUGFjayAoIlNlcnZpY2UgUGFjayIpIGNvbnRhaW5zIHVwZGF0ZWQgdmVyc2lv ***** i deleted that the rest of the records leaving first and last one Y2UgUGFjay4NCg0KDQoNCg== ----PART.BOUNDARY.1-- Content-Type: application/octet-stream; name="input.txt" Content-Disposition: attachment; filename="input.txt" Content-Transfer-Encoding: base64 cGdwIC1lIGM6XHRlc3QudHh0IFNsYXZh ----PART.BOUNDARY.1-- ______________________________________________________________________ Important Email Information The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you are not the intended addressee please contact the sender and dispose of this e-mail. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- This communication is confidential and may be legally privileged. If it is not addressed to you, you are on notice of its status. Please immediately contact us at our cost and destroy it. Please do not use, disclose, copy, distribute or retain any of it without our authority - to do so could be a breach of confidence. Thank you for your co-operation. Please contact us on (09) 356 5800 if you need assistance. +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
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.