typographical error in setting the "maildir_attr" and
"homedirectory_attr" attributes in my LDAP server (I had to add the
field being returned into these required Maildrop attributes into the
LDAP schema). While the database was happy with the lookup, apparently
the information returned didn't exactly match what Maildrop needed.
Once I corrected the typo, all is well.
(sigh) sorry for the noise.
Howdy:
I'm pretty new to using Maildrop (like, 3 weeks or so). I'm trying to
get Maildrop to authenticate against an LDAP database. Apparently it is
successful, as my LDAP database returns exactly one entry with a zero
error code (it's Netscape Directory Server Version 4.16). However,
Maildrop constantly returns a "signal 0x0B" (maildrop: signal 0x0B). I
understand that this is a segfault, and is returned because Maildrop
didn't get the "required results" from the LDAP query.
I'm wondering what the "required results" should be. I can't increase
the logging verbosity because that flag is disabled using the delivery
method (cat <filename> | maildrop -d <user>@<domain>). I've tried
paring down the maildropldap.config file to just a bare lookup (both
anon and binding via the Directory Administrator). Each time the LDAP
server returns no errors and exactly one entry.
I've been Googling around for answers with no useful results. I notice
that Maildrop-LDAP is using LDAP V2 while Courier-POP3 (authenticated
via LDAP) is using LDAP V3 and working like a charm.
Any assistance would be helpful.
: This Space Intentionally Left Blank :
2 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] maildropldap failure ...
