I am not sure this is a bug or support request.

In system status, admin/reports/status, I get the error message:
Mailhandler requires that PHP's IMAP extension is enabled in order to function properly.

I am running Ubuntu 10.04 but have pinned php5 to 5.2.10, php5-imap, and php5-mcrypt to 5.2.6 per https://launchpad.net/~txwikinger/+archive/php5.2

When I take a look at the /usr/lib/php5 directory I see:

20060613+lfs:
total 732
drwxr-xr-x 2 root root 4096 2011-07-16 08:04 .
drwxr-xr-x 6 root root 4096 2011-07-31 08:04 ..
-rw-r--r-- 1 root root 56884 2010-05-20 22:57 curl.so
-rw-r--r-- 1 root root 105260 2010-05-20 22:57 gd.so
lrwxrwxrwx 1 root root 23 2011-07-16 08:04 imap.so -> ../20090626+lfs/imap.so
lrwxrwxrwx 1 root root 25 2011-07-16 08:04 mcrypt.so -> ../20090626+lfs/mcrypt.so
-rw-r--r-- 1 root root 9832 2010-05-20 22:57 mhash.so
-rw-r--r-- 1 root root 101696 2010-05-20 22:57 mysqli.so
-rw-r--r-- 1 root root 44664 2010-05-20 22:57 mysql.so
-rw-r--r-- 1 root root 124946 2011-07-16 07:28 pdo_mysql.so
-rw-r--r-- 1 root root 239066 2011-07-16 07:27 pdo.so
-rw-r--r-- 1 root root 47181 2011-07-16 07:30 uploadprogress.so

20090626+lfs:
total 140
drwxr-xr-x 2 root root 4096 2011-07-31 08:25 .
drwxr-xr-x 6 root root 4096 2011-07-31 08:04 ..
-rw-r--r-- 1 root root 97576 2010-08-28 18:04 imap.so
-rw-r--r-- 1 root root 35192 2010-08-28 18:17 mcrypt.so

If I add imap.ini to /etc/php5/apache2/conf.d and run php -v I get an error that the api version for php5-imap is not the same as php5.2.10 installed. As a result I removed it. In either case the status report error persists.

Has anyone else ran up against this issue? How have you solved it?

Comments

danepowell’s picture

Not sure what to tell you, sorry... did you ever figure out a solution? Is this still an issue for you?

socialnicheguru’s picture

yes. it is.

has anyone installed ubuntu 10.04 but pinned php to 5.2?

open social’s picture

drupal.txwikinger.me.uk/content/php5-mcrypt-and-php5-imap-packages-are-now-available-php52

here is a fix for imap

socialnicheguru’s picture

thanks. I found that link a long time ago. I get the same issue as the first commenter.

http://drupal.txwikinger.me.uk/content/php5-mcrypt-and-php5-imap-package...

I am on bunt 10.04 and pinned php 5.2.

It will not load crypt or imap because of the versions of php.

Do you have any idea how to get around that?

open social’s picture

well I did the short term fix at a comment in the middle. It works fine here. So

For more see: http://drupal.txwikinger.me.uk/content/php5-mcrypt-and-php5-imap-package...

socialnicheguru’s picture

but I am on a 32 bit machine :(

Edit.

actually I loaded Ubuntu. how do I check if I loaded 32 or 64 bit?

open social’s picture

uname -m

I fixed the href to the packages

socialnicheguru’s picture

I am on i686.

are the packages above compatible?

open social’s picture

I think they are compatible.

socialnicheguru’s picture

Nope:

dpkg -i libc-client2007b_2007b~dfsg-1.1build1_amd64.deb
dpkg: error processing libc-client2007b_2007b~dfsg-1.1build1_amd64.deb (--install):
package architecture (amd64) does not match system (i386)
Errors were encountered while processing:
libc-client2007b_2007b~dfsg-1.1build1_amd64.deb

socialnicheguru’s picture

looks like i'll be upgrading to 10.04 64bit.

open social’s picture

danepowell’s picture

Title: Ubuntu 10.04 pinned to php5.2.10: Mailhandler requires that PHP's IMAP extension is enabled in order to function properly. » Conflict between Ubuntu 10.04, PHP 5.2.10, and PHP IMAP extension

@SocialNicheGuru - can you try the 32-bit versions linked to in #12? Also, one workaround (yet to be implemented) could be to avoid the PHP IMAP extension altogether: #275926: Message retrieval library plugins (in order to avoid PHP IMAP dependency)

meecect’s picture

I ran like this for some time, but finally 5.3 packages made it into the ubuntu repo so I just upgraded to php5.3, and removed the pinning to 5.2. Can you upgrade to 5.3?

danepowell’s picture

Status: Active » Fixed

No reply from the OP in some time, and a number of possible solutions have been proposed, so I'm going to consider this fixed. Please re-open if you still need help.

Automatically closed -- issue fixed for 2 weeks with no activity.