Hello,
I'm now officially reporting issues with eTicket 1.7.2 using the POP3 mail method. I am unable to use the pipe method due to the fact that mail does not come inbound to our server (we use Google Apps and do not accept inbound mail to this server).
I am the server admin of our dedicated server (running Ubuntu 7.04 Feisty Linux), so I am able to provide any information you need. I am interested in helping get to the bottom of this issue as it seems several other people are having the same problem (based on research in this forum).
First of all, is there anyone that can confirm that the POP3 method is working under eTicket 1.7.2?
We are currently using an older version of eTicker with this method, and not having any problems. I am unable to confirm the older version number, unless you can tell me where to look (it is not listed in settings.php)
By the way, the settings in use for Gmail on the older version are:
Name: esupport
POP3 Host: pop.gmail.com:995/ssl
POP3 Username: esupport@ourdomain.com
We have currently setup eTicket 1.7.2 in a separate directory, and with a separate Gmail account for R&D.
The problem details are the same as most other people are reporting:
- Outbound mail works fine
- Inbound mail or replies to tickets does not work at all
- Executing automail.php returns to the prompt almost immediately and no errors or warnings that I can find in any logs (I also commented out the error_reporting(0); line at top) -- seems like this step should at least take a few seconds.
Below is my output from the troubleshooter:
Troubleshooter:
* PHP version: 5.2.1 (Should be PHP 5.0.0 or above)
* PHP Safe Mode is off
* Webserver: Apache
* GD version: 2.0 or higher
* Multibyte String is installed
* iconv version: 2.5
* IMAP is installed
* Socket support enabled.
* User Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.16) Gecko/20080715 Ubuntu/7.10 (gutsy) Firefox/2.0.0.16
* Character set:
* Link: http://secure.ourdomain.com/eticket/troubleshooter/troubleshooter.php
Please note that Character set appears blank in this report, but it is infact set to UTF-8 in the admin interface as well as the db table.
We are not doing anything out of the ordinary here and just trying to get started with a plain vanilla install. Once that's working we will move forward with customizing.
Thanks in advance for any tips, and please advise what other info or tests you would like me to run to help track down the source of this problem.
Thank you very much for keeping eTicket open source -- this app is great!