Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.nla.gov.au!act.news.telstra.net!psgrain!news.uoregon.edu!newsfeed.internetmci.com!swrinde!howland.reston.ans.net!vixen.cso.uiuc.edu!uwm.edu!news.sol.net!uniserve!usenet From: tom@uniserve.com (Tom Samplonius) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: sendmail.cf bug? Date: 18 Mar 1996 01:20:18 GMT Organization: UNIServe Online Lines: 36 Distribution: world Message-ID: <4iidoi$lgq@atlas.uniserve.com> References: <31487508.266262635@aquila.sni-usa.com> NNTP-Posting-Host: pc.sdf.com Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII X-Newsreader: WinVN 0.99.6 In article <31487508.266262635@aquila.sni-usa.com>, hsnyder@sni-usa.com says... > >Here is a possible bug with the sendmail ruleset shipped with FreeBSD >2.1 (sendmail 8.6.12.1): > >My domain is set with > CPtrans.sni-usa.com >Addresses of the form > joe@trans.sni-usa.com >get transformed into > joe@trans.sni-usa.com.sni-usa.com > >The rule that does this is in Ruleset 96 - "bottom half of Ruleset 3" > R$* < @ $* $~P > $* $: $1 < @ $[ $2 $3 $] > $4 >As I read this rule, it should fail if the input ends with any member >of class P. Instead, ~P matches "com" and $* matches "trans.sni-usa." >causing the problem above. > >Commenting out the rule in question makes the problem go away. It >sure looks as if this rule is not doing what it was intended to, but I >am too new to sendmail to know whether the problem is with 1) my >configuration, 2) the default sendmail.cf file, or 3) the sendmail >binary. ?? The real problem is that you have a wildcard MX setup for sni-usa.com. This is a bad thing (tm), and requires special handling. Wildcard MX's are discouraged these days. What is happening here, is that because you have the line "domain sni-usa.com" in resolv.conf, the resolver tries the lookup with sni-usa.com appended first, and if that fails try a lookup unmodified. However, since you have a wild-card MX defined, the first lookup always works. A temporary workaround would be to be remove the "domain" line from resolv.conf. Tom