Email Piping

hypuk

Hi there

Where in the admin settings do I enable email piping?

Regards

Mark

faction918

I have not personally set up email piping so I am no expert, but until someone else replies with more info than me you could take a look here: http://osticket.com/wiki/Email_Piping(http://osticket.com/wiki/Email_Piping)

I'm assuming you have already read that, so with that said... This is not something you setup in the osticket settings... this is set up on your web server. Are you using your own webserver (LAMP install) or a shared host?

hypuk

I know how to set it up on my server, in previous versions of OSTicket, you had to enable a checkbox in the admin settings to enable email piping but I can't see this option anywhere in the preferences.

faction918

I just set it up on my shared host using cPanel and did not need to enable any options in the osTicket config. Only change I made to osTicket at all was CHMOD 755 ./pipe.php

Tickets and replies seem to be working fine. I never played with the older version so it looks like they took out that options to turn off piping?

PaulC2K

Yeah, the wiki seems to be dated, there is no option. It seems it should just work without needing to tell it.

My issue seems to be that while the pipping works, and i instantly get a auto-response with my ticket info, i also get a mail delivery failed email with it, including an error message.

PHP Notice: Undefined index: SCRIPT_NAME in /home/DOMAIN/public_html/support/main.inc.php on line 19

PHP Warning: session_start() : Cannot send session cookie - headers already sent in /home/DOMAIN/public_html/support/include/class.ostsession.php on line 39

PHP Warning: session_start() : Cannot send session cache limiter - headers already sent in /home/DOMAIN/public_html/support/include/class.ostsession.php on line 39

faction918

@[deleted]: There is a section in that wiki page regarding mail delivery failed... does that apply?

http://osticket.com/wiki/Email_Piping#Mail_delivery_failed(http://osticket.com/wiki/Email_Piping#Mail_delivery_failed)

Mail delivery failed

If you have the error: 'Mail delivery failed: returning message to sender' but the user's email is still successfully processed.

You have some options

1. Update php.ini

/usr/local/lib/php.ini update: display_errors Off

restart apache

2. Update exim.conf:

Update /etc/exim.conf in the section:

address_pipe:

driver = pipe

return_output

virtual_address_pipe:

driver = pipe

group = "${lookup{$domain}lsearch* {/etc/userdomains}{$value}}"

return_output

user = "${lookup{$domain}lsearch* {/etc/userdomains}{$value}}"

Change return_output to return_fail_output

REASON: (from exim.conf comment)

If the pipe generates any standard output, it is returned to the sender of the message as a delivery error. Set return_fail_output instead of return_output if you want this to happen only when the pipe fails to complete normally. You can set different transports for aliases and forwards if you want to - see the references to address_pipe below.

PaulC2K

Having another look, i guess it does apply. I think when i first read it i'd just assumed it meant when submitting web tickets it wasnt giving any kind of errors, it hadnt occurred to me it was for the bounce backs.

Im on shared hosting, i've tried creating a php.ini with 'display_errors Off' in the osT root folder & /include folder too, and ive also tried what appears to be a global setting within the cPanel configuration settings, but for both i still continue to get the returned emails. I obviously dont have the power to restart apache, and ive no idea if thats something which is done scheduled, if i'd have to request that, or if it'd just work anyway. Usually any adjustments in a php.ini would have instant results.

I wouldnt have a clue where to begin with exim.conf, if i even have the means to adjust that.

faction918

I don't know a ton about this stuff but i'll try to help...

If your on a shared host (as I am too) you're not going to be able to edit their server files directly and they most likely aren't going to restart apache for you. I was doing some research and it looks like you can override the php.ini file with an .htaccess file. See this stackoverflow post: http://stackoverflow.com/questions/7781927/overriding-global-php-ini-file(http://stackoverflow.com/questions/7781927/overriding-global-php-ini-file) and note "imm's" two links.

Sounds like you can add this to your .htaccess file:

php_flag display_errors off

PaulC2K

Sadly it doesnt appear to be having any impact :(

I've tried:

.htaccess

php_flag display_errors off

php.ini

display_errors = 0;

display_errors = Off;

I've put those in the root osT folder, /includes, and /api seeing as thats where the pipe.php file is. Im still getting the delivery failed email as well as the auto-responder.

I'll give it a while and see if something just naturally falls into place, but it not looking positive for me.

Infact, looking at a phpinfo report, thats saying display_errors is off as the master and local value.

I can switch between php5.3 & 5.5 freely and that shows in the phpinfo, however enabling & disabling display_errors has no effect, but its always 'off' anyway which would be what i'd want anyway.

faction918

This is a shot in the dark... do you have any cron jobs running for osTicket?

PaulC2K

I had one initially for when i was trying the POP route, but i removed that a day or 2 ago on the off chance it could be causing a conflict.

faction918

I did see some posts with a similar error and a cron job. Sorry man, I don't have any other ideas as of now. Hopefully someone else can help??