On Wed, Aug 8, 2012 at 12:43 PM, Antoine Jacoutot <ajacou...@bsdfrog.org> wrote: > On Wed, Aug 08, 2012 at 12:35:36PM +0200, David Coppa wrote: >> On Wed, Aug 8, 2012 at 12:04 PM, viq <v...@viq.im> wrote: >> > On 2012/8/8 11:30, David Coppa wrote: >> >> On Wed, Aug 8, 2012 at 11:17 AM, viq <v...@viq.im> wrote: >> >>> On 2012/8/5 24:31, Stuart Henderson wrote: >> >>>> as noted by viq, php crashes in an ssl-related function if curl.so >> >>>> (from the php-curl package) and mapi.so (from zarafa-webaccess) >> >>>> are both enabled in php. >> >>> >> >>> This still happens after recent zarafa/mapi/libvmime update. >> >>> (FWIW php-curl brought in by www/tt-rss) >> >>> -- >> >>> viq >> >> >> >> Does reversing the loading order (loading mapi module before curl module) >> >> help? >> >> >> > >> > Yes, it does help, httpd starts with 'cat curl.ini >> mapi.ini' and only >> > mapi.ini being present in /etc/php-5.3/ >> >> So, it could be that zarafa php extension suffers from the same bug >> described here[1] ? >> >> [1] https://bugs.php.net/bug.php?id=40926 > > For the time being I can always rename mapi.ini to aaamapi.ini in the zarafa > pkg until a proper fix is found.
Yes, this should work. But imho a ticket should be opened on the Zarafa bugtracking system, so they can fix their code to properly unregister OpenSSL callbacks... > Antoine Ciao, David
