From owner-freebsd-current  Tue Mar 25 03:55:43 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id DAA07867
          for current-outgoing; Tue, 25 Mar 1997 03:55:43 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA07859;
          Tue, 25 Mar 1997 03:55:32 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id WAA25361; Tue, 25 Mar 1997 22:52:23 +1100
Date: Tue, 25 Mar 1997 22:52:23 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703251152.WAA25361@godzilla.zeta.org.au>
To: asami@vader.cs.berkeley.edu, wosch@freebsd.org
Subject: Re: -current uudecode can't grok one of japanese/vfxdvi's distfiles
Cc: current@freebsd.org, mita@jp.FreeBSD.org
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Looking at the uudecode source, this change seems to be the difference.
>
>===
>revision 1.5
>date: 1997/02/18 17:49:43;  author: wosch;  state: Exp;  lines: +32 -1
>Better check for detecting header line. A header line must match
>"begin [0-7]* *". Now `begin with, ' is not a header line.
>
>Do a boundary check for body characters. Characters less than 33 or
>greater than 96 are out of range. If characters are out of range
>uudecode print a error message and die.
>===
>
>Is this check really necessary?  This file used to decode fine with
>the old decoder.  Besides, I can't figure out for the life of myself
>which character it's barfing on.

Someone send me a uuencoded gzipped file with spaces in it.  I changed
the spaces to backquotes and it uudecoded correctly.

Bruce