Xref: utzoo comp.lang.perl:334 comp.mail.misc:2917 Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!uflorida!usfvax2!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.lang.perl,comp.mail.misc Subject: Sendmail in Perl Message-ID: <25D2D161.124C@tct.uucp> Date: 9 Feb 90 14:19:12 GMT References: <1004@frankland-river.aaii.oz.au> <14678@fluke.COM> <1990Feb6.223117.16428@iwarp.intel.com> <20620@watdragon.waterloo.edu> <7013@jpl-devvax.JPL.NASA.GOV> <1990Feb8.032115.5667@iwarp.intel.com> Organization: ComDev/TCT, Sarasota, FL Lines: 24 According to merlyn@iwarp.intel.com (Randal Schwartz): >According to lwall@jpl-devvax (Larry Wall): >| Actually, I was thinking about what I'd need to write the new rn in perl. >| I don't want to rewrite sendmail. (Not consciously, anyway. :-) > >But Larry! You could write the "canonical sendmail", and then all the >rewrite rules would be in Perl, and user's customized delivery scripts >would be handled by 'do $HOMEOF{$user} . "/.deliver.pl";', and >everything would be wonderful! But, get 'rn' in Perl finished first. The similarity of Randal's hypothetical ".deliver.pl" to my real ".deliver" can't be a cooincidence. Deliver (currently at version 2.0; patch five will be out soon) executes scripts to control mail delivery. User delivery scripts are named "$HOME/.deliver". As distributed, Deliver runs scripts with "/bin/sh", and I'd say that's a reasonable default for user delivery files. But system delivery files can be complex, especially if you're attempting to parse network addresses. Perl is an excellent choice for such jobs. So, in a manner of speaking, Sendmail in Perl already exists. -- Chip Salzenberg at ComDev/TCT , "The Usenet, in a very real sense, does not exist."