I was using the 1.9.x version of this software for months on end without any issues what so ever. A couple months ago all the sudden it would stop interpreting HTML messages from a certain sender. I since then have tried PHP7.x and upgraded the OS Ticket installation I had to 1.11. I've also tried 1.10 just to see if that would work. I notice someone explaining code for Pear MIME types but this version doesn't have an api/tickets.email file to see if updated PEAR code works.

I recently installed 1.11.0-rc1 freshly and piped the emails over. Again the same sender which shows fine on any other email program results in missing BODY everything is stripped....

The closest answer to my solution is posted here https://github.com/osTicket/osTicket/issues/3278

Unchecking the Enable html in thread entries and email correspondence. Is the only way to get the body to show up in these messages from that sender.

Is this something expected to be fixed in the upcoming release? Do you suspect something is wrong with Blue Host email encoding?

I am all out of solutions other than looking for another ticket support system. Any suggestions are welcome.

API Unexpected Data - Is the only Log error I see...

PHP Warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead in /public_html/tickets/include/pear/Mail/mimeDecode.php on line 648

So you provided a lot of information.It seems to me that you should be running PHP5.6 (recommended) and 1.10.4 (stable as of this writing).  But with all the changes you made I'm not real sure what versions of what you are running now.I know that the devs will ask for an example email (with full mail headers) to test with.  I've asked them to take a look at this thread.

From support@mydomain.com Mon Oct 01 14 2018

Received: from web.mydomain.com ( helo=localhost)

by box1350.bluehost.com with esmtpsa (TLSv1.2-RSA-AES128-GCM-SHA256)

(Exim 4.91)

(envelope-from <support@somedomain.com>)

id 1g74mq-002Kvo-59

for support@somedomain.com; Mon, 01 Oct 2018 14 -0600

From: support@somedomain.com

To: support@somedomain.com

Subject: Welcome

Date: Mon, 01 Oct 2018 20 +0000

Content-Type: text/html; charset=iso-8859-1

Content-Transfer-Encoding: quoted-printable

Content-Disposition: inline

MIME-Version: 1.0osTicket Versionv1.11.0-rc1 (e321982) —  Up to dateWeb Server SoftwareApacheMySQL Version5.6.32PHP Version5.6.37

1.10 Stable does the exact same thing. It seems like this references MIME pear code repositories that don't exist anymore hence the fact it just stopped working without me doing anything to the server, files, or settings.If it helps , the emails come from a Magento installation on a NGIX server which is separated from my shared blue host server which hosts email and my Os Ticket install.... The original email is sent from a secondary private VPS server from OVH.  ( the one with Magento installed )  So basically the emails come from the same domain but the sending server is not the same as the OS Ticket install.. It worked flawless for months on end. I've even tried to send the emails through SMTP IMAP on OS Ticket and the email sending server to see if it was a PHP piping issue. Same result. If I send an email from that server by php function. All users get the emails just fine unless it's Yahoo servers complaining about DKIM then sometime they go to spam. 

Now maybe this broke something else but all is well here now and working fine after replacing the MimeDecode php file with a later version from the source site

https://pear.php.net/package/Mail_mimeDecode/

WARNING: I do not know if this is the right solution for you. Install this file with care.

Emails are now being decoded properly and (EMPTY) has not appeared again.

Write a Reply...