Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!seismo!lll-lcc!pyramid!ncc!lyndon
From: lyndon@ncc.UUCP
Newsgroups: comp.os.minix,comp.mail.uucp
Subject: Re: uucp
Message-ID: <1380@ncc.UUCP>
Date: Sat, 4-Apr-87 03:15:47 EST
Article-I.D.: ncc.1380
Posted: Sat Apr  4 03:15:47 1987
Date-Received: Sun, 5-Apr-87 09:42:47 EST
References: <480@gouldsd.UUCP> <43183@beno.seismo.CSS.GOV> <7319@boring.mcvax.cwi.nl>
Distribution: comp.os.minix
Organization: Nexus Computing Corp.,  Edmonton, AB
Lines: 15
Keywords: mail RFC822
Xref: utgpu comp.os.minix:500 comp.mail.uucp:403

In article <7319@boring.mcvax.cwi.nl>, jack@mcvax.cwi.nl (Jack Jansen) writes:
> [...]
> Of course, you won't have sequence numbers and callback and all that stuff,
> but do you *really* care? Just restrict micros to sending mail, and that's
> all.

As the "world" adopts RFC822 for mail, it will be important that any
mailer systems understand the envelope syntax required by the standard.

If you only want to exchange mail with local (PC based) sites, or BBS
systems, you don't require anything fancy. On the other hand, if you
want to talk to the world, you are going to need software capable of
generating (and understanding) the headers.

The routing problem isn't going to get any easier either...