Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!ucbarpa.Berkeley.EDU!fair
From: fair@ucbarpa.Berkeley.EDU.UUCP
Newsgroups: comp.os.minix,comp.mail.uucp
Subject: Re: uucp mail inefficiency
Message-ID: <18164@ucbvax.BERKELEY.EDU>
Date: Fri, 3-Apr-87 08:39:11 EST
Article-I.D.: ucbvax.18164
Posted: Fri Apr  3 08:39:11 1987
Date-Received: Sun, 5-Apr-87 03:07:04 EST
References: <7326@boring.mcvax.cwi.nl> <2629@phri.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Distribution: world
Organization: USENET Protocol Police, Western Gateway Division
Lines: 18
Keywords: uucp uucico kermit
Xref: utgpu comp.os.minix:487 comp.mail.uucp:399

UUCP mail can be sent one copy for multiple recipients to any host
except a 4.1 BSD UNIX (their "rmail" is screwed up). However, in all
cases, you will run up against the size of the command execution
buffer in UUXQT, which will ungracefully core-dump when you exceed it.

If we really wanted to do this right, there is a version of the SMTP
(Simple Mail Transfer Protocol) for batched systems that BITNET uses
called (strangely enough) BSMTP (for Batched SMTP). Someone could
write a new command to be executed on the remote end of a UUCP link
(let's say "bsmtp" with no arguments), and it can read standard input
for the BSMTP protocol and the letter(s), which can be of arbitrary
length, since we're getting it on stdin, rather than in the command
line argument buffers.

I can probably cause the RFC to be posted to mod.sources.doc if enough
people are interested.

	Erik E. Fair	ucbvax!fair	fair@ucbarpa.berkeley.edu