Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!crdgw1!barnett From: barnett@grymoire.crd.ge.com (Bruce Barnett) Newsgroups: comp.mail.sendmail Subject: Re: Sample sendmail.cf Message-ID: Date: 10 May 91 18:56:25 GMT References: <176@netxcom.netx.com> Sender: news@crdgw1.crd.ge.com Reply-To: barnett@crdgw1.ge.com Organization: GE Corp. R & D, Schenectady, NY Lines: 36 In-reply-to: elw@netxcom.netx.com's message of 5 May 91 23:41:28 GMT In article <176@netxcom.netx.com> elw@netxcom.netx.com (Edwin Wiles) writes: > If you've already got a sendmail.cf that mostly works, lay hands > on the "ease" program and use it. It makes understanding and modifying > sendmail.cf files MUCH easier. (Check your local comp.sources.unix > archives, in volume 17, for a package named "ease2". DO NOT ask me > for source or binaries!) Ease 2 has several problems. I am currently working on Ease 3.2 Beta. Send me mail if you want it. I posted it to alt.sources a while ago. > Unfortunately, it is a bit of a bear to get running, mainly due to > two problems: > > 1) The "cfc" program, which takes an existing sendmail.cf file > and does *most* of the translation work into "ease", will dump > garbage into the output (including nulls) if there are any > syntactical errors in the sendmail.cf file. This is one area I spent a lot of time fixing. I made major changes to ease and cfc (I was not the original author or either) just so I could convert a *.cf file into ease, and convert the ease back into *.cf, and compare the two. In 99% of the cases files I have tried, I could convert back and forth with no errors (warnings - yes) and just a few cosmetic differences changes. > 2) The "et" (ease translator) program makes use of a YACC generated > parser that uses "free()" to release memory apparently allocated > durring translation. Unfortunately, on my machine (a 386 IBM PC > clone, running SCO Xenix), an attempt to free a null pointer will > get you a memory fault core dump. Yes - I fixed this is Ease 3.1. I would have fixed it sooner but my machine never complained about it, and I don't have Saber-C. -- Bruce G. Barnett barnett@crdgw1.ge.com uunet!crdgw1!barnett