eTicket Community
September 02, 2010, 02:34:46 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Got Bug? Please use the new tracker at http://www.eticketsupport.com/tracker
 
   Home   Help Search Login Register  
Quick Register
Choose username  Email                 
Verify password    Choose password 
I agree to Registration Agreement
Pages: [1]   Go Down
  Print  
Author Topic: Mail delivery failure  (Read 1149 times)
0 Members and 1 Guest are viewing this topic.
alle50
New Member
*

Karma: +0/-0
Offline Offline

Posts: 5


« on: November 12, 2008, 04:51:44 AM »

When an end user send a message to the support email, he receives the confirmation reply from eticket system with the ticket number but at the same time he receives a delivery failure; this is part of the message:

Quote
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/horseand/public_html/eticket/pipe.php

Any idea why this happens?
Thank you
Logged
Hummdis
Moderator
Super Member
*****

Karma: +13/-0
Offline Offline

Posts: 601


In a world without fences, who needs Gates?


WWW
« Reply #1 on: November 12, 2008, 09:12:04 AM »

Does the email actually make in INTO the ticket system?

Have you tried the pop3 method?
Logged

Don't PM me directly for help.  Post to the forums, that's what they are for after all.  PM's to me that request help will be ignored.

Hummdis Web Design - Freelance Website Design & IT Consulting
eserikto
New Member
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #2 on: November 12, 2008, 03:09:24 PM »

I had the same problem, put a -q at the end of line 1 of your pipe.php so it looks like this

#!/usr/bin/php -q

that fixed the problem for me
Logged
Hummdis
Moderator
Super Member
*****

Karma: +13/-0
Offline Offline

Posts: 601


In a world without fences, who needs Gates?


WWW
« Reply #3 on: November 12, 2008, 03:52:44 PM »

Ah...I noticed that I fixed the problem without making a mental note.  I changed my PHP path to:

Code:
#!/usr/bin/env php

That explains why it works for me. Smiley
Logged

Don't PM me directly for help.  Post to the forums, that's what they are for after all.  PM's to me that request help will be ignored.

Hummdis Web Design - Freelance Website Design & IT Consulting
alle50
New Member
*

Karma: +0/-0
Offline Offline

Posts: 5


« Reply #4 on: November 14, 2008, 01:40:37 AM »

Thanks guys. I have tried adding the #!/usr/bin/php -q on the pipe.php and it works fine. I haven't tried the other option.

Do you know what the -q does?

Logged
Hummdis
Moderator
Super Member
*****

Karma: +13/-0
Offline Offline

Posts: 601


In a world without fences, who needs Gates?


WWW
« Reply #5 on: November 14, 2008, 02:21:39 AM »

The "-q" tells the parser not to generate HTTP header information and HTML output.  So it's advisable that you use "#!/usr/bin/php -q" and not my original line of "#!/usr/bin/env php" -- which uses PHP based on the defined path the the executing users environment variable.  I changed my code after I realized the significant difference. Smiley
Logged

Don't PM me directly for help.  Post to the forums, that's what they are for after all.  PM's to me that request help will be ignored.

Hummdis Web Design - Freelance Website Design & IT Consulting
eTicket Community
   

 Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.8 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
Page created in 5.785 seconds with 23 queries.

Google visited last this page September 19, 2009, 08:10:50 PM