Very odd piping problem

Fuze9-Hunter · 11:51 PM

I have piping set up for "abuse@fuze9.net". For some reason, piping works, but at the same time, every time you send an email to it, you get a mailer daemon message back saying it wasnt deleted =/

Code:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  pipe to |/usr/local/bin/php -q /home/fuze9/public_html/support/cli/index.php
    generated by abuse@fuze9.net

The following text was generated during the delivery attempt:

------ pipe to |/usr/local/bin/php -q /home/fuze9/public_html/support/cli/index.php
       generated by abuse@fuze9.net ------

I've had my server admins look at it, everything is set up how it should be - I've talked 3 times on live chat here at kayako about it, and none of them can figure it out either.

**bear** · 21-09-2007, 12:46 AM

Quote:

|/usr/local/bin/php -q /home/fuze9/public_html/support/cli/index.php

The part marked in red is actually part of the cron command, not the mail forward to pipe into Kayako. The "pipe" should be entered into the mail forward like this:

Code:

"|/home/fuze9/public_html/support/cli/index.php"

Fuze9-Hunter · 09:07 AM

Code:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  pipe to |/usr/local/bin/php -q /home/fuze9/public_html/support/cli/index.php
    generated by abuse@fuze9.net

The following text was generated during the delivery attempt:

------ pipe to |/usr/local/bin/php -q /home/fuze9/public_html/support/cli/index.php
       generated by abuse@fuze9.net ------

Still doing the same thing, and I think that I had it set up the right way in the first place when I first did it, and my server manager added that php bit in there. But for some reason it STILL automatically puts that php bit in there. Odd...

Strangest thing is that the system won't let me delete the forwarder either, I hit delete and nothing happens...

EDIT: Fatal! Write Failure: /etc/valiases/fuze9.net. Ignore any messages of success this can only result in failure! - just noticed that in cPanel once I click "Email" or "forwarders"

I think that I'm going to re-create the account tomorrow if theres no response or solution posted here, there might just be some funny picky error.

**bear** · 21-09-2007, 11:28 AM

You need to check the valiases file and see if that extra PHP bit exists in it. If so, remove it. The only other place that line should exist is in the "shebang" at the top of the actual /cli/index.php file.

Fuze9-Hunter · 02:14 PM

okay i got everything sorted out with that little problem, but mail is still getting returned -

Code:

 This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

 pipe to |/home/fuze9/public_html/support/cli/index.php
    generated by sales@fuze9.net

The following text was generated during the delivery attempt:

------ pipe to |/home/fuze9/public_html/support/cli/index.php
       generated by sales@fuze9.net ------

**bear** · 21-09-2007, 03:24 PM

Are tickets being created?
Is "index.php" set to have 755 permissions?

Fuze9-Hunter · 22-09-2007, 01:13 AM

Quote:

Originally Posted by bear

Are tickets being created?
Is "index.php" set to have 755 permissions?

Yes and Yes

Mohit Sharma · 22-09-2007, 05:08 AM

Hi,

This issue has been resolved on ticket.

Regards,

**bear** · 22-09-2007, 10:57 AM

It would be very helpful to know the cause and fix, Mohit, if it's not sensitive information. Simply saying "it's fixed" doesn't help the next user with an issue...

craigbrass · 22-09-2007, 02:17 PM

I do agree with bear on this. It helps others who have the same issue to fix it without submitting a ticket. I always ask users to do this when they say they have sorted the problem without saying how.

tommyquang · 29-05-2008, 08:22 AM

I'm having the same problem.

Quote:

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
pipe to |/home/user/public_html/cli/index.php
generated by xxx@domain.com
local delivery failed

I searched, read and tried everything, but I'm still not able to find a way to fix it.

accyroy · 21-07-2008, 10:03 PM

I'm also having this exact same issue - if the solution had been posted here I wouldn't now have to go and create a support ticket....

Siora · 22-07-2008, 12:27 AM

I am also having this problem....what is the fix for this?

accyroy · 22-07-2008, 02:46 PM

This is what worked for me. I guess some specific versions of exim make this problem appear because it worked fine until I moved it to a new server.

You need to make changes to /etc/exim.conf

Look for this section:

virtual_address_pipe:
driver = pipe

Add this line after driver = pipe
ignore_status

Restart Exim.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Piping problem (please help)	Indirect	E-mail Piping Issues	27	10-07-2006 01:41 AM

bear Offline Community Moderator Posts: 688 Join Date: Jan 2005	21-09-2007, 11:28 AM You need to check the valiases file and see if that extra PHP bit exists in it. If so, remove it. The only other place that line should exist is in the "shebang" at the top of the actual /cli/index.php file. ...read me...

bear Offline Community Moderator Posts: 688 Join Date: Jan 2005	21-09-2007, 03:24 PM Are tickets being created? Is "index.php" set to have 755 permissions? ...read me...

Mohit Sharma Offline Member Posts: 39 Join Date: Aug 2006	22-09-2007, 05:08 AM Hi, This issue has been resolved on ticket. Regards, Mohit used to be a Kayako staff member.

bear Offline Community Moderator Posts: 688 Join Date: Jan 2005	22-09-2007, 10:57 AM It would be very helpful to know the cause and fix, Mohit, if it's not sensitive information. Simply saying "it's fixed" doesn't help the next user with an issue... ...read me...

craigbrass Offline Senior Member Posts: 5,576 Join Date: Jun 2005 Location: Cumbria, UK	22-09-2007, 02:17 PM I do agree with bear on this. It helps others who have the same issue to fix it without submitting a ticket. I always ask users to do this when they say they have sorted the problem without saying how. Craig Brass - Kayako Forum Squatter (Note: I am NOT a staff member) Icon Headquarters - Its Elixir - Web2Messenger

accyroy Offline New Member Posts: 7 Join Date: Nov 2004	21-07-2008, 10:03 PM I'm also having this exact same issue - if the solution had been posted here I wouldn't now have to go and create a support ticket....

Siora Offline Member Posts: 1,308 Join Date: Apr 2007 Location: Toronto Canada	22-07-2008, 12:27 AM I am also having this problem....what is the fix for this? Siora Solutions Inc. www.sioraIT.com

accyroy Offline New Member Posts: 7 Join Date: Nov 2004	22-07-2008, 02:46 PM This is what worked for me. I guess some specific versions of exim make this problem appear because it worked fine until I moved it to a new server. You need to make changes to /etc/exim.conf Look for this section: virtual_address_pipe: driver = pipe Add this line after driver = pipe ignore_status Restart Exim.