On Tue, Jan 30, 2007 at 11:23:08 -0800, Jeremy Kitchen wrote:
...
> > You can work around that by having new feature in greetdelay:
> > if env var GREETDELAYDISABLE is set, greetdelay is skipped.
> > Alternatively, greetdelay could skip the delaying if RBLSMTPD is set.
> >
>
> no need. in the greetdelay program I mentioned previously, if
> GREETDELAY is not set, it simply executes its command line arguments
> without delay or checking for input.
That was general idea for working around "tcpserver can't unset
environment".
> As for RBLSMTPD... if you're setting RBLSMTPD="" to disable rblsmtpd for
> an IP, simply refrain from setting GREETDELAY. Also, you should run
And if you set GREETDELAY globally in run file?
And if you have million different other features checking env vars...
Easier to "whitelist" by RBLSMTPD="" . IMHO.
> greetdelay *after* rblsmtpd, so there's no delay if rblsmtpd is just
> going to tell them to screw off anyways.
You can't run greetdelay after rblsmtpd because rblsmtpd already
shows the greeting.
And what's the idea in signing the emails when your public key
is nowhere to be found?
--
pgpoLsmX6he9A.pgp
Description: PGP signature
|