Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!eecae!netnews.upenn.edu!rutgers!att!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.mail.elm
Subject: Re: Missing text when printing
Message-ID: <7779@chinet.chi.il.us>
Date: 21 Feb 89 04:26:35 GMT
References: <447@ciss.Dayton.NCR.COM> <63@dsinc.UUCP>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Distribution: usa
Organization: Chinet - Public Access Unix
Lines: 24

In article <63@dsinc.UUCP> syd@dsinc.UUCP (Syd Weinstein) writes:

>How we solved this problem for the future is we extended Elm to try
>and cope with non RFC 822 mailers.  We now define the end of the
>header as the first line that doesn't look like a header or a header
>continuation line.  We can still get confused by lines that look
>like headers, so it isn't a total fix.
>(A header is a line starting in column 1 and containing a :, or a line
>following a header line that starts with whitespace)

Why don't you add the ability to recognize the headers used by AT&T's
PMX mailers and the replacement for /bin/mail that comes with them?
(I suspect this will become standard in SysVr4.)
There is a Content-Type: header followed by a Content-Length: header.
There is one blank line after the Content-Length header, then the
number of characters specified as the length are unambiguously the
body so you don't have to worry about lines that start with "From" or
things that look like headers.  A "Content-Type: Multipart" may precede
several attachments, each with its own Content-Type: and Content-Length:
header.  It is a very handy feature to be able to attach files to mail
and the PMX mailers will allow binary attachments if the receiving
machine and intermediates are known to allow them.

Les Mikesell