Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 113791

Summary: vpopmail 5.4.13 ldap support
Product: Gentoo Linux Reporter: Markus Ullmann (RETIRED) <jokey>
Component: New packagesAssignee: Net-Mail Packages <net-mail+disabled>
Status: RESOLVED LATER    
Severity: enhancement CC: fernando.ribeiro, hoffbrinkle, sjulean
Priority: High    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: ebuild diff against 5.4.13
files/vpopmail-5.4.13-ldap.patch
files/vpopmail.ldap

Description Markus Ullmann (RETIRED) gentoo-dev 2005-11-28 07:01:14 UTC
Patch to support vpopmail-ldap module and set connection parameter via
/var/vpopmail/etc/vpopmail.ldap instead of hardcoding it in vldap.h

Reproducible: Always
Steps to Reproduce:
Comment 1 Markus Ullmann (RETIRED) gentoo-dev 2005-11-28 07:01:53 UTC
Created attachment 73730 [details]
ebuild diff against 5.4.13
Comment 2 Markus Ullmann (RETIRED) gentoo-dev 2005-11-28 07:02:17 UTC
Created attachment 73731 [details, diff]
files/vpopmail-5.4.13-ldap.patch
Comment 3 Markus Ullmann (RETIRED) gentoo-dev 2005-11-28 07:02:45 UTC
Created attachment 73732 [details]
files/vpopmail.ldap
Comment 4 Fernando Ribeiro 2006-03-21 20:41:36 UTC
Somebody have tested this patchs?
Comment 5 Silviu Julean 2006-09-07 06:01:59 UTC
I have tested this patchset. Had to massage the ebuild patch a little bit to apply against the current 5.4.13 ebuild, but I managed to get it to compile cleanly.

However, the resulting vpopmail could not add a domain. It created the domain on-disk, and it added it to /var/qmail/control/locals, but when trying to add it to LDAP, vadddomain failed with the following error:

vadddomain: error.c:188: ldap_perror: Assertion `ld != ((void *)0)' failed.

A strace revealed that it wasn't trying to connect to LDAP, and moreover, that it wasn't even trying to read /var/vpopmail/etc/vpopmail.ldap.
Comment 6 Markus Ullmann (RETIRED) gentoo-dev 2006-10-18 17:06:19 UTC
No time left to fix this currently :( Will re-open once I can track that down further