@KevinTheJedi
Thanks for your last reply!
However here is what I ended up doing today 3/21/19
Blew out my TEST Help Desk and Rebuilt it with a clean install of osTicket ver1.11
Still found the Forwarding/Piping method to be unreliable and stripping out the body of the messages and generating the API errors most of the time unless I was replying specifically from the Gmail App on my iPhone.
So I turned off the forwarding/piping method and turned on the Fetch/IMPAP/SMTP/CRON JOB method.
And so far its working correctly with Native iPhone Mail, iPhone Gmail App, Gmail Web and Outlook 2013 from my desktop pc.
Cron Job Command:
osTicket Example = */5 **** nobody /path/to/php /path/to/api/cron.php
The one I used = */5 **** /usr/bin/php /path/api/cron.php
Note: I had to remove the (nobody) as it caused the job to fail when using it
I just changed over to IMAP/Cron on my live Help Desk and it looks good so far. ?
Customer New Ticket Using Web Form = Good
Customer New Ticket from Shopify Web Form = Good
Reply from Outlook 2013 on Desktop pc = Good
Reply from Web Base Gmail on Desktop pc = Good
Reply from iPhone using Gmail App = Good
Reply from iPhone Native Mail App = Good
Now this is how it's supposed to work...why didn't I do this sooner. LOL
Also I have a Ticket with NameCheap Support asking them to explain why the forwarding/piping is generating the API errors.
Well see what happens but at least this IMAP/Cron Job method might work for now. ?
Thanks again for all your help and support!
Regards, BlackHawk17