-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hebrew Characters turn to Gibberish when ticket is received via 0Auth with Office365 #17396
Comments
this is the closest issue I found on the subject #7709 |
Hi, Please check if the problem persists in GLPI 10.0.15. If problem persists, please attache the message into |
Testing after 10.0.15 בדיקה נוספת אחרי מעבר לגרסה חדשה.eml.zip it was blocking the .eml file so it's attached inside this compressed zip file. |
I validate the issue. It sees that the problem is related to usage of
|
Issue solved. By editing Mailcollector.php I was able to edit the functions decodeMimeHeader and getDecodedContent to be able to handle Hebrew characters. the decoding function that works for incoming emails from M365 is mb_convert_encoding. Attaching my code snippets of Mailcollector.php for your consideration. I will test some more next week but you can close this thread if you want.
|
Could you please open a pull request with your changes? Test suite will run with your changes; and it's easiest for us to review changes. |
Code of Conduct
Is there an existing issue for this?
Version
10.0.12
Bug description
I installed GLPI 10.0.12 and after connecting our ticketing office365 tenant mailbox via 0auth, I tried opening tickets via email with Hebrew characters and I get gibberish instead in the subject and the body.
When I open it manually on the platform there's no problem and Hebrew is shown fine.
Relevant log output
No response
Page URL
No response
Steps To reproduce
Your GLPI setup information
Information about system installation & configuration
Server
GLPI constants
Libraries
SQL replicas
Notifications
Plugins list
Anything else?
The text was updated successfully, but these errors were encountered: