Hi,
you are stepping into to uncharted territory here
First, there are issues with the wbl contrib working correctly with dnsbl/whitelists
See these two bugs :
V8
http://bugs.contribs.org/show_bug.cgi?id=8327v9
http://bugs.contribs.org/show_bug.cgi?id=8747I believe that qpsmtpd *should* work by default with whitelisted IP addresses (the patch only fixes domain names and individual senders).
However, I am not sure of a format for subnetting. Documentation for plugins is sparse online.
The place to look is in /usr/share/qpsmtpd/whitelistsoft
"=item whitelisthosts
Any IP address (or start-anchored fragment thereof) listed in the
whitelisthosts file is exempted from any further validation during
'connect', and can be selectively exempted at other stages by
plugins testing for a 'whitelisthost' connection note.
Similarly, if the environment variable $WHITELISTCLIENT is set
(which can be done by tcpserver), the connection will be exempt from
further 'connect' validation, and the host can be selectively
exempted by other plugins testing for a 'whitelistclient' connection
note."
Damned if I now what a "start-anchored fragment" is !
The bit of code that does the checking is this :
my $config_arg = $self->{_per_recipient} ? { rcpt => $rcpt, %MERGE } : {};
for my $h ($self->qp->config('whitelisthosts', $config_arg)) {
if ($h eq $ip or $ip =~ /^\Q$h\E/) {
$self->qp->connection->notes('whitelisthost', 1);
$self->log(2,"host $ip is a whitelisted host");
return OK;
But how or what it checks I have no idea ! I have a feeling that this part checks for the start of the IP block :
$ip =~ /^\Q$h\E/
I guess if you were trying to block say :
192.168.10.*
You could try just
192.168.10
I'll try and test that bit and see what it gives as a result unless anyone else knows ?
B. Rgds
John