On Fri, 26 Jan 2001 4:56:14 GMT,
[EMAIL PROTECTED] (Samuel W. Heywood) wrote:
>
> I'm getting even with you guys for disparaging one of my favorite mailers
> by insinuating that NetMail cannot be set up so as to integrate very nicely
> with external programs such as mpack for encoding attachments and inserting
> MIME headers. Behold, I send you an example:
>
> Sam Heywood
> - -- Message sent by NetMail DOS, v. 2.12 and using OLIM, v. 1.40
>
> - ---==========---
> Content-Disposition: attachment; filename="GET_EVEN.GIF"
> Content-Type: application/octet-stream; name="GET_EVEN.GIF" <====
> Content-Transfer-Encoding: base64
Nothing wrong with NetMail, but as far as I know, MIME is handled
by the mailreader, not the mailer. In this case, OLIM calls the
external program pointed to by the "mencoder" line in olim.rc to
encode the attachment and insert the MIME headers. NetMail just
sends the resulting text message.
I also believe it is the Content-Type that Howard S. is asking
about. Running mpack or muencode -a from the command line, I
get something like this.
--==_MUencode_2001-Jan-26_20:37:35
Content-Type: image/gif; name="get_even.gif" <====
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="get_even.gif"
Since I hardly ever use MIME in practice, I haven't tried to get
this to work with different mailreaders. As has been pointed out,
Arachne does it "right", although I'm not even sure why image/gif
is "right" and application/octet-stream is "wrong", since I can
decode the attachment in either case.
Howard E.
--
DOS TCP/IP * <URL:http://www.ncf.ca/~ag221/dosppp.html>
