Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!orchid!egisin
From: egisin@orchid.UUCP
Newsgroups: ont.uucp
Subject: UofT mail being sent over RSCS
Message-ID: <7004@orchid.UUCP>
Date: Fri, 17-Apr-87 08:52:33 EST
Article-I.D.: orchid.7004
Posted: Fri Apr 17 08:52:33 1987
Date-Received: Sat, 18-Apr-87 03:49:46 EST
Distribution: ont
Organization: U of Waterloo, Ontario
Lines: 31

I got some mail from UofT that came via RSCS.
Part of the header follows:

From mailer@utorgpu.bitnet  Thu Apr 16 16:30:02 1987
Received: from watmath.uucp by orchid; Thu, 16 Apr 87 16:30:02 EDT
Received: from watmath.uucp by watdragon; Thu, 16 Apr 87 16:28:57 EDT
Redirected-From: watmath.uucp
Received: from utzoo by gpu.utcs.toronto.edu via phone with UUCP id AA02927;
        Thu, 16 Apr 87 16:29:28 EDT
Date: Thu, 16 Apr 87 16:29:28 EDT
From: henry@utzoo
Message-Id: <8704162029.AA02927@gpu.utcs.toronto.edu>
To: egisin@watmath

The body of the message had empty lines turned into lines
consisting of 3 or 4 blanks, typical of rscs.

My first complaint is that the rscs mailers did not
insert Received lines, so I don't know how the mail was routed.
One of the mailers also failed to rewrite the From address
to include a top level domain, either .uucp or .toronto.edu.

The second complaint is that rscs is known for its inability to
transfer text files between ascii systems without mangling them.
Source code ususally has to be encoded before it can be sent
reliably over a rscs link.  The most common way to do this
is with uuencode, and even that doesn't work with the standard
Unix uuencode because rscs strips trailing blanks from lines.

I assume this routing was done for economical reasons,
but I think it will cause a lot of problems for users.