🚀 go-pugleaf

jromine@binky.ics.uci.edu (John Romine) writes:

>andys@flatline.sbi.com (Andy Sherman) writes:
>>We are running Solaris 2.1 and I've noticed a change in sendmail.  To better
>>integrate with the multimedia mailtool, sendmail makes sure there are
>>Content-Type and Content-Length headers in every message.  Since it
>>now *knows* the body length of a message, it has no need to prepend a
>>'>' to every line beginning with \nFrom.  So it doesn't.  The result is
>>that when my boss forwards a message to me, inc splits it into two

>What happens if a message already has a content-length header, but
>Sun's sendmail doesn't agree with the length given?  TOPS20 used
>a mailbox format which included file lengths... it sure was a pain
>to edit those mailbox files.

First of all, it isn't sendmail that adds the Content-Length: header,
it is the local mailer. It fixes the Content-length header if you
send a wrong one, as it should. (Or it simply always replaces it).

>As for MH, it supports the UUCP-style (From user date ...) and
>MMDF-style (ctrl-A) mailbox formats.  It doesn't support the newly-
>discovered Solaris-broken-UUCP-style mailbox format.

Ah. The ``ugly hack with >From'' is better? Bullshit. A Content-Length:
header seems the only right way (no need to escape anything in any message).

>It seems likely that other UAs will also not understand the
>Solaris-broken-UUCP-style mailbox format.  Perhaps fixing
>/bin/mail to write the '>' characters is the right thing to do?

Elm does understand Content-Length: headers. MH is the only other
mail agent we have installed that doesn't come with the system. All
Solaris UA understant Content-Length: headers.

Fixing MH would be the proper thing to do.

Casper