Using v 1.8.0.1I've had one customer today tell me the e-mail they received yesterday as a reply had no content, and another send me this back to show what he received....I'm at a loss to explain this as it was working fine during testing and others seem to be receiving the e-mails fine...I cant paste the gibberish example because the forum then tells me the body is X characters too long, so here's a screencap.
For the record, the templates all look fine. I've asked one of the customers what client they use and am awaiting a reply. In the meantime, it appears the attachment I added didn't upload, so here's the screencap:
hiI noticed i had this error when using built in php mail and not when using smtp server. Try it. in admin panel -> emails -> emails and change the setting in the email you use.
I am not able to reproduce your report. I will however ask the devs to take a look at this thread.edit: Missed thisYou might also want to read the following thread on github.https://github.com/osTicket/osTicket-1.8/issues/202#issuecomment-32816077
Seems like Outlook is the common thread in these cases. Not terribly surprising that MS's e-mail has the standards compliance their browser had as of IE7 or so...I will report back once I find out what client these two are using.
As a side note we use Outlook 2007 and 2013 here in house and have not had this problem reported to us.
Customer reported using outlook 2010, I could not reproduce on outlook 2013 and 2007 either, but the client confirmed it was working when I switched from php mail to smtp in the config.
Hm. Yeah, my customer just replied and said he is using Windows 8 with Outlook as his client. I'll have to check into the SMTP setup.
We have an issue on the GitHub project page at https://github.com/osTicket/osTicket-1.8/issues/202 to track the issue. I have a patch posted as a suggested fix. Could anyone verify if it fixes the issue?
I enabled SMTP for sending in the configuration late yesterday afternoon and did a couple tests, and it seems to have worked for both customers who had the issue. It will take further use of course to see if anyone else pops up with this issue still.
As a side note 1.8.0.2 was released last night so it might fix your problem as well.
