On Dec 15, 2014, at 17.47, Wietse Venema wrote: > btb: >> hi- >> >> i currently have: >> >> postscreen_access_list = cidr:$table_directory/postscreen_access_list.cidr >> >> with various sized netblocks rejected therein. this all works >> fine. i have more than one mx, and would like to store this data >> in a centralized location and query over the network instead of >> duplicating the files on each mx. i don't believe postfix can >> currently do this, aside from a traditional access(5) lookup which >> is limited to octet boundaries. am i wrong? if not, could this >> be considered as a possible feature? could this potentially be >> done with pipemap? > > cidr is a sequential map that tries each pattern in a fixed order > until a match is found. How is "try each pattern in order" supposed > to work when patterns are stored in a hash, btree, lmdb, ldap, > *sql*, or memcache table?
well, since i was thinking in terms of network lookups, my focus was sql/ldap. i'm not sure if/how this could work with the others you mention, aside from just reading the contents as a list, but i guess that wouldn't serve much purpose, since the plain text file already does that for local storage. for sql though, i envisioned a query that would return the same data that would be read from the text file, a list of patterns and a matching result for each, for postfix to iterate through. i know this would be a different type of query than is currently used for sql maps. i'll have to think more about this. -ben
