Error in emails

[OCReactive]

Script URL:
Mods for HESK version: 2018.1.0
HESK version: 2.8.1
Hosting company:
URL of phpinfo.php:
URL of session_test.php: OK
What terms did you try when SEARCHING for a solution: MIME

Write your message below:

Since updated HESK to 2.8.1 and MfH to 2018.1.0 I get the emails in plaintext starting with this code: https://pastecode.xyz/view/raw/4f67651c
Then, there is the plaintext email's-text, and then the html email's-text.

Could be a translation's error?

[mkoch227]

Does this happen when HTML-enabled emails are turned on? If yes, does it still happen when HTML-enabled email are turned off?

[OCReactive]

I've disabled HTML emails but I still get the MIME text.

[lcockell]

Mods for HESK version: 2018.1.0
HESK version: 2.8.1

I also have the same since updating. I get a similar header but wont allow me to post it in this reply. when html is on or off.


Also when Allow Html email is switched on I get the body of the message twice. Once in plain text and once html formatted. It does not autoselect the correct template.

[mkoch227]

OCReactive or lcockell: Can one of you PM me one of the emails that looks incorrect? Please make sure you send the "original message" (which contains all of the email headers). I just sent a "New ticket" email from the demo site and it came out correct, but I want to make sure that it's not gmail auto-correcting anything

[mkoch227]

Thanks OCReative for the example. Can one (or both of you) try making the following change and see if it resolves the issue?

In email_functions.inc.php, find (line 574):

Code: Select all

"Message-ID: " . hesk_generateMessageID() . "\n",

replace with:

Code: Select all

"Message-ID: " . hesk_generateMessageID(),

Then go ahead and save, upload, and test. I'm wondering if the stray new line at the end of the header is causing issues with some mail clients.

[lcockell]

That seems to have fixed the problem for me.

[OCReactive]

It works for me as well!

[gosanchezamdc]

Great!
Worked for me!
Thanks a lot.

[PeteHanley]

I had the same issue when I upgraded today. I just made the change to that line and it worked for me.