Scott Taylor writes:
I've received enough requests to make the maildrop (when built as part of the full mta) talk to courier-authlib. It's easy enough for me to comment out the check in its autobloat script which would then let it build that way... but is there a good reason this should not be done? In
Why do you want to do that in first place?
the older versions, passing --enablemaildropldap and such seemed to make people happy. Would it be bad to forcibly allow maildrop to get the authlib features, or would steps need to be taken to make sure courier called on the stripped maildrop, and building a second executable that the rest of the system can use that does have the authlib support?
You should get the standalone maildrop build, if you want something like that, for some reason, and install it in a separate location.
pgpnebQArlrbo.pgp
Description: PGP signature
