From owner-freebsd-hackers Wed May 31 12:26:46 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA12589 for hackers-outgoing; Wed, 31 May 1995 12:26:46 -0700 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA12560 for ; Wed, 31 May 1995 12:26:35 -0700 Received: by haven.uniserve.com id <208>; Wed, 31 May 1995 12:43:09 -0700 Date: Wed, 31 May 1995 12:42:57 -0700 (PDT) From: Tom Samplonius To: Nate Williams cc: "Jonathan M. Bresler" , hackers@FreeBSD.ORG Subject: Re: mailing lists In-Reply-To: <199505311809.MAA12856@trout.sri.MT.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.ORG Precedence: bulk On Wed, 31 May 1995, Nate Williams wrote: > FWIW, our ISP recently switched *from* Zmailer back to sendmail after > they had lots of problems with it. According to our ISP, Zmailer didn't > support things such as aliases, .forward file, and such w/out alot of > work and in their environment sendmail was much easier to maintain over > the long-term. Competely bogus. Zmailer supports aliases. Zmailer has special security consisderations for .forward files, but you can override them so they work just like Sendmail. Unless, you speak sendmail.cf as as a second-language, Zmailer will be easier to configure. However, Zmailer isn't without problems, but those certainly aren't them. Main problem is some weirdness in the scheduler of versions 2.99.X that cause it to generate bogus error messages. Either use 2.2e6, or 2.99.14 with a scheduler from an earlier version. Tom