SCHEDULERS: could not get an IMAP connection resource for ID

[commshop]

I've encountered a long standing bug that has no fix identified in this forum.

This IMAP problem is related to the CRON.php not downloading emails for 4.5.1*

All threads related to this state to delete the email account and reset the password but this does not fix SugarCRM scheduler hashing the passwords to the email host, the root of this failure. Repair InboundEmail Accounts does nothing to fix the problem.

Since the SugarCRM development community is ignoring this bug, has anyone else identified a definitive fix for this bug?

I have a fresh, virgin install of 4.5.1i and also tried 4.5.1.j. Both have the same problem. They do not retrieve emails using the cron.php. Instead the logs are full of "SCHEDULERS: could not get an IMAP connection resource for ID"

Any workaround would be appreciated.

[julian]

As you mentioned, this problem occurs on a fresh install of Sugar, right? Have you tried 5.0?

I'm moving this to the Help forum, where you might get a more targeted answer. I'll also take a look at this myself and get back to you soon!

[aerodesigns]

I'm having this problem as well, but what is really strange is that if i access the cron.php via my web browser then it all runs fine and downloads the IMAP mail, however if it is run by CRON then it displays the "FATAL SugarCRM - SCHEDULERS: could not get an IMAP connection resource for ID" all the times in the logs. Does anybody know a solution for this? I'm hesitant to upgrade to 5 as I have quite a few modules installed which I doubt would be compatible with the new release.

[aerodesigns]

Actually, just realised that the cron.php only runs correctly via the browser when I am logged in, and still reports an error (like CRON) when I'm logged out.

[commshop]

As you mentioned, this problem occurs on a fresh install of Sugar, right? Have you tried 5.0?

I'm moving this to the Help forum, where you might get a more targeted answer. I'll also take a look at this myself and get back to you soon!

Hi Julian, Sorry but no thanks.

Not to diminish my appreciation for your time Julian but, it appears that your reply is the standard operating procedure for calls for help with this matter, I.E. ignore the problem and sidestep to a new version. Thats one of the reasons this critical bug has been ignored for so long.

We seek someone who has resolved the standing issue with SugarCRM 4.5.1 hashing the passwords and how to resolve with a hack of any form.

It's sad that the SugarCRM development community has ignored this issue for so long. This is evident by the number of calls for help with this issue.

Thanks again Julian and we remain open for any suggestions.

[aerodesigns]

Hi Julian, Sorry but no thanks.

Not to diminish my appreciation for your time Julian but, it appears that your reply is the standard operating procedure for calls for help with this matter, I.E. ignore the problem and sidestep to a new version. Thats one of the reasons this critical bug has been ignored for so long.

We seek someone who has resolved the standing issue with SugarCRM 4.5.1 hashing the passwords and how to resolve with a hack of any form.

It's sad that the SugarCRM development community has ignored this issue for so long. This is evident by the number of calls for help with this issue.

Thanks again Julian and we remain open for any suggestions.

Speaking personally but probably for others as well, I don't even need a full Patch or Update to fix this, if someone could just say which files need editing and which lines to change then that would do fine.

[commshop]

Speaking personally but probably for others as well, I don't even need a full Patch or Update to fix this, if someone could just say which files need editing and which lines to change then that would do fine.

Ditto: As in most patch, hacks this is the thrust of resolving an issue.

What files are pertinent to this issue?

Some direction would eventually allow the solution to evolve.

It's just hard to find a SugarCRM team member to respond to this issue.
The long standing history of this issue is testimony.

Any help is appreciated.

[aerodesigns]

I've got an idea I'm just working on - further to my previous post, accessing cron.php via my web browser when i'm logged on runs the InboundEmail scheduler perfectly, however accessing it whatever way when logged out results in an error. So I'm just trying to use a SOAP script found in this forum to automatically log into Sugar and then call cron.php. I don't know whether this will work or not but we'll soon find out...

[commshop]

I've got an idea I'm just working on - further to my previous post, accessing cron.php via my web browser when i'm logged on runs the InboundEmail scheduler perfectly, however accessing it whatever way when logged out results in an error. So I'm just trying to use a SOAP script found in this forum to automatically log into Sugar and then call cron.php. I don't know whether this will work or not but we'll soon find out...

I'm surprised you can even do it with cron from the web browser.

I have run cron both from the web browser and from shell with the same results. No joy, no mail.

What I have found it that the Sugar logs do not fill with the "IMAP connection resource for ID" error upon running cron.php.
The log fills upon the scheduler running the job: function:ollMonitoredInboxes under the scheduler.

If I had your problem, I would consider it a cron command issue. If cron.php does work (retrieve your emails) when run from a browser:

You have the option of running it this way: Set a cron job to run the following command.

Example: wget http://www.mysite.com/SugarCRM/cron.php

The above would equate to running http or a browser to execute the cron.php. Good luck.

SugarCRM Developers, we patiently await your wisdom on the original post.

What files should we look at to begin our journey to a solution?

[aerodesigns]

I'm surprised you can even do it with cron from the web browser.

I have run cron both from the web browser and from shell with the same results. No joy, no mail.

What I have found it that the Sugar logs do not fill with the "IMAP connection resource for ID" error upon running cron.php.
The log fills upon the scheduler running the job: function:ollMonitoredInboxes under the scheduler.

If I had your problem, I would consider it a cron command issue. If cron.php does work (retrieve your emails) when run from a browser:

You have the option of running it this way: Set a cron job to run the following command.

Example: wget http://www.mysite.com/SugarCRM/cron.php

The above would equate to running http or a browser to execute the cron.php. Good luck.

SugarCRM Developers, we patiently await your wisdom on the original post.

What files should we look at to begin our journey to a solution?

Thanks for the help commshop, but what I have found makes it even stranger is that if I have an active session with SugarCRM and am logged in on another browser window, then accessing cron.php via the browser results in the success. Accessing the page when I am not logged into SCRM results in the IMAP error in the logs. Running a cron also results in the same error. I tried the running the soap script but typically came up against another brick wall as my host won't allow 'loopback connections' - hence fsockopen in nusoap.php won't work. Oh well, it might work for someone else who doesn't have these restrictions though.