Lefteris Tsintjelis:
> I am struggling to find some info about how postfix collaborates with
> blacklistd but can't seem to find much. I assume this is only login
> based so far (works REALLY great BTW). Besides the false logins, the
> question I have is if it is possible to use blacklistd with postscreen
> also (I assume it has no interaction???) and if there are any plans to
> expand support up to that point.
I don't know blacklistd, but it is (in theory) possible that such
programs write to a $postscreen_access_list table in order to
block or whitelist a client.
For latency and integrity reasons this should be a table that
supports concurrent reads and writes without Postfix-managed locks.
The only table that I know can do this is LMDB (*SQL and LDAP lookups
are too slow, Berkeley DB requires Postfix-managed locks, and CDB
does not support update operations).
Wietse
