After trying to upgrade our (very) old Tine 2.0 installation to the latest version of Tine 2.0, Tine 2.0 was not able to connect to our mailservers any more. After testing a few things, it became clear that the PHP IMAP module had problems with the SSL certificate we are using for our mailservers. Even though it is not a self-signed certificate, imap_open() failed to connect to the mailserver. After digging a bit in the Tine 2.0 sources, I found that peer verification can be disabled by setting the peerVerify flag to false. Since I could not find a UI setting in the Tine 2.0 setup for this option, the solution was simple: Look for the imap configuration in the tine20_config database table and add the peerVerify:false setting to the existing JSON object for the connection configuration.
Since more than one year we moved from eGroupWare to Tine 2.0. After using eGroupWare for more than 5 years it was time to look for an alternative. Integrating Tine 2.0 into our it infrastructure was no big deal, it was even possible to connect it to our central LDAP server. The LDAP sync of Tine 2.0 is designed in a way to copy all user and group information from the LDAP server into the local Tine 2.0 database. The sync process is triggered via a cronjob. Since we have a lot of LDAP groups for the various applications we use, I was looking for a way to filter groups that should be synced. I realized there was no way of ignoring certain groups so I changed my plan and added some custom code which would at least hide the groups.
To accomplish that open the file Tinebase/Group.php and locate the syncGroups() method and look for the line