We appear to be running into a problem with the size of our private blacklists. We currently have a main group named in the config doc, and in that group there are currently three sub-groups. Each has around 1500 entries (with another 1500 I haven’t had a chance to add yet.
Unfortunately we are now seeing the following error on all servers:
SMTP Server: Error expanding configuration field SMTPPrivBLHosts. Restrictions will not work as expected: Adding entry will cause text list to exceed 64K. Entry not added.
Does this mean a private Blacklist can only be 64k? I find it incredible that the 64k limit would apply to this, considering that ($Users) is in memory at all times and must be way bigger than that.
Sorry, I don’t monitor this forum as much as I used to. No time.
Never seen that problem before. The use of groups was supposed to be a way of getting round the 64k limitation you encounter when populating the server config local blacklist field directly with blacklisted networks.
We have two groups named in the server config document, with each group containing a large number of entries (unable to count them now) and it works fine.
I wonder if using cascading groups is part of the problem.
Why not just name the sub groups directly in the server config document and ditch the intermediate group?
Thanks for that. Unfortunately it makes no difference, since the groups that I have (three) are packed to the gunwales, certainly over 64k’s worth.
Sadly I don’t know enough about DNS to set up a zone on our own DNS servers (or rather, get our network manager to do it), so I don’t think this is solvable, unless Lotus radically change the way the private blacklists are held.
Also, we have clients all over the world, including the usual hostpots like the far east, so using a blackhole list probably isn’t going to be acceptable to the business.
I see no 64k limitation here. My blacklists are also packed to the gunwales but are referenced directly by the server config document and not by another group which is then listed in the server config.
Works fine and we probably exceed 64k’s worth of blacklists by a factor of at least 5.
No, I think I understood you - I added the names of the groups that contain the actual IP addresses to the config doc itself, removing the parent group, restarted the listener and received the same error.
We have 4708 entries, amounting to 78K +. The error message specifically mentions the 64K limit being exceeded as well, Or did you mean add the groups to the Deny Connection field?
BTW, I initially split the groups up since I ran into the 32K limit for a text field on the first group I set up.