qmaiUID is the system id the process will execute.  something like 1001

you can probably configure a default on ~control



Leonard Tulipan wrote:

Hi!

I have an old qmail-ldap install running here in the company. For another location I wanted a similiar setup for which I'm using:

openldap-2.2.23 and
qmail-ldap-1.03-20050401a.patch

Now, apparently a few things changed from our setup (openldap-2.0 now also 2.2.23 and and old qmail-ldap)

What I'm basically talking about ist this error

# /var/qmail.ldap/bin/qmail-ldaplookup -u dieter
Searching ldap for: (&(objectClass=qmailuser)(uid=dieter))
under dn: dc=intra,dc=xxxxxxxxxxxxxxx
Found 1 entry:

dn: uid=dieter,ou=Users,dc=xxxxxxxxxxxxxxx
-------------------------------------------------------
objectClass: top
objectClass: inetOrgPerson
objectClass: posixAccount
objectClass: shadowAccount
objectClass: sambaSamAccount
objectClass: qmailUser
mail: [EMAIL PROTECTED]
uid: dieter
accountStatus: undefined -> active
mailHost: undefined
homeDirectory: /home/dieter
aliasEmpty: /home/dieter/Maildir
qmailDotMode: ldaponly
qmail-ldaplookup: fatal: qldap_get_uid: needed value is missing

which results in  (qmail log file)
@40000000429e06820a8c7e2c info msg 824161: bytes 2261 from <[EMAIL PROTECTED]> qp 25829 uid 503 @40000000429e06820ec74594 starting delivery 8: msg 824161 to local [EMAIL PROTECTED]
@40000000429e06820ec764d4 status: local 1/10 remote 0/20
@40000000429e06823578a304 delivery 8: failure: LDAP_attribute_is_not_given_but_mandatory._(#5.3.5)/
@40000000429e068236156bbc status: local 0/10 remote 0/20
@40000000429e068236925834 bounce msg 824161 qp 25831
@40000000429e06823692738c end msg 824161

when trying to the admin-account at first, I got this interesting thing

@40000000429e04fb14816d84 info msg 819244: bytes 2259 from <[EMAIL PROTECTED]> qp 25631 uid 503 @40000000429e04fb14fb6814 starting delivery 1: msg 819244 to local [EMAIL PROTECTED]
@40000000429e04fb14fb836c status: local 1/10 remote 0/20
@40000000429e04fb14fe522c delivery 1: deferral: Sorry,_message_has_wrong_owner._(#4.3.5)/

All users are the same in LDAP and where normal /etc/passwd users a week ago.

Any ideas or pointers how I can circumvent making those attribute-additions to the users (qmailUID and qmailGID)? I'd really rather hat qmail-ldap use the normal uid of the user.

Cheers
Leonard


Reply via email to