6 messages in net.sourceforge.lists.courier-maildropRe: [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:Re: [maildropl] Re: Maildrop 20040424Actions...
From:Tony Earnshaw (ton@billy.demon.nl)
Date:Apr 25, 2004 4:10:42 am
List:net.sourceforge.lists.courier-maildrop

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

When will we get ldapi and or ldap TLS? When will we get decent logging? When will maildrop respect --enable-restrict-trusted=0 with LDAP compiles? (At the moment, setting this excludes all LDAP libs and leads to mail disappearing into a bottomless pit without trace).

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.

Also, try the -V 9 option to maildrop to get more logging then you could possibly care for.

I'll read up on that, thanks.

--Tonni

--

We make out of the quarrel with others rhetoric but out of the quarrel with ourselves, poetry.

mail: billy - at - billy.demon.nl http://www.billy.demon.nl