6 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: Maildrop 20040424
FromSent OnAttachments
Sam VarshavchikApr 24, 2004 3:57 pm 
Tony EarnshawApr 24, 2004 6:35 pm 
Sam VarshavchikApr 24, 2004 7:18 pm 
Tony EarnshawApr 25, 2004 4:10 am 
Tony EarnshawApr 25, 2004 11:08 am 
Sam VarshavchikApr 25, 2004 1:23 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] Re: Maildrop 20040424Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Apr 25, 2004 1:23:45 pm
List:net.sourceforge.lists.courier-maildrop

Tony Earnshaw writes:

søn, 25.04.2004 kl. 04.18 skrev Sam Varshavchik:

The --enable-restrict-trusted option has nothing to do with LDAP.

1.6.3: For some reason (I haven't looked at the code) it produces a maildrop binary with no LDAP libraries linked in. This cost me a bunch of mail before I realized what was going on. I compiled again and again with and without this modifier and could always reproduce and confirm. Believe me, I thought it was my fault.

When you look at the code you will find that all that option does is set a preprocessor directive.

AC_MSG_CHECKING(for RESTRICT_TRUSTED) AC_ARG_ENABLE(restrict-trusted, [ --enable-restrict-trusted=1 restrict -d for trusted users only], [RESTRICT_TRUSTED=$enableval], [RESTRICT_TRUSTED=1]) case "$RESTRICT_TRUSTED" in 1*|y*|Y*) RESTRICT_TRUSTED=1 ;; *) RESTRICT_TRUSTED=0 ;; esac AC_MSG_RESULT($RESTRICT_TRUSTED) AC_SUBST(RESTRICT_TRUSTED)

That's pretty much it.