Email Fetcher Auto Cron Question

[rjkunde]

Last night, I noticed that a client submitted a ticket to our email inbox at 9:30pm. Not until one of the technicians logged in, at 10:30pm did the email fetcher / cron job actually fire, and pull the email into the ticketing system.

Does anyone have a simple remedy or possibly auto cron script that will have the osTicket system pull email on a schedule, ex. every 10 or 15 minutes (when a user is not logged in?)

Thanks!

[ntozier]

Sounds like your using auto cron. You will want to read the section in this about cron

http://osticket.com/wiki/POP3/IMAP_Settings

[rjkunde]

Thanks ntozier, looks like you can simply schedule a windows task (assuming windows web server) to run cron, and this way a user doesn't need to be logged into the system in order to have the email fetcher work correctly. Thank you for the information. Will post results.

[rjkunde]

For anyone attempting to accomplish the auto cron feature I mentioned earlier:


I made a batch file that runs with the windows task scheduler, and stored it on the web server. It contains the following code, and I named it autocron.bat

echo off
c:\php\php.exe c:\inetpub\"path to website goes here"\api\cron.php
exit

then in task scheduler I have it running every 5 minutes, I verified it works by having all users log out of osticket, send an email to the ticket inbox, and ran the batch file... It successfully pulls the emails out of the inbox. This could be useful if you need emails pulled into osticket after normal business hours.

screenshot of the task is attached. Note: Task runs as a local administrator, I would not recommend using a domain admin account, because it cache's the credentials inside task scheduler, which might be a security issue.

[ntozier]

Sorry! I wasn't really near a computer all weekend. Yes you can use windows Task Scheduler. (I do!) I did a quick search here on the forums and found an old post about it here:

http://osticket.com/forums/showthrea...highlight=cron

We've since upgraded our server and IIS but it should generally be the same since TaskSched hasn't really changed much.

I'm glad that you got it working, and thanks for posting a good explanation here on the forums!