On out mailserver, we have USE=ldap, because we would one day like to use this. today I found that maildrop took several minutes to deliver mails. I finally tracked this down to the supplied (and never touched) default config /etc/maildrop/maildropldap.cf. This states a host ldap.server.yourdomain.com that really seems to exist. So every maildrop dried to establish a TCP connection and had to wait for a timeout. Reproducible: Always Steps to Reproduce: 1. USE=ldap in make.conf 2. emerge maildrop Actual Results: Every maildrop process tries to contact ldap.server.yourdomain.com Expected Results: Don't use ldap at all unless someone actually configures some sensible host The easiest would be to just comment the hostname entry in the default maildropldap.cf, but I'm not sure if perhaps some of the default_ settings would still be used. In this case, all those entries should be comments as well, I think.
I don't think if you have ldap use flag activated the expected behavior is "not to use ldap unless someone actually configures some sensible host". If you are not actually using ldap, just deactivate ldap use flag. Cheers, Ferdy
I reopen this bug because now I've got a scenario where this behaviour is even more unexpected. I've got a system completely without ldap. One user asks for the gnupg ldap module to access ldap://keyserver.pgp.com, so I build gpg with the ldap USE flag. As a dependency, openldap is built, to provide ldap client libs. The openldap package provides the ldap use flag, so even if ldap is not included in make.conf, suddenly maildrop does not work any more. So I have a situation where just adding some feature to gnupg suddenly renders maildrop slow when it is updated next, which might be months in between. I am still of the opinion, that a USE flag should describe some feature made available, not force the sysadmins to actually configure and use this feature.
You can always disable ldap USE flag for maildrop in /etc/portage/package.use. Or, you can investigate a bit and propose a change to default config that would fix this problem of yours. The bottom line is, don't enable USE flags you don't actually need. Not even "if you would one day like to use it".
In fact with newer versions of maildrop this isn't a problem anymore since it uses courier-authlib. Cheers, Ferdy
