Emails - Again

[roblaus]

I just transferred an installation from one server to another (52e). All standard out of the box setting (LAMP).
Now all of a sudden group emails don't get picked up anymore with the well known message:
[FATAL] SCHEDULERS: could not get an IMAP connection resource for ID [ 9f2a98d1-cc14-53c0-3f5a-4a2767f50e91 ]. Skipping mailbox

To the outside world this shows as a scheduler job forever "in progress".

The imap account in question is functional
When setting it up I could select folders and (just in case) also the "test settings" worked without problems
Imap is installed and working (I can get emails from other imap accounts - even from this one if it is set up as personal)
The scheduler (cron job) is working - other scheduled jobs are running. The above error message wouldn't show if the job wasn't triggered correctly.
I did repair inbound emails as well as the scheduler
I did rebuild relationships.
I did set up the account from scratch.
And I did set up a second account just to make sure that it is NOT the account: same result.

I am kind of pissed off and so is the customer. I have found at least 20 threads about the same topic going back as far as 2005. No solution...

And again the question that I asked a couple of times already: Isn't it better to fix the email once and forever rather than playing with themes and connectors? People tell me that the crappy email functionality is the number one reason NOT to go for Sugar (with reason no2 - calendar not even coming close.)

[crmsiva]

yes. roblaus is right. Emails and Calendar sometimes make us to put our heads down before customer.

[roblaus]

chorlick writes sometime in March:
----
I hope this helps someone the solution for my install turned out to be that the imap module for php wasnt loaded(exactly as the debug messages said go figure). If you go to your console and type 'php -m' and you do not see the imap module listed this solution will work for you. It turns out that php cli and php apache module use different php.ini files and thus have different module loading parameters. Open your php.ini file for php cli and add 'extension=imap.so'. This should take care of your issue.
-----
Many thanks to him

[batoski]

I have kind of the same pb (emails get received by sugar and are stored in the database, but do not display in the email window) although I did make sure this extension was already loaded through /etc/php.d/imap.ini (which contains a line : "extension=imap.so"), and choose the right folder, etc.

[crwebcraft]

chorlick writes sometime in March:
----
I hope this helps someone the solution for my install turned out to be that the imap module for php wasnt loaded(exactly as the debug messages said go figure). If you go to your console and type 'php -m' and you do not see the imap module listed this solution will work for you. It turns out that php cli and php apache module use different php.ini files and thus have different module loading parameters. Open your php.ini file for php cli and add 'extension=imap.so'. This should take care of your issue.
-----
Many thanks to him

But what if it is listed with php -m? I am still unable to configure inbound mail.

Inbound Email Disabled
Warnings: Inbound Email cannot function without the IMAP c-client libraries enabled/compiled with the PHP module. Please contact your administrator to resolve this issue. <--That would be me, unfortunately, and why I am here.

Any suggestions?
Apache2
PHP Version 5.2.6
MySQL 5.0.75

Thanks

[roblaus]

install the imap libraries and enable them in php.ini. If I am not mistaken the package on Debian/Ubuntu is php5-imap and the file to be enabled in php.ini is imap.so

[crwebcraft]

install the imap libraries and enable them in php.ini. If I am not mistaken the package on Debian/Ubuntu is php5-imap and the file to be enabled in php.ini is imap.so

Okidoki!, I also have noticed a lot of users wanting to know how to enable the imap libraries as well, so here is what I discovered earlier while waiting for a reply to my post, and as luck would have it the reply confirmed my discovery was correct. And thanks to Roblaus for unknowingly confirming my results.

Here is yet another possible solution for those who are getting the imap warnings.

Inbound Email Disabled
Warnings: Inbound Email cannot function without the IMAP c-client libraries enabled/compiled with the PHP module. Please contact your administrator to resolve this issue. <--That would be me, unfortunately, and why I am here.

If you are running:
Ubuntu 9.04 (Probably will work on most recent debian linux kernel releases)
Apache2
PHP Version 5.2.6
MySQL 5.0.75

This may work for you, I did a little experimenting and this fixed it for me.

Before you start, make sure you do have the imap libraries installed and then this is how to enable them in the php.ini .

1) Open a terminal window
2) Type php -m | grep imap
3) If imap shows, then copy your php.ini [might be /etc/php5/apache2/php.ini ] to your home directory for editing.

Warning Warning: Make a copy of your php.ini and copy to your home directory. Never Ever edit the ini file directly. Mess it up, you can really mess up!

4) Now change to your home directory and copy the php.ini to php.ini.original. Do not rename, copy, this is your backup copy of the original.
5) Now edit with your favourite text editor, you will have to sudo the edit since it will most likely belong to root or the web server.
6) Scroll down until you get to Dynamic Extensions and just below the description you will add the following

extension=imap.so

7) Save, then quit the editor.
8) Now copy your new php.ini back to where you got it and ok the overwrite.

You will probably have to do something like this: sudo cp -i ~/php.ini /etc/php5/apache2/php.ini

9) Now restart apache2 gracefully, something like this:sudo /etc/init.d/apache2 restart
10) Now login to SugarCRM as the admin and click on Monitor New Mail Account and if all is right as rain you should now see Inbound Email Setup:
11) If you running as root and not a user, get up, get a big hammer, strike self directly in the middle of forehead repeatedly. Never Ever run as root, always as user! That is what sudo is for, those times when you need root permissions to do an action like restarting the webserver, and then the permission expires shortly after the action completes. Can't accidently wipeout critical files that way.

Hope this helps.
Cheers!