@BlackHawk17

So you made the changes listed in both of these pull requests?
https://github.com/osTicket/osTicket/pull/4731
https://github.com/osTicket/osTicket/pull/4758

Cheers.

@BlackHawk17

At this point I'm at a loss as it works just fine for me on 1.10.5 and 1.11.

Have you tried sending mail from the Gmail app instead?

Cheers.

Outlook?

We use Outlook 2016 here, and do not have the problem that you are experiencing.

You had mentioned "Shopify App" so I presumed that the app was malforming the emails.

@BlackHawk17

This is driving me nuts too. Something has to be awry with your setup as emails from Gmail desktop/mobile work just fine for me on the 1.10 series and the 1.11 series (even old 1.9 series). Even YaHoo emails work fine in my testing. Piping works as well as fetching and we have thousands of customers using outlook, gmail, yahoo, and other 3rd party mail providers just fine on the latest codebase (v1.11) on a daily basis. Before this we were running v1.10.x and there were little to no issues with this either for years. Very little issues have been reported with incoming mail and 9 times out of 10 it was the mail provider/mail server/configurations causing the issues. The other 1 out of 10 reports were actual issues and have all been addressed and included in the maintenance releases of v1.10.1-5. If you’re running 1.10.5 or v1.11 you should see no issues with your incoming mail.

A good way to test stuff like this is to get the entire raw contents of an email that hasn’t been fetched yet (in gmail you can click on an email, click the more button, and select view original), copy the raw contents, make a .txt file, paste the contents in the .txt file, save it, and run the following command (will differ depending on the system you’re running; just google how to run a php script via cli on your system; the api/pipe.php < filename.txt part should be the same though):

$ php /path/to/api/pipe.php < filename.txt

This will attempt to pipe the email into the system and if successful should create a ticket, send out an alert, etc. (this simulates email piping) If not, you should see errors. With the errors start looking at what it’s complaining about and check the corresponding data in the raw email to see if anything is malformed/etc. like recipients/etc. You can post the errors you find here if you need more help.

Note

Get this, I just tested mail from native iPhone app via piping on v1.11 and this worked without a hitch.

Cheers.

@BlackHawk17

WHEW! Sweeeettt! I'm so glad it's working for you now. The piping issue is driving me insane because I can't replicate it! I wish I could so I could at least explain to you why but I can't ?

Cheers.

@BlackHawk17

It's funny because they are the only ones having this issue ? GREAT!

I'm glad you have a working solution as well. Just bugs me that I can't figure it out as I don't have access to the servers/etc. Unfortunately, I would need an account with them to configure, test, debug, etc.

Cheers.

ryance85

Hello ryance85

Tried that and disable html format worked for a while then gone back to acting up again.

Any other suggestions

Regards

I got the same issue with (empty) message body after the upgrade to v1.17.
After looking into the mimeDecode.php code and analyzing the email source, I figured out the problem and found a fix.
Email message had 'Content-Type: multipart/multipart' which was not processed in the decode function.
so I added this code after line 310:
case 'multipart/multipart':
if(!isset($content_type['other']['boundary'])){
$this->error = 'No boundary found for ' . $content_type['value'] . ' part';
return false;
}
$default_ctype = (strtolower($content_type['value']) === 'multipart/digest') ? 'message/rfc822' : 'text/plain';
$parts = $this->boundarySplit($body, $content_type['other']['boundary']);
while (count($parts)) {
$part = array_shift($parts);
list($part_header, $part_body) = $this->splitBodyHeader($part);
$part = $this->decode($part_header, $part_body, $default_ctype);
if($part === false)
$part = $this->raiseError($this->error);
$return->parts[] = $part;
}
break;

Hope it helps.
Cheers