We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
.env
./check-config.sh
docker-compose logs
docker-compose.override.yml
cfg/
When sending a utf-8 email it doesn't shows properly
Send "שלום עולם" (hebrew text) as the body of an email, You will see that it doesn't reproduces to the same text in the app.
It should show the email as it is.
It shows the text in gibrish
$ docker-compose up httpd bind mysql php redis
$ ./check-config.sh <<< REPLACE THIS LINE WITH OUTPUT FROM ABOVE COMMAND >>>
$ docker-compose logs <<< REPLACE THIS LINE WITH OUTPUT FROM ABOVE COMMAND >>>
It looks like PHP's base64_encode doesn't supports utf-8 text properly
base64_encode
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
ISSUE TYPE
Checklist
.env
file is attached./check-config.sh
output is added belowdocker-compose logs
output is added belowdocker-compose.override.yml
is attached (if exists)cfg/
dir are attached (if exist)OS / ENVIRONMENT
SUMMARY
When sending a utf-8 email it doesn't shows properly
STEPS TO REPRODUCE
Send "שלום עולם" (hebrew text) as the body of an email,

You will see that it doesn't reproduces to the same text in the app.
EXPECTED BEHAVIOUR
It should show the email as it is.
ACTUAL BEHAVIOUR
It shows the text in gibrish

OTHER INFORMATION
Start command
Outputs
It looks like PHP's
base64_encode
doesn't supports utf-8 text properlyThe text was updated successfully, but these errors were encountered: