Zoltan Posted May 13, 2014 Report Posted May 13, 2014 I'm not sure if this is a bug... The email piping is working, because the emails are arriving to Blesta, but whoever sends an email, receives this ( I have changed my email to "email address"): 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/cmhosth/public_html/ugyfelek/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1/ generated by (email address) The following text was generated during the delivery attempt: ------ pipe to |/home/cmhosth/public_html/ugyfelek/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1/ generated by email address ------ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us" dir="ltr"> <head> <title>Blesta</title> <link rel="stylesheet" type="text/css" href="/home/cmhosth/public_html/ugyfelek/plugins/support_manager/app/views/errors/css/styles.css" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> </head> <body> <div class="program_error"> <h3>Oh noes!</h3> <div class="contents"> <p>Object of class MimeMailParser could not be converted to string on line <strong>124</strong> in <strong>/home/cmhosth/public_html/ugyfelek/lib/model.php</strong></p> </div> </div> </body> </html> ------ This is a copy of the message, including all the headers. ------
PauloV Posted May 13, 2014 Report Posted May 13, 2014 I'm not sure if this is a bug... The email piping is working, because the emails are arriving to Blesta, but whoever sends an email, receives this ( I have changed my email to "email address"): 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/cmhosth/public_html/ugyfelek/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1/ generated by (email address) The following text was generated during the delivery attempt: ------ pipe to |/home/cmhosth/public_html/ugyfelek/plugins/support_manager/pipe.php plugin/support_manager/ticket_pipe/index/1/ generated by email address ------ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us" dir="ltr"> <head> <title>Blesta</title> <link rel="stylesheet" type="text/css" href="/home/cmhosth/public_html/ugyfelek/plugins/support_manager/app/views/errors/css/styles.css" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> </head> <body> <div class="program_error"> <h3>Oh noes!</h3> <div class="contents"> <p>Object of class MimeMailParser could not be converted to string on line <strong>124</strong> in <strong>/home/cmhosth/public_html/ugyfelek/lib/model.php</strong></p> </div> </div> </body> </html> ------ This is a copy of the message, including all the headers. ------ Do you have debug mode enable on blesta.php file? if so disable and trie it again. We have the same bug wen we enable PIPE (we didnt trie in 3.2-b3 yet)
Michael Posted May 13, 2014 Report Posted May 13, 2014 I've not had an issue so far and we use piping?
Zoltan Posted May 14, 2014 Author Report Posted May 14, 2014 I have set up piping and was working fine. Then we have turned on debug mode and we have these emails. Thanks for the suggestion, it was the debug mode. I turned it off, it is working fine now.
Cody Posted May 14, 2014 Report Posted May 14, 2014 The issue appears to be with line 290 in /plugins/support_manager/components/ticket_manager/ticket_manager.php. if ($this->SupportManagerTickets->checkLoopBack($email, $this->max_reply_limit, $this->reply_period)) { Should be: if ($this->SupportManagerTickets->checkLoopBack($address, $this->max_reply_limit, $this->reply_period)) { Does making that change resolve the issue for you?
Recommended Posts