Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!tut.cis.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: frozen $s in 5.65 + ida-1.4.2 Message-ID: <1991Feb25.142401.735@mp.cs.niu.edu> Date: 25 Feb 91 14:24:01 GMT References: <1991Feb25.090701.25065@wsrcc.com> Organization: Northern Illinois University Lines: 31 In article <1991Feb25.090701.25065@wsrcc.com> wolfgang@wsrcc.com (Wolfgang S. Rupprecht) writes: > >I am having problems with using $s in ruleset S0. It is failing only >*only* if sendmail is run from a frozen config file. It appears that >the $s macro is still frozen when S0 is run. If I freeze in a value >with 'sendmail -bz -oMsFuNkYsTuFf' then I will still see that frozen >value at S0 time. Is this a problem with a known solution? "That's not a bug, that's a feature." It is part of the definition of freezing a configuration that all macro values are frozen. Why on earth would you be putting '-oMsFuNkYsTuFf' on the command line for freezing? It is supposed to be that $s is defined dynamically as the invoking host name. If you receive mail from an SMTP client you should find that $s is redefined. If you have an 'rmail' which includes the '-oMshost' flag this will also happen to mail received via UUCP. Mail from any other source is unlikely to redefine $s, so the value that you defined stays. This treatment - freezing macro values - is no different for $s than for any other macro. If it didn't work that way your configuration file would not be able to define $j which is used in the SMTP protocol to identify the host name. -- =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Neil W. Rickert, Computer Science Northern Illinois Univ. DeKalb, IL 60115 +1-815-753-6940