Here are some frequently asked questions.
Visit the Smartphone support page
Problem OBM UI access URL is obm.example.org . Horde access URL is intranet.example.org . But this URL is not resolved then access to webmail fails.
OBM-sync log levels are handled by Log4J. The configuration file on the server is /usr/share/tomcat/lib/log4j.properties. Edit this file to add/decrease log verbosity. Locate the line “log4j.logger.fr=DEBUG, R”. The log4j.logger.* part points to the class (and the ones under it on the package) onto which the log level will apply. You could also change the “DEBUG” level to any value described in here. You can add as many line as this one to set more precise log settings.
One could also log every request and corresponding response sent to the obm-sync server using Java Filters. To activate these, on the obm-sync server, edit /usr/share/tomcat/conf/web.xml and add/uncomment these lines :
<filter> <filter-name>LogFilter</filter-name> <filter-class> fr.aliacom.obm.common.DumpFilter </filter-class> </filter>
<filter-mapping> <filter-name>LogFilter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
You may also want to edit the “url-pattern” part to prevent from logging all requests/responses. Logs are displayed in /var/log/obm-tomcat/obm-java.log using a “Conversation UID” (”[CUID i]” in logs) thats identifies connections.
All system accounts are stored to database. To recover the list of system users, you can use mysql client.
mysql>select usersystem_login from UserSystem;
To change a password, you must edit the corresponding entry.
mysql>update UserSystem set usersystem_password="chosen_password" where usersystem_login="selected_account";
Then, if you use OBM >= 2.2 and < 2.3, you must recover the global domain_id.
mysql>select domain_id from Domain where domain_name="global.virt";
Now, you need to update your ldap directory using the update.pl script. The command-line is not the same according to your OBM release. If OBM ⇐ 2.1 you must use the domain_id 0:
#/usr/share/obm/www/auto/update.pl --domain O --global
If OBM >= 2.2 and < 2.3, you need to use the domain_id you have recovered in the previous step:
#/usr/share/obm/www/auto/update.pl --domain-id X --global
If OBM >= 2.3 you can use the –domain-global argument :
At last, you must restart saslauthd to purge passwords cache :
You create an event and when you want to add an user, any users appear. It causes by a SQL table which is empty (_userpattern).
To fill it, you must run the update-2.3.7-2.3.8.post.php PHP script like this :