Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!ukma!david
From: david@ms.uky.edu (David Herron -- One of the vertebrae)
Newsgroups: comp.mail.uucp
Subject: Re: BSMTP - Its time has come
Message-ID: <9757@e.ms.uky.edu>
Date: 23 Jun 88 20:08:28 GMT
References: <14605@uunet.UU.NET> <10127@mcdchg.UUCP> <10266@ncc.Nexus.CA> <1787@van-bc.UUCP> <10267@ncc.Nexus.CA> <9593@g.ms.uky.edu> <1793@van-bc.UUCP>
Reply-To: david@ms.uky.edu (David Herron -- One of the vertebrae)
Organization: U of Kentucky, Mathematical Sciences
Lines: 71

In article <1793@van-bc.UUCP> sl@van-bc.UUCP (pri=-10 Stuart Lynne) writes:
>In article <9593@g.ms.uky.edu> david@ms.uky.edu (David Herron -- One of the vertebrae) writes:
>>In article <10267@ncc.Nexus.CA> lyndon@ncc.nexus.ca (Lyndon Nerenberg) writes:
>>>In article <1787@van-bc.UUCP> sl@wimsey.bc.ca (10 Stuart Lynne) writes:
>>>>Something else which could (should) be done is to get BSMTP implemented at
>>>>UUNET. 

>>Getting my bsmtp program to interface to smail would be trivial,
>>merely follow the outline I wrote into domail() (or whatever that
>>routine was named) to call /bin/smail with the right arguments.
>>Easy stuff ...

>Actually it's easier than that. Just have smail use a delivery program which
>can differentiate between sites that can receive BSMTP bundles and ones that
>don't. Messages to the former get routed to a mailer that creates the BSMTP
>message, to the latter get sent to uux rmail!...




We're talking about two different halves of the problem.  For some reason
I was only talking about the receiving site and you're talking about
the sending site.


>>Queueing.  To take advantage of the batching in bsmtp you want to
>>have as many mail messages in the batch as you can manage.  But
>>neither smail or sendmail will handle more than one message at
>>a time, will they?  (My memory on them is a little poor, but I
>>don't remember anything for handling more than one message at
>>any one moment).

>What you have to do is to append the output of the BSMTP program to the end
>of an outbound mailbag, one per site that you talk to. When the size of that
>file exceeds a certain size (say 50k) you dispatch the mailbag to the remote
>site via rmail. Eg:

Yeah, after some thought that's my basic plan also



>	bsmtp ..... >> remote.mailbag
>	...
>	uux remote!bsmtp < remote.mailbag

um, rfc976 already allows for

	uux remote!rmail path!b-smtp
	uux remote!rmail b-smtp

So let's use that scheme, please?



>>[Some things I said about routing issues, but I accidentally deleted ...]
>I don't think you tell the world. BSMTP mail bundles simply replace smaller
>single message files on a single hop. So if you know that uunet can receive
>BSMTP mail bundles (for example by mailing them to uunet!bsmtp) you simply
>place there name in a file listing the hosts that you talk to that can
>receive BSMTP bundles. 

Well, that's fine and dandy if you only want to do BSMTP between two neighbors.
However the stuff in rfc976 allows for BSMTP to be sent to some place
far far away, across many hops.  It would be nice to have some organized
way of doing so.

-- 
<---- David Herron -- The E-Mail guy                         
<---- s.k.a.: David le casse\*'   {rutgers,uunet}!ukma!david, david@UKMA.BITNET
<----                        A proud supporter of the Marcel Marceau Foundation
<------ Because a mime is a terrible thing to waste