🚀 go-pugleaf

In article <2548@soma.bcm.tmc.edu>, sob@soma.bcm.tmc.edu (Stan Barber) writes:
> uumail sources have been submitted to mod.sources for distribution.
> My thanks to all the nice folks who beta tested the software for me.

   We had been using an old version of the 'address' and 'uupath' utilities
that came with uumail; I was reluctant to actually replace rmail with uumail
at the time since I didn't trust it or the maps too much.  When the newer
version of uumail came out several months ago I was quite excited, but it
did nothing but core dump on our Pyramid, and made lint puke too, so I didn't
investigate further.  I didn't know it was a beta version.

   The versions of uumail that I have seen so far depend on a 'domains'
file to figure out how to get to .domains.  Recently the mod.maps files
are including d.* files explicitly indicating domain connections and
these are handled by pathalias ok.  'smail' by the UUCP Project folks
uses only the pathalias database to figure out everything.  I think
this is an advantage, assuming the d.* files are kept up-to-date.
Instead of having a manually-updated domains file doesn't it make more
sense to use the domain connections as posted with the uucp maps and as
used by smail?

  One thing that smail is lacking is the capability for doing what the
uumail 'address' and 'uupath' routines do, i.e. show the paths that would
be used.  A minor change to smail involving addition of an extra -option
accomplishes that easily.


...Rick			..{cbmvax,pyrnj,psuvax1,bpa}!vu-vlsi!perry
			perry@vuvaxcom.bitnet