Archive-Date: Sun, 7 Sep 2003 16:15:47 -0700 From: "Kurt A. Schumacher" Reply-To: MX-List@MadGoat.com To: Subject: Sending MIME encoded messages (MX V5.3 on TCPware V5.6) Date: Mon, 8 Sep 2003 01:15:41 +0200 Message-ID: <000001c37595$f52deb30$14010a0a@home.schumi.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit All, Bet this has been covered elsewhere, but the resources have disappeared. How can we send MIME encoded messages e.g. by applications or the VMS V7.3 MIME utility (not a single MIME encoded message by SEND/FOREIGN/TYPE=1 - this works fine, but we don't like the empty mail with the single attachment)? OpenVMS Mail is adding an empty line at the beginning, so every (or most) mail tool will display it in plain text... -Kurt. HP-Interex.ch ================================================================================ Archive-Date: Mon, 8 Sep 2003 00:29:18 -0700 From: "Kurt A. Schumacher" Reply-To: MX-List@MadGoat.com To: Subject: RE: Sending MIME encoded messages (MX V5.3 on TCPware V5.6) Date: Mon, 8 Sep 2003 09:29:12 +0200 Message-ID: <001301c375da$e6eb5a90$14010a0a@home.schumi.ch> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <000001c37595$f52deb30$14010a0a@home.schumi.ch> Received two private messages from Colin and John. John suggested to use MX_SITE_IN - works basically, but is not the "nice" way. Colin suggested the usage og OVMS-MIME to create the file, and send using something like $ mail /noedit/subj="this is what you requested" - mail_temp.txt "fred@a.b.c" This is exactly what I tried. Found the statement making the clients go wrong - but this part is _not_ a part of the MIME encoded file. Return-Path: Original-Recipient: rfc822;KURT.SCHUMACHER@SCHUMI.CH Received: by decus.ch (MX V5.3 AnGc) id 6; Mon, 8 Sep 2003 09:11:11 +0200 Date: Mon, 8 Sep 2003 09:11:10 +0200 From: Kurt.Schumacher@decus.ch To: Kurt.Schumacher@schumi.ch Message-ID: <00A25971.9BDCF672.6@decus.ch> Subject: TEST.MIME MIME-Version: 1.0 <-----!!!!!!!!!! Content-Transfer-Encoding: 7bit <-----!!!!!!!!!! Content-Type: text/plain; charset="iso-8859-1" <-----!!!!!!!!!! MIME-version: 1.0 <-- first line of my file Content-Type: multipart/mixed; boundary="OpenVMS/MIME.6073.1062977491" Content-Transfer-Encoding: 7bit Message-ID: <6073.1062977491@OpenVMS> --OpenVMS/MIME.6073.1062977491 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Intro - Text only -Kurt. --OpenVMS/MIME.6073.1062977491 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename ... What does add this faux MIME header then? VMS Mail? MX? ??? -Kurt. -----Original Message----- From: Kurt A. Schumacher [mailto:Kurt.Schumacher@schumi.ch] Sent: Monday, September 08, 2003 1:16 AM To: MX-List@MadGoat.com Subject: Sending MIME encoded messages (MX V5.3 on TCPware V5.6) All, Bet this has been covered elsewhere, but the resources have disappeared. How can we send MIME encoded messages e.g. by applications or the VMS V7.3 MIME utility (not a single MIME encoded message by SEND/FOREIGN/TYPE=1 - this works fine, but we don't like the empty mail with the single attachment)? OpenVMS Mail is adding an empty line at the beginning, so every (or most) mail tool will display it in plain text... -Kurt. HP-Interex.ch