Tomas Kuliavas wrote:

Tomas Kuliavas wrote:



Ok.

starting from the begining.

have you tried removing ldapdefaultdelivery file? I got bunch of
messages,
some dublicate, some contain mostly quoted texts. Might have missed the
one where you said that you removed ldapdefaultdelivery file, restarted
qmail and it haven't fixed your problem.

have you tried creating qmail-ldap install with minimal required
configuration files?





Earlier I did not, but now I can say yes I tried... with following set
of control files.
---< snip >--
quark:/var/qmail/control# svstat /service/qmail
/service/qmail: up (pid 25559) 12 seconds
quark:/var/qmail/control# ls
ldapbasedn  ldapgid  ldappassword  ldapserver  ldapuid  locals  me
rcpthosts
quark:/var/qmail/control#
---< /snip >--
I removed all the control/ files and then went on adding one by one till
qmail restored.
Now qmail is running but still delivery is failing but due to different
reason.
Looks like some control/ldap* files are missing. These are the files I
have in
control/ directory. And this is the error in logs.
---< snip >--
quark:/home/sam/jail# ls /var/qmail/control/
ldapbasedn   ldapgid    ldapmessagestore  ldappassword  ldapuid  me
ldapcluster  ldaplogin  ldapobjectclass   ldapserver    locals
rcpthosts
quark:/home/sam/jail# tail -n 20 /var/log/qmail/current | tai64nlocal
2005-05-12 23:10:38.786005500 delivery 14: failure:
Illegal_value_in_LDAP_attribute._(#5.3.5)/
2005-05-12 23:10:38.786010500 status: local 0/10 remote 0/20
2005-05-12 23:10:38.825533500 bounce msg 5800497 qp 25645
2005-05-12 23:10:38.825605500 end msg 5800497
2005-05-12 23:10:38.838418500 new msg 5800362
2005-05-12 23:10:38.838437500 info msg 5800362: bytes 730 from <> qp
25645 uid 1011
2005-05-12 23:10:38.838484500 starting delivery 15: msg 5800362 to local
[EMAIL PROTECTED]
2005-05-12 23:10:38.838546500 status: local 1/10 remote 0/20
2005-05-12 23:10:39.889809500 delivery 15: failure:
Illegal_value_in_LDAP_attribute._(#5.3.5)/
2005-05-12 23:10:39.889814500 status: local 0/10 remote 0/20
2005-05-12 23:10:39.918359500 bounce msg 5800362 qp 25647
2005-05-12 23:10:39.918431500 end msg 5800362
2005-05-12 23:10:39.931218500 new msg 5800363
2005-05-12 23:10:39.931238500 info msg 5800363: bytes 1175 from <[EMAIL 
PROTECTED]>
qp 25647 uid 1011
2005-05-12 23:10:39.931276500 starting delivery 16: msg 5800363 to local
[EMAIL PROTECTED]
2005-05-12 23:10:39.931345500 status: local 1/10 remote 0/20
2005-05-12 23:10:40.935186500 delivery 16: failure:
Illegal_value_in_LDAP_attribute._(#5.3.5)/
2005-05-12 23:10:40.935192500 status: local 0/10 remote 0/20
2005-05-12 23:10:40.935195500 triple bounce: discarding bounce/5800363
2005-05-12 23:10:40.935199500 end msg 5800363
quark:/home/sam/jail#




which tool was used to create qmail ldap user accounts?

show LDAP entry that causes illegal attribute error



I just have one user/account entry in the ldap directory. Thats admin.
Rest of the ldap entries are ou and basedn

---< snip >--

quark:/home/sam/backups/qmail-control# /var/qmail/bin/qmail-ldaplookup
-u admin
Searching ldap for: (&(objectClass=qmailUser)(uid=admin))


...

show ldif output. not qmail-ldaplookup

ldif output for user admin

---< snip >--

quark:/home/sam/ldap_data# cat admin_user.ldif
# Example.tld Admin, qmail_users, example, tld
dn: cn=beekeycorp.in Sameer,ou=qmail_users,dc=beekeycorp,dc=in
cn: beekeycorp.in Sameer
ou: qmail_users
sn: Sameer
objectClass: top
objectClass: person
objectClass: inetOrgPerson
objectClass: qmailUser
mail: [EMAIL PROTECTED]
mailHost: secure.beekeycorp.in
mailQuotaSize: 10000000
mailQuotaCount: 1000
uid: admin
accountStatus: active
userPassword: {SSHA}0uOJqLThPzooPpIa+G4Kts+gJcGd8HEL
mailMessageStore: admin/Maildir/
mailAlternateAddress: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
deliveryMode: noprogram

---< /snip >--

--

Sameer N. I.
/****************************************************************/
/ The early bird gets the coffee left over from the night before./
/****************************************************************/



Reply via email to