whitelist_hosts not being used?

[SupermanInNY]

I have lots of instances where whitelist_hosts are not included and as such,. users are not able send or recieve from blacklisted ips.

/etc/virtual/whitelist_hosts

Here is a sample of my IPs listed.
I'm not sure how to include entire classes correctly, so I'm trying all sorts of ways to do that.

How do I get to whiltelist 89.1.x.x all IPs?


87.70.150.0/23
87.70.152.0/22
87.70.238.109
87.70.64.0/18
89.1.0.0/16
89.1.0.0/17
89.1.0.0/18
89.1.95.124
89.138.0.0/16
89.138.0.0/17
89.138.0.0/18
89.138.0.0/20
89.138.172.3

Thanks,

-Alon

 

[nobaloney]

Subnets in whitelist_hosts may work in the latest SpamBlocker Version 3-beta. If not, then you can ask me to post a later version and I will.

However you MUST put all the IP#s at the top of the file. The final release version won't have this restriction, but will probably use separate files for IP#s and server names.

You can't just use arbitrary numbers after the slash; check this Wikipedia article; it's a great reference which I use whenever I work on networks.

Jeff

 

[SupermanInNY]

I always get myself confused with the classes.

a.b.0.0/16 +0.0.255.255 255.255.000.000 65,536 256 C = 1 B
a.b.0.0/15 +0.1.255.255 255.254.000.000 131,072 2 B b = 0 ... (2n) ... 254
a.b.0.0/14 +0.3.255.255 255.252.000.000 262,144 4 B b = 0 ... (4n) ... 252
a.b.0.0/13 +0.7.255.255 255.248.000.000 524,288 8 B b = 0 ... (8n) ... 248
a.b.0.0/12 +0.15.255.255 255.240.000.000 1,048,576 16 B b = 0 ... (16n) ... 240
a.b.0.0/11 +0.31.255.255 255.224.000.000 2,097,152 32 B b = 0 ... (32n) ... 224
a.b.0.0/10 +0.63.255.255 255.192.000.000 4,194,304 64 B b = 0, 64, 128, 192
a.b.0.0/9 +0.127.255.255 255.128.000.000 8,388,608 128 B b = 0, 128

of all of the above, in order to capture the following: 89.1.0.0/16 Is that the most comprehensive covering 89.1.0.0 to 89.1.255.255 ?
That's what I'm looking for.

I'm using: SpamBlocker.exim.conf.2.1.1-release 05-Jun-2007

And that one doesn't handle subnets?

thanks,

-Alon.

 

[nobaloney]

I always get myself confused with the classes.

Classes are actually easier than classless routing: there are only four classes: A, B, C, D. But they depend not only on the number of bytes in the network, but also the value of the bytes.

So to make life easy we look at Classless Inter-Domain Routing. That way we don't care if it's a real Class allocation or simply a small part of a larger Class allocation.

But classless subnetting may seem a bit more complex. What you're looking at (89.1.0.0 - 89.1.255.255 is a /16 cidr block.

in order to capture the following: 89.1.0.0/16 Is that the most comprehensive covering 89.1.0.0 to 89.1.255.255 ?
That's what I'm looking for.

Yes, that's a /16 cidr block (usually just called a /16 [pronounced slash sixteen]).

How do we know?

You can learn how to count bits; I actually learned it that way. But it's easier to just look it up in a table; hence my link .

I'm using: SpamBlocker.exim.conf.2.1.1-release 05-Jun-2007

And that one doesn't handle subnets?

No, it doesn't. You can rewrite it, or you can update to Version 3-beta.

It's only beta because I keep working on it; it works fine.

You might be better off with my latest running version; let me know and I'll post it for you to download. (It's setup directions are a bit more complex, but it's got complete documention in the file.)

Jeff