Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!cmcl2!yale!husc6!think!rutgers!lll-crg!hoptoad!gnu
From: gnu@hoptoad.uucp (John Gilmore)
Newsgroups: net.bugs.usg,net.bugs
Subject: Re: bugs in /bin/mail
Message-ID: <1185@hoptoad.uucp>
Date: Sat, 11-Oct-86 03:28:06 EDT
Article-I.D.: hoptoad.1185
Posted: Sat Oct 11 03:28:06 1986
Date-Received: Sat, 11-Oct-86 21:39:44 EDT
References: <1196@ncr-sd.UUCP>
Organization: Nebula Consultants in San Francisco
Lines: 25
Xref: mnetor net.bugs.usg:392 net.bugs:346

In article <1196@ncr-sd.UUCP>, matt@ncr-sd.UUCP (Matt Costello) writes:
>                         Why does mail go to so much trouble to preserve
> nulls in a mail file? ...                           Does anyone see any
> reason why stripping nulls would have a detrimental effect?

Yes.  Mail should just act as a transportation mechanism without imposing
any meaning on the data being transported.  In particular, making
assumptions like "nobody would want nulls in a message" is imposing
a meaning ("Nulls are useless in mail messages").

In point of fact, if mail and news would carry nulls without trouble,
we would not have to uuencode binary programs to mail them to each other,
post them to the net, etc.  Since people started mailing binaries
around, this has been noticed, and I applaud the System V maintenance
team for fixing this in their /bin/mail.  Berkeley hasn't fixed it,
to my knowledge, and if Sun has fixed it (they know about it), they
haven't shipped the fixed release yet.

There are also problems with bytes in which the top bit is set, at
least in Sun/Berkeley mail.  Further problems appear if you send text
which has long stretches without newlines.  If anyone wants specific
bug reports, ask me for a copy -- or try it yourself!
-- 
John Gilmore  {sun,ptsfa,lll-crg,ihnp4}!hoptoad!gnu   jgilmore@lll-crg.arpa
(C) Copyright 1986 by John Gilmore.             May the Source be with you!