🚀 go-pugleaf

In demon.ip.support.unix Paul Black <paul@canix.co.uk> wrote:
> Peter McDermott <peter@petermc.demon.co.uk> wrote:
>> 
>> I kill the sendmail demon, and then re-launch it, and everything
>> is fine. So, my question is, is there some way I can stop the
>> punts from attempting to deliver immediately, or does anyone have
>> any other clues what I should do to fix this?

> You could get sendmail to not check the domains, add to .mc file:
> FEATURE(accept_unresolvable_domains)

I'd considered this, though I wanted to avoid it as I
seem to be getting quite a lot of spam recently and
this appears to bounce a fair amount of it. 


> Another way might be to have your own cacheing DNS and use ipchains
> to control access to it, i.e. add/remove rules in ip-down/ip-up.

Ah. I actually am running my own caching DNS (though
I haven't gotten around to setting up ipchains yet.
Could it be that what's happening is that it tries
to resolve the waiting mails before a connection to
demon's dns is established?

Is it essential to firewall my dns? It's not a service
I would have thought likely to be accessed by outside
domains?
 
>> 
>> Question number two, is my suck question. For some reason,
>> I can't seem to run suck from within a script. I've tried to
>> call it from withing ip-up, I've tried it from a script of
>> it's own. Nada. I'm probably missing something completely
>> obvious, but I've no idea what it might be. It runs fine if
>> I just type the same command by hand.

> Is it requiring an environment variable to be set which isn't
> set when called from ip-up?

I don't believe so. I get exactly the same results when I
run the command in a shell script as root, yet it works 
perfectly well if I type it in.

Those enviroment variables are a serious pain in the arse
though. They've caught me out umpteen times in the past.
I'll read the man page again, see if I'm missing anything
obvious.