Why not support CIDR notation for block lists?

Post your MailEnable suggestions here.
Post Reply
Crazyyeti
Posts: 8
Joined: Fri Jan 12, 2007 6:06 pm
Location: Denver, CO USA

Why not support CIDR notation for block lists?

Post by Crazyyeti » Wed Feb 01, 2012 6:08 am

I have been using ME Pro for some years (was Ver 2.5 recently upgraded to 6.03). Block lists (on inbound SMTP) still use 192.168.* .* as the pattern. Why not support CIDR notation for example 192.168.0.0/16. This allows me to block 65,536 addresses in 1 statement. Using the 192.168.*.* method would take 9 statements. This is silly. If you want to support both methods for historical reasons, fine, but CIDR notation has been in effect for many years. Time to get with the modern internet.

In case you are wondering, I block EU, Asia, Africa, and South America IP ranges. I have nobody in those areas of the world that send legitmate messages to my mail server. Anything from there I want to block. No spam, nothing. Currently it take 300+ statements to perform this blocking. With CIDR notation (x.y.x.a/xx) it would take less than 50 statement to perform the same blocking.

Post Reply