The strlcat/strlcpy problem remains. Right now these are the known issues:
1) If a previous version of opendkim installed a libstrl, we will detect its presence and assume we don't need to install a new one. Then RPM removes the old one when the old package is installed, and now the installed binaries won't run.
2) libdns from the unbound package also exports strlcat/strlcpy, which are in conflict with the ones we install and try to use. To add to this, some programs (e.g., opendkim-spam) actually don't need what's in libdns, so just linking against that is also the wrong thing. Similar issues might appear with libbsd or other-party libstrl installations.
We might want to revert to doing dkim_strlcat() and dkim_strlcpy() but put them in their own library like libopendkimutil. it would be a shame to pollute the filesystem with yet another strlcat/strlcpy, hiowever.