Inbound emails

[terence]

I am having difficulty setting up my email service on sugar. I have upgraded to verison 4.2.


I get this error message.

Inbound email disable:

Inbound Email cannot function without the IMAP c-client libraries enabled/compiled with the PHP module. Please contact your administrator to resolve this issue.

What can I do to fix the built-in sugar email system.

[pierreavista]

Hi there

We also upgraded to 4.2, Inbound email was working fine for us before in 4.0.1e and we are also incapable of gettting this to work with 4.2

I am a Pro customer and exchanged many emails with Suggar Support on this since Monday this week. I am not totally certain, it has not been said to me very clearly, but it looks like there are serious bugs in 4.2 with numbers. And this may have an impact on inbound email andthe cron.php file used for this process.

We personally have given up trying to get this to work. Either we get a fix today from Sugar or we will downgrade to 4.1.
The inbound email is not the primary reason I am considering downgrading, currently the system is practically totally down. It is running, but cannot not be used to enter or modify ANYTHING. All we can do is look at stuff already entered.

I am not pleased at all with the mounting delays at fixing this.

Let me know if ever you find a solution....

[bsdnazz]

I am having difficulty setting up my email service on sugar. I have upgraded to verison 4.2.


I get this error message.

Inbound email disable:

Inbound Email cannot function without the IMAP c-client libraries enabled/compiled with the PHP module. Please contact your administrator to resolve this issue.

What can I do to fix the built-in sugar email system.

I've installed a fresh 4.2 release and can't get email to work either. I have a fully operational IMAP server (University of Washington) with OpenSSL but can't get SugarCRM 4.2 to connect to it.

For example, I can try to monitor inbound email and enter the hostname for the imap server and the protocol (IMAP) select SSL (so port 993) and every time I click on 'Test Settings' I get a pop-up error box saying

Can't connect to <server FQDN>, 993: Permission denied.

Is there a way to turn on low level logging to see what might be going wrong?

[bsdnazz]

Well, my particular problem with SugarCRM and Fedora Core 5 Linux has been solved.

FC5 installs by default with quite a lot of security (a good thing) including a setting which prevents web applications
(eg php) from making network connections. This makes it hard to communicate with IMAP servers...

The following command

/usr/sbin/setsebool -P httpd_can_network_connect=1

fixes the problem.

This setting can also be changed from the SELinux sub pannel in the system admin menu.

[tonywood100]

Just as a little feedback I have installed a clean 4.2 install on RH ES and the IMAP email functionality on a per user basis is working fine without problems.

I hope this helps.

Tony

[sugarchris]

I am having difficulty setting up my email service on sugar. I have upgraded to verison 4.2.


I get this error message.

Inbound email disable:

Inbound Email cannot function without the IMAP c-client libraries enabled/compiled with the PHP module. Please contact your administrator to resolve this issue.

What can I do to fix the built-in sugar email system.

Since no one in this thread actually answered your question:

You or your server-guy has to enable (Windows) or recompile (Linux) PHP with the IMAP c-client library. This is difficult and technical for someone who has not done this before.

Which platform are you on? Oh, and take a quick look at the threads in my signature. The first post of each FAQ is a distilation of the wisdom of many users who have had the same problems as many of you. It may bear reading - and if you have a solution that hasn't been added, by all means, please do so.

[electric]

We have a client using sugarCRM 4.2.0d, and is having the exact same problem:

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.

Any help to resolve this problem would be appreciated.

Here is a link to the phpinfo.php file:

http://luc.host-vault.com/phpinfo.php

Any suggestions?

[Markku]

I'm basically quoting sugarchris here, but your client has to contact their hosting provider and ask this hosting provider to recompile PHP with the IMAP c-client library.

[peteunderwood]

I don't know if theis helps, but I was getting this in 4.2d when I was monkeying around with the upload_tmp_dir (in trying to get rid of the attachment warning).

I am running on Windows, however. I pointed the ipload_tmp_dir back to /tmp and it seemed to work.

Good luck.

[rogkarlsson]

I'm basically quoting sugarchris here, but your client has to contact their hosting provider and ask this hosting provider to recompile PHP with the IMAP c-client library.

Hi,

How do I recompile PHP with the IMAP c-client libary?

Thanks.