From: rich@example.invalid   
      
   Mike Spencer  wrote:   
   >   
   > Rich  writes:   
   >   
   >> Mike Spencer  wrote:   
   >>   
   >>> It would be convenient to be able to query the sendmail daemon to see   
   >>> what it was using as nameservers and avoid a restart if one isn't   
   >>> needed.   
   >>   
   >> Not sure that is possible.  Sendmail (and mail servers in general) are   
   >> going to assume stable, static IP values, and so it is very doubtful   
   >> there is any official way to ask the daemon what nameservers it is   
   >> using.  Reason being that in a static environment, there's no need to   
   >> ever bother doing so.   
   >>   
   >> But, if the sendmail daemon's only task is to deliver outgoing mail to   
   >> a smarthost, what about configuring sendmail with the IP address of the   
   >> smart host?  Then it won't need to do a DNS lookup to get the smart   
   >> host's IP, and changing resolv.conf won't matter to it.  All that will   
   >> matter is that it can connect to that IP address via the current in use   
   >> network path.   
   >   
   > That's a good idea.  I'm using the mailertable mechanism which, AIUI, is   
   > distinct from the smarthost one.  But I could put the IP address in   
   > the mailertable & authinfo files, rebuild the corresponding .db files   
   > and see if the problem goes away.  Don't have to mess with sendmail.cf.   
      
   Seems it is worth a try.  It is likely your simplest item to try.   
      
   > My mail provider is a mom&pop ISP that seems to jockey IP addresses   
   > around from time to time but I can stay alert to that.   
      
   Yeah, you'll have to manually follow their changes if you go this   
   route.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)