It would be really good if I could get this module working and thanks for putting it together.

1. Set up the client as per INSTALL.TXT
2. Went to clients/fetch
3. Clicked on fetch
4. Screen went blank
5. Returned to clients/fetch
6. The following warnings appeared in red box with summary in blue box

################### Warnings ##################################

* warning: set_time_limit() [function.set-time-limit]: Cannot set time limit in safe mode in /var/www/vhosts/mayfield.co.nz/subdomains/mws/httpdocs/sites/all/modules/jobtrack/jobtrack.module on line 1155.

* warning: imap_open() [function.imap-open]: Couldn't open stream {202.89.57.13:110/pop3/novalidate-cert}info@ashburtonartgallery.org.nz in /var/www/vhosts/mayfield.co.nz/subdomains/mws/httpdocs/sites/all/modules/jobtrack/jobtrack.module on line 1193.

* Imap error: Can't open mailbox {202.89.57.13:110/pop3/novalidate-cert}info@{client name}.org.nz: invalid remote specification

* warning: set_time_limit() [function.set-time-limit]: Cannot set time limit in safe mode in /var/www/vhosts/mayfield.co.nz/subdomains/mws/httpdocs/sites/all/modules/jobtrack/jobtrack.module on line 1155.

* warning: imap_open() [function.imap-open]: Couldn't open stream {202.89.57.13:110/pop3/novalidate-cert}info@ashburtonartgallery.org.nz in /var/www/vhosts/mayfield.co.nz/subdomains/mws/httpdocs/sites/all/modules/jobtrack/jobtrack.module on line 1193.

* Imap error: Can't open mailbox {202.89.57.13:110/pop3/novalidate-cert}info@{client name}.org.nz: invalid remote specification

################### Summary ##################################

* Fetching mail for {client name}...
* Failed to download messages for{client name}, connection to mail server failed.
* Fetching mail for {client name}...
* Failed to download messages for {client name}, connection to mail server failed.

###########################################################

It seems to be retaining the warning and error information. The warnings and info ARE REPEATED after two failed attempts

Comments

jeremy’s picture

Status: Active » Postponed (maintainer needs more info)

If you get a white screen, you should review your Apache error_log.

From the errors you got on the subsequent pages, it's clear that your mail connection is not properly configured. Double check all your settings, including your pop account and password. If you're sure they're all correct, test the connection with telnet (telnet HOST 110), and be sure you can sign on with the username/password you are using, such as is described here.

The latest development code in CVS displays additional debug information when you have "administer jobtrack" permissions and you try and fetch mail manually.

philprism’s picture

Thanks for the response. Just picked this up, Checking and will be back shortly.......

##########################BLANK SCREEN######################

I used telnet to verify the server could be reached and logged into the mail account ok (thanks for the tip)

No errors recorded in apache log

server is in safe mode and the ISP wont change it this means the call to set_time_limit(0); is ignored so there is no time limit on execution.

I commented out the return -1 exit point at line 1207

I replaced it with the following

DECLARED $f_return_val = TRUE;

$f_return_val = FALSE;
}

if ($f_return_val === TRUE)
{
.
. Code not executed on failure
.
}

if ($manual) {
drupal_goto('admin/jobtrack/clients');
}

The blank screen problem is solved and the code which follows the imap errors is not executed, that is what you intended I think.

So navigates OK now but I am still stuck on the imap errors

##############################IMAP ERRORS###########################

I noticed the path {webmail.mayfield.co.nz:110/pop3/novalidate-cert} doesnt correspond to a location in the root

warning: imap_open() [function.imap-open]: Couldn't open stream {webmail.mayfield.co.nz:110/pop3/novalidate-cert}admin@mayfield.co.nz in /var/www/vhosts/mayfield.co.nz/subdomains/mws/httpdocs/sites/all/modules/jobtrack/jobtrack.module on line 1194.

I also notice the location is hard coded into the $connect variable for

$connect .= '/pop3/novalidate-cert}'. $client->mailbox;

is this guaranteed on every ISP as a POP3 standard?

################CONTEXT ASSUMPTIONS FOR CLIENT CONFIGURATION ##############

Client name: * {Literaly the clients name }
Path: * {Not sure what the path variable refers to}
Server name: * {I have taken this to mean the clients mail server}
Hostname or IP address.
Server username: * {I have taken this to mean the clients mail server username}
Server password: * {I have taken this to mean the clients mail server password}
Mailbox: * {I have left this as the default INBOX}
From address: * {I have taken this to mean the SENDERS email address}
Port: * {I have taken this to mean the clients mail server port}

Now this might seem obvious to you but I am not clear about why I am fetching, where I am fetching from, and the purpose of the fetch within the jobtracker workflow.

Am I supposed to be pulling emails from the clients mailbox or pulling emails from jobtracker for onward delivery to the client???

############################

Its looking good now it doesn't hang on the blank page and I am porting jobs to it..... :-)

jeremy’s picture

Thanks -- fix committed to properly display errors instead of a white screen and to log them in the watchdog.

I do not know if the path needs to be variable -- this is what works with my host. Can look here and see if you can find a path that works for you? I'd like to simplify the configuration process as much as possible.

For the rest of your questions, there's some more info here answering your path question.

Yes, I agree that the config page is confusing -- I do intend to clean it up and add inline documentation. Patches are welcome! Otherwise, well, this is still a beta release.

To properly use this ticketing system, you will need to manage a mailbox for each client. For example, if your domain is sample.com, and you have clients "foo" and "bar", then you will want to set up an account "foo@sample.com" and "bar@sample.com". Now, all email communication with client "foo" should also be cc'd to "foo@sample.com" and the ticketing system will track it for you -- creating and updating tickets as necessary for you.

I suppose the mail portion of jobtrack could be made optional, but it is the primary reason that I've written jobtrack.

--

I am leaving this issue open until we track down the proper parameters to pass to imap_open() for mail to start working for you. Let's keep this issue focused on that single item -- other questions and problems should be moved into their own issues. One problem per issue to keep things focused and organized.

jeremy’s picture

Status: Postponed (maintainer needs more info) » Fixed

No further feedback, closing ticket.

Status: Fixed » Closed (fixed)

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