Setup POP3 Fetching (email to ticket)
As of version 2.4 HESK supports POP3 fetching - converting emails from a POP3 email account into tickets.
» Setting up POP3 fetching:
Decide which email address you wish to use for support. Preferably this should be a new (unused) email account, such as firstname.lastname@example.org and have a valid POP3 account (check with your email provider if not sure).
Send a test email to your support email address (email@example.com). Do not read it!
On Linux servers, CHMOD file inc/mail/hesk_pop3.php to 755 (rwxr-xr-x).
Enable POP3 fetching in HESK Settings (Admin panel > Settings > Email tab > POP3 Fetching: ON).
Enter your email account details in the fields that appear then click the Test POP3 Connection button.
If you receive an Error message double-check your POP3 settings and make sure they are 100% correct. Do not continue with next steps until the test succeeds.
If you receive a Success message click the Save changes button at the bottom.
Open hesk_pop3.php file in your browser, for example:
Check your HESK admin panel - was a new ticket created?
» YES, ticket created:
Go back to HESK Settings and set the "From:" email setting on General tab to the email address you use for POP3 fetching (firstname.lastname@example.org). This will allow your customers to reply to tickets via email as well.
» NO, ticket not created:
- wait a few minutes then try again
- still nothing? Try the HESK Support forum
To automatically convert emails to tickets you will need to setup a CRON job (scheduled task) to run the hesk_pop3.php script for example every 5 minutes. Most hosting companies support CRON jobs, please check your hosting control panel or contact your host.
Alternatively, you may use a third party remote CRON service to call the hesk_pop3.php file for you.
Note: HESK will detect identical emails as an Email loop and ignore them. When testing POP3 fetching or Email piping make sure that each of your test email messages is unique.
Once you have POP3 fetching up and running it is strongly recommended to rename hesk_pop3.php to a hard to guess name, such as hesk_pop3_BZ1jKg4Zz0.php
Or (if you are using local CRON) secure the file with a .htaccess password.