Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!uunet!ateng!chip
From: chip@ateng.com (Chip Salzenberg)
Newsgroups: comp.mail.uucp
Subject: Re: Smail, Aliases & Programs
Keywords: smail alias
Message-ID: <2561CDFB.4258@ateng.com>
Date: 15 Nov 89 20:58:34 GMT
References: <590@piglet.vision.UUCP> <974@becker.UUCP> <254733A5.10634@ateng.com> <13074@s.ms.uky.edu> <254CCBB1.19467@ateng.com> <1989Nov2.200712.163@twwells.com> <255344AF.10561@ateng.com> <1989Nov6.064722.15635@twwells.com> <14858@bfmny0.UU.NET>> <1989Nov13.080002
Organization: A T Engineering, Tampa, FL
Lines: 35

According to bill@twwells.com (T. William Wells):
>Well, this all depends on your point of view. Personally, I'd find
>maintaining my mailing list using deliver's mechanisms a bit of a
>bother. Whereas, with lmail, all I do is add a name to a list.

Deliver can arrange to be just that simple to use:

	case "$u" in
	mailing-list)
		awk '{print $1}' /usr/local/lib/mailing-list-file
		;;
	*)
		echo "$u"
		;;
	esac

>I truly hope that no one is taking my comparison of the two
>programs as sniping. But, in case anyone has, let me say this:
>Deliver is a neat idea. Use it if it suits your needs.

And for an opposing view:  Lmail provides enough functionality for most
purposes, and I'm glad its authors are writing and posting.

>remote execution        [uucp job umichC57d9 (11/9-16:51:16)]
>	rmail b-tech!zeeff
>exited with status 139
>
>	===== stderr was =====
>sh: 16679 Memory fault

Looks like Jon Zeeff's lmail has a null pointer dereference.  :-) :-)
-- 
You may redistribute this article only to those who may freely do likewise.
Chip Salzenberg at A T Engineering;  <chip@ateng.com> or <uunet!ateng!chip>
    "Did I ever tell you the Jim Gladding story about the binoculars?"