Page 1 of 1

Test mail configuration?

PostPosted:Wed Mar 30, 2011 8:26 am
by Catscratch
Hi,

I configured the mail configuration like it is descriped in the documentation:
http://wiki.openkm.com/index.php/JBoss_ ... figuration

But I don't receive notifications. Also there is no error in the log. So is there a way so test the notification mechanism?

Thank you.

Re: Test mail configuration?

PostPosted:Wed Mar 30, 2011 6:32 pm
by pavila
Subscribe to a document, the lock and unlock it. Every time a mail notification should be sent. Configure JBoss mail is debug mode which will spit a lot of info in the log (or the console if you started JBoss from the command line).

Re: Test mail configuration?

PostPosted:Thu Mar 31, 2011 7:47 am
by Catscratch
See next post.

Re: Test mail configuration?

PostPosted:Fri Apr 01, 2011 11:11 am
by Catscratch
I debugged it.

The error is in line 200 of LdapPrincipalAdapter.java:
Code: Select all
NamingEnumeration<SearchResult> results = ctx.search(searchBase, searchFilter, searchCtls);
searchBase = cn=user1,ou=MMTOpenUsers,dc=mmtopen,dc=de
searchFilter = (objectClass=person)

searchCtls
- attributesToReturn = null
- countLimit = 0
- derefLink = false
- returnObj = false
- searchScope = 2
- timeLimit = 0

Do you have a hint for me please?
Thank you.

Edit:
I changed the openKM.cfg to:
Code: Select all
principal.ldap.mail.search.base=ou=MMTOpenUsers,dc=mmtopen,dc=de
principal.ldap.mail.search.filter=(&(objectClass=person)(sAMAccountName={0}))
Now no exceptions is thrown, but
Code: Select all
while (results.hasMore())
is false. So the enum is empty.

If I hardcode the user with:
Code: Select all
principal.ldap.mail.search.filter=(&(objectClass=person)(sAMAccountName=USERNAME))
Mailnotification works. How do I have to set the parameter right?

Re: Test mail configuration?

PostPosted:Mon Apr 04, 2011 6:53 am
by Catscratch
Someone has a working configuration?

Re: Test mail configuration?

PostPosted:Tue Apr 05, 2011 9:18 pm
by jllort
Remember changes on OpenKM.cfg need restarting jboss this could be the problem. Take a look on administrator if parameter is propertly. And make some print in source code, because it's a misterious problem.