1 Topic by xycmu

  • xycmu
  • Member
  • Offline
  • Registered: 2013-12-18
  • Posts: 6

Topic: Blacklist / Whitelist large subnets

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 2.1.1
- Linux/BSD distribution name and version: CentOS 6.4
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? Yes
- Related log if you're reporting an issue:
====

I'm attempting to add a system-wide blacklist for an entire /18 subnet generating a lot of spam. I could add 172.103.%.% and block the entire third and fourth octet, but would prefer to block only the infringing 172.103.64.0/18.

Is there a way to accomplish this using wildcards without blocking an entire Class B of IPs and without adding 64 different /24 listings:
172.103.64.%
172.103.65.%
172.103.66.%
...
172.103.127.%

Adding 172.103.64.0/18 doesn't seem to work.


NetRange:       172.103.64.0 - 172.103.127.255
CIDR:           172.103.64.0/18

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: Blacklist / Whitelist large subnets

The white/blacklist implementation in iRedAPD doesn't support CIDR format network, you can add it in Cluebringer.

I will try to improve this in future release of iRedAPD.