Sami Farin wrote:
> On Tue, Jan 30, 2007 at 13:03:29 -0600, Matthew R. Dempsky wrote:
>> On Tue, Jan 30, 2007 at 11:49:15AM -0500, Phil Breskey wrote:
>>> I added a line to my /etc/tcp.smtp like this:
>>>
>>> 70.87.77.70:allow,RELAYCLIENT="",RBLSMTPD="",QMAILQUEUE="/var/qmail/bin/qmail-queue"
>> Do you set GREETDELAY in /service/qmail-smtpd/run? If so, you need to
>> instead set GREETDELAY for each appropriate line in /etc/tcp.smtp,
>> otherwise GREETDELAY will still be set for 70.87.77.70.
>>
>> (Times like this make me wish tcprules/tcpserver had a built-in syntax
>> for selectively unsetting environment variables.)
that's why its best you not set 'global' environment variables in your
run script and try to disable them in tcprules. You simply set a
'default' rule in your tcprules and it will handle it from there.
For instance, my 'default' rule looks like this:
:allow,QMAILQUEUE="/var/qmail/bin/qmail-scanner-queue",GREETDELAY="30"
It does make for 'some' redundancy, and also for some tedium if I want
to change the 30 to say, 20, globally, but I'm using a fairly small
tcprules file, so running a search/replace on it isn't that hard, and if
I was managing a much larger one, I would just generate it from some
sort of database or using a macro language like m4.
> 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.
As for RBLSMTPD... if you're setting RBLSMTPD="" to disable rblsmtpd for
an IP, simply refrain from setting GREETDELAY. Also, you should run
greetdelay *after* rblsmtpd, so there's no delay if rblsmtpd is just
going to tell them to screw off anyways.
-Jeremy
signature.asc
Description: OpenPGP digital signature
|