Xref: utzoo news.admin:14591 news.software.b:7902 Path: utzoo!mnetor!tmsoft!eci386!jmm From: jmm@eci386.uucp (John Macdonald) Newsgroups: news.admin,news.software.b Subject: Re: Really funny jokes being missed Message-ID: <1991May23.165452.7964@eci386.uucp> Date: 23 May 91 16:54:52 GMT References: <282FD655.3D2A@tct.com> <5ukZ24w164w@mantis.co.uk> <1991May17.170033.17759@dsuvax.uucp> Reply-To: jmm@eci386.UUCP (John Macdonald) Organization: Elegant Communications Inc. Lines: 19 In article ben@wri.com (Ben Cox) writes: | |This is the lazy man's answer. Given sufficient effort, one could probably |write a shell script that would fix a Date: header. A Path: header would be |harder, but most others are cake. In a word, bullshit! Given sufficient effort, one could write a shell script that would fix a dozen different bad Date: header formats. There would still be people bitching that *their* invalid date format wasn't being fixed (or that, even worse, it *was* being fixed but the fix was *wrong* and Jan 9 gets converted to Sept 1 by the wrong guess of what 1/9 means). There is no way to write any program that will fix bad format headers and be right every time the fix is *obvious* to the originator and his software. -- sendmail - as easy to operate and as painless as using | John Macdonald manually powered dental tools on yourself - John R. MacMillan | jmm@eci386