I ran into a similar situation, but in our case we wanted to waive
the requirements for SMTP Auth for local nets. I wrote a plugin that
handles this (although I don't think it ever got integrated b/c the
smtp auth stuff is/was being reworked) - see the attached code, it
should give you a good starting point from which you only have to
change a few things... But this has me wondering if it might make
more sense to have a more generic framework that can be called from
any plugin you desire. So for example you'd have something like a
config/ip_overrides, that looked a little like this:
check_earlytalker:
ip 192.168.0.
auth_secure_conditions:
port 465
ip 192.168.0.
$PLUGIN1:
$skip_condition1
...
$skip_conditionN
...
$PLUGINn:
Are there other circumstances in which chaining things like this for
ip/port/etc. restrictions might come in handy?
Cheers,
Brian Szymanski
[EMAIL PROTECTED]
On Jan 4, 2007, at 10:55 AM, [EMAIL PROTECTED]
wrote:
Lo all,
I have a line in my config for check_earlytalker:
check_earlytalker 1 log 0
I've put it to log because it was rejecting connections from
some internal systems, possibly blat or a java scheduler.
Is it possible, currently, to configure check_earlytalker
to _not_ check particular ip addresses? eg 192.168.0.*
John
