I am having an issue fetching emails with cron. I have checked all of the settings under the client for incoming email and it is ok. When I run fetch manually, it works fine......

Cron is giving me this error...

warning: imap_open() [function.imap-open]: Couldn't open stream {208.17.196.42:110/pop3}INBOX in /home/wrender/public_html/sites/all/modules/jobtrack/jobtrack.module on line 1983.

CommentFileSizeAuthor
#2 cronjob_imap_error.png2.76 KBYura

Comments

wrender’s picture

I forgot to mention, to test I am just going to "reports" and then "status report" and running cron manually. This was just to speed up the process of having to wait for my actual cron to run.

Yura’s picture

Version: 6.x-1.6-rc1 » 6.x-1.5
StatusFileSize
new2.76 KB

I have same issue with manual run cron

gigiozzz’s picture

Category: support » bug

hi

i've the same problem

when i use the path ?q=jobtrack/fetch
mail fetch don't work
when i use the path ?q=admin/jobtrack/clients/1/fetch
it work fine

i've debugged a little
the problem is the connection string like explained in the past bug report
it need /notls or /novalidate-cert

you can try with this little code
-------------------------------------------
$mailbox = "{servername.com:110/pop3/novalidate-cert}INBOX";
$user = "xxxx";
$pass = "xxx";

$connection = imap_open($mailbox,$user,$pass) or die(imap_last_error()."
Connection Faliure!");

print "connection ok \n";
--------------------------------

when you GET jobtrack/fetch link Drupal call
jobtrack_fetch_client_mail()
jobtrack_active_clients()
IMHO in this last function there's a error if you add extra column to sql query it work fine
----
SELECT clid, name, path, status, integrate_email, server_name, server_username, server_password, mailfrom, mailbox, protocol, port, notes, autosubscribe,extra, domains FROM {jobtrack_client} WHERE status = 1
----

maybe the error comes after the last great new feature
http://drupal.org/cvs?commit=214162

please give me feedback
does it work to you??

jeremy’s picture

Status: Active » Fixed

Please upgrade to support-6.x-1.0-rc1 and report if this problem still exists. (The jobtrack module has been renamed due to possible trademark infringement.)

Status: Fixed » Closed (fixed)

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