HP3000-L Archives

September 1999, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Chris Bartram <[log in to unmask]>
Reply To:
Date:
Tue, 28 Sep 1999 17:17:22 -0400
Content-Type:
Text/Plain
Parts/Attachments:
Text/Plain (55 lines)
 In <[log in to unmask]> [log in to unmask] writes:

> I'm using a small e-mail system created by Telamon (I'm really not sure what
> the name of the program is but the version information says "28Apr99-09:28
> (A.01.58) MPE/iX Telamon, Inc. (C) 1994, 1999").  It's a great little
> program but now I need to send an attachment but I need to specify the file
> extension to be .doc so that my client can just click on the attachment and
> open it up in Word.  Any one know how to specify an extension and not use
> the default .txt?

You have two options;

  Some mail clients will parse 'uuencoded' attached files; you would uuencode
the attachment, then include that attachment in your message. Uuencoded files
include (as part of the attachment) the name of the original file; if you used
a .doc file, it would be labelled that way and *IF* the client you're sending
to can parse uuencoded imbedded files, you should be able to 'click' on the
attachment to launch the viewer for that file-type.

  The other way (more complicated but more reliable) is to add appropriate
labels in the mail message. These labels are defined in various RFCs, and
are collectively referred to as "MIME" (Multipurpose Internet Mail Extensions)
Doing this with a manual client (like the mail client you refer to) will
require you to:
 1) add MIME-Version: 1.0  headers to the header part of the message
 2) add a Content-Type: header to the header part of the message, with a
    boundary-string (assuming you'll be creating a "multipart" message)
 3) encode the 'doc' file using uuencode or (preferably) MIME's BASE64
    encoding scheme
 4) adding boundary strings before and after the attachment
 5) adding content-type: and content-transfer-encoding: labels after the
    boundary and before the actual contents of the attachment

Not much fun, admittedly, though it is possible with some creative script-
writing I suppose.

<plug> Another option is to use NetMail/3000, which does all that for you.
It can lookup a file's type (by filecodes for MPE files or .extensions for
files attached from a pc) and will create all the appropriate MIME labels
for you (or even uuencode if you insist). 1-800-NetMail for info/demo. </plug>

     -Chris Bartram


______________________/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
  Chris Bartram        Sales (US):   800 Net-Mail    Fax:+1 503 361-8895
   ______                         +1 503 361-8850    mailto:sales at 3k.com
  /__ |  \__________   Sales (Europe):+44(1480)414131 Fax:+44(1480)414134
 /  / | / ________     Sales (Pacific):+61 3 9488 4333 Fax:+61 3 9482 5124
|  /_ |<  ______       Tech Support:+1 503 361-8833
 \ __)| \ ___          mailto:support at 3k.com       Me: rcb at 3k.com
  \______/Associates,  PO Box 6003, Springfield VA 22150
_________________Inc._/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
Gopher: gopher.3k.com   Anon-FTP: ftp.3k.com  WWW: http://www.3k.com/

ATOM RSS1 RSS2