🚀 go-pugleaf

Well.  I have one written in YACC, not Lex.  Will that do?

It came to me from Daniel Karrenberg <dfk@unido.uucp>, and he got it
from Bill Nesheim <bill%bullwinkle@crnlcs.bitnet>.  It includes a note
from Bill saying to give it to whoever wants it ... so, I'm
offering...

From what I've gathered from looking at it, it does a good job of
parsing RFC-822.  But then I've had it for a year and a half and
haven't done anything much with it.

It's possible either one of the above two people have done something
more with the code.   I dunno.

If enough people ask for it I can post it to somewhere.  Probably
comp.sources.misc since it doesn't quite match the standards that r$
wants to keep.  If you're on the internet you can ftp anonymously to
"{a,g,e}.ms.uky.edu" and look in "archive/wrk/Network/Mail/Rfc.822" for
the sources.  (After hours is preferable, and access from "a" is preferable
since the files are physically stored on "a").

[ We have a large pile of software which hasn't been sorted through
  which people are welcome to look through ... If you have problems
  connecting the address is [128.163.128.{1,5,7}] (1 is for "a", 5
  for "e", and 7 for "e" ... If you still have problems send me mail
  describing the problem].


-- 
<---- David Herron,  Local E-Mail Hack,  david@ms.uky.edu, david@ms.uky.csnet
<----                    {rutgers,uunet,cbosgd}!ukma!david, david@UKMA.BITNET
<---- I thought that time was this neat invention that kept everything
<---- from happening at once.  Why doesn't this work in practice?