Remote piping, where is tickets.email???

cjay

I found another forum on this same topic but no answer was given. From the instructions:
Remote piping is useful when osTicket installation and the mail server are on two separate machines. To maintain logic in one place remote piping is done over HTTP post to osTicket’s API. osTicket ships with two scripts to help you accomplish this task; automail.php and automail.pl. Both accomplish the same task by posting to http://www.yourdomain.com/osticket/api/tickets.email (replace osticket with the folder name where you installed osticket)

I set up the mail forward to the pipe pointing to the automail.php script and changed the URL and API key to my OSTicket server. But the mail is failing as "tempory delivery failure" and never gets into the OSTicket system. Only thing I can see is the missing tickets.email script.

Help to locate the tickets.email file...

cjay

Update: I did see a post where the user switched the "api/tickets.email" with the "api/pipe.php" on the OSTicket server and commented out the code where it checks if running local to the mail server. This works to an extent. The issue is the mail server doesn't receive proper success code from the HTML request which I'm sure the pipe.php script is not performing. This causes the message to end up as a temporary delivery error and stays in the mail server mail queue even though the message was successfully entered into the OSTicket system. Which would eventually fail back to the sender as an undeliverable message.

I hacked the automail.php file to always return status "0", success, and that keeps the message from ending up as a failed delivery. But the main issue remains, where is this mystery tickets.email file?

ntozier

Have you consulted the documentation?
https://docs.osticket.com/en/latest/Getting%20Started/Email%20Piping.html

cjay

Yes, that is the same document I'm following. Where is the tickets.email file?

"Both accomplish the same task by posting to http://www.yourdomain.com/osticket/api/tickets.email (replace osticket with the folder name where you installed osticket)"

cjay

By the way running lastest git pull 1.12 version

ntozier

I do not think that osTicket has ever come with a file called tickets.email. I think that it was a re-direct to pipe.php. I've asked a dev for clarification though.

ntozier

The devs tell me that this is not a file and that it is a redirect. But I was wrong it is not to pipe.php its to api.tickets.php. I think that perhaps he means api.inc.php or I'm reading his response wrong.

which was:
url_post("^/tickets\.(?P<format>xml|json|email)$", array('api.tickets.php:TicketApiController','create'))

cjay

I'm not following the logic here. If tickets.email is a redirect, where is that defined? Running curl command this is what I get:

curl -d "{}" -H "X-API-Key:8602ACA8XXXXXXX" http://help-test.cosine.oregonstate.edu/asbc/api/tickets.email
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /asbc/api/tickets.email was not found on this server.</p>
</body></html>

I then tried the http.php file in the api folder but that doesn't work either:

curl -d "{}" -H "X-API-Key:8602ACA828BA083D1XXXXXXXXXXXXX" http://help-test.cosine.oregonstate.edu/asbc/api/http.php
URL not supported

So far, the only thing that looks to work is pointing to the api/pipe.php.

KevinTheJedi

@cjay

If tickets.email is a redirect, where is that defined?

@ntozier just told you, it's defined here:

url_post("^/tickets\.(?P<format>xml|json|email)$", array('api.tickets.php:TicketApiController','create'))

It goes from browser, to api/.htaccess (URL rewrite), to api/http.php, to inclue/api.tickets.php. Just follow the code.

Cheers.

cjay

Okay, success! You need to make sure your web server is set up to allow processing .htaccess. Something that should be included in the instructions. I created a new htaccess.conf file in /etc/http/conf.d folder with the following:

<Directory "/var/www/html/">
Options Indexes MultiViews FollowSymlinks
AllowOverride All
Require all granted
</Directory>

I'm only running OSTicket on this server. Probably other better ways to fix this than what I did.