Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!rickert From: rickert@mp.cs.niu.edu (Neil Rickert) Newsgroups: comp.mail.sendmail Subject: Re: IBM Do It Again Message-ID: <1991Apr12.155948.29233@mp.cs.niu.edu> Date: 12 Apr 91 15:59:48 GMT References: <1991Apr10.214922.23442@pa.dec.com> <1991Apr12.145344.7135@csl.dl.nec.com> Organization: Northern Illinois University Lines: 37 In article <1991Apr12.145344.7135@csl.dl.nec.com> ylee@csl.dl.nec.com (Ying-Da Lee) writes: > >Is it really stated in any "formal" document that S3 is to be >idempotent? This is news to me and there are a great number of >sendmail.cf's out there that have non-idempotent S3. None of >Sun's sendmail.cf's I have seen, for example, have idempotent S3. I do not know of anything in sendmail that requires S3 be idempotent. It is very common for the first few rules of S3 to convert User Name into just user@domain and it is very common for the last few rules to convert user@domain into user<@domain> With such a practice, S3 cannot be idempotent. What is sometimes done is for another ruleset to convert 'user<@domain>' back to 'user@domain' then run it through ruleset S3 again. This usually happens after some reformatting, such as converting a!b into b@a.uucp. -- =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Neil W. Rickert, Computer Science Northern Illinois Univ. DeKalb, IL 60115 +1-815-753-6940