Font issue after upgrade to 3.0.1.9
Font issue after upgrade to 3.0.1.9
Hi,
After upgrade to 3.0.1.9 all email with Vietnamese have issue with font.
Our appliance info :
Do you have any way to fix this ?
After upgrade to 3.0.1.9 all email with Vietnamese have issue with font.
Our appliance info :
Do you have any way to fix this ?
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Font issue after upgrade to 3.0.1.9
Which version were you on previously? I would like to bring this to MailWatch's attention.
Re: Font issue after upgrade to 3.0.1.9
I had upgraded from 3.0.1.8
Re: Font issue after upgrade to 3.0.1.9
Same problem with E.F.A. 3.0.1.9 with Lithuania chars after upgrade from 3.0.1.8 .
---
Ramas
---
Ramas
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Font issue after upgrade to 3.0.1.9
Thanks for feedback, I'm going to link open an issue with MailWatch.
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Font issue after upgrade to 3.0.1.9
Is php-mbstring installed on your systems?
Re: Font issue after upgrade to 3.0.1.9
Yes:
Code: Select all
sudo rpm -qa | grep mbstring
php-mbstring-5.3.3-48.el6_8.x86_64
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Font issue after upgrade to 3.0.1.9
I think this issue is still in MailWatch, but please update to 3.0.2.0 and confirm that issue is still present.
Re: Font issue after upgrade to 3.0.1.9
Hi,shawniverson wrote: ↑09 Apr 2017 16:27 I think this issue is still in MailWatch, but please update to 3.0.2.0 and confirm that issue is still present.
updated to 3.0.2.0. Update went smooth, but font problem persists in status page.
Aggree, issue in MailWatch.
Interesting that in message detail when showing message headers i see correct fonts, but subject line like in wrong encoded font:
---
Ramas
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Font issue after upgrade to 3.0.1.9
It's an issue in 3.0.2.1 as well.
Are there any quick fixes, or am I going to have to dig through the mailscanner code to find out what they broke?
Are there any quick fixes, or am I going to have to dig through the mailscanner code to find out what they broke?
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Font issue after upgrade to 3.0.1.9
Please reply "me too" to this issue here.
https://github.com/mailwatch/MailWatch/issues/742
I haven't had much time to dig deeper yet, but I'm sure if others raise issue, it may get more attention.
https://github.com/mailwatch/MailWatch/issues/742
I haven't had much time to dig deeper yet, but I'm sure if others raise issue, it may get more attention.
Re: Font issue after upgrade to 3.0.1.9
done.
I'll try to debug it when I have a free moment and post the results to that thread.
I'll try to debug it when I have a free moment and post the results to that thread.
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Font issue after upgrade to 3.0.1.9
Posting this info over here and going to include fix in 3.0.2.2 release for all. Many thanks to pdwalker for taking the time to dig into this issue.
In /etc/my.cnf.d/server.cnf (edited), need to have:
In /etc/my.cnf.d/server.cnf (edited), need to have:
Code: Select all
collation-server = utf8mb4_unicode_ci
init-connect='SET NAMES utf8mb4'
character-set-server = utf8mb4
Re: Font issue after upgrade to 3.0.1.9
Crap. You beat me posting this. I got caught up in reading old threads.
Oh well.
Oh! Restart the mysql server afterwards so the system will pick up the change.
(Ha! forgot that shawniverson! )
[edit:] the file is specifically /etc/my.cnf.d/server.cnf and the location is just after the [mysqld] section.
(ha! forgot that pdwalker!)
Oh well.
Oh! Restart the mysql server afterwards so the system will pick up the change.
(Ha! forgot that shawniverson! )
[edit:] the file is specifically /etc/my.cnf.d/server.cnf and the location is just after the [mysqld] section.
(ha! forgot that pdwalker!)
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Font issue after upgrade to 3.0.1.9
For what it is worth, everything renders correctly now.
Before, I would sometimes have some chinese characters not render correctly. The move to utf8mb4 must have done the trick.
Before, I would sometimes have some chinese characters not render correctly. The move to utf8mb4 must have done the trick.
Re: Font issue after upgrade to 3.0.1.9
Great !!!
Add those setting fixed the issue.
Thank you all.
Add those setting fixed the issue.
Thank you all.
Re: Font issue after upgrade to 3.0.1.9
Hi,
agree, those setting fixed the issue, but not all.
status.php correct:
detail.php correct:
In viewmail.php issue still exists:
---
Ramas
agree, those setting fixed the issue, but not all.
status.php correct:
detail.php correct:
In viewmail.php issue still exists:
---
Ramas
- shawniverson
- Posts: 3644
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Font issue after upgrade to 3.0.1.9
That is progress, at least
I will run some tests with viewmail.php and see if we can resolve.
I will run some tests with viewmail.php and see if we can resolve.
Re: Font issue after upgrade to 3.0.1.9
Ramas,
Can you provide the raw headers to that email, like I did in https://github.com/mailwatch/MailWatch/issues/742 (3rd comment down).
It will make the debugging a bit easier.
Or, you can follow what I did in that comment thread and see if your headers are being stored correctly?
Can you provide the raw headers to that email, like I did in https://github.com/mailwatch/MailWatch/issues/742 (3rd comment down).
It will make the debugging a bit easier.
Or, you can follow what I did in that comment thread and see if your headers are being stored correctly?
Re: Font issue after upgrade to 3.0.1.9
Sure:pdwalker wrote: ↑02 May 2017 02:27 Ramas,
Can you provide the raw headers to that email, like I did in https://github.com/mailwatch/MailWatch/issues/742 (3rd comment down).
It will make the debugging a bit easier.
Code: Select all
Received: from mail.manoteo.lt (mail.manoteo.lt [82.135.235.4])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mail.********.lt (Postfix) with ESMTPS id 96C49A00A0
for <******.*************@******.lt>; Mon, 1 May 2017 16:36:40 +0300 (EEST)
Received: from SRCOMPROD2 (unknown [172.16.92.156])
by mail.manoteo.lt (Postfix) with ESMTP id 7FAE2329B
for <******.*************@******.lt>; Mon, 1 May 2017 16:36:39 +0300 (EEST)
MIME-Version: 1.0
From: "Telia" <noreply@telia.lt>
To: ******.*************@******.lt
Date: 1 May 2017 16:36:39 +0300
Subject: =?utf-8?B?UHJhbmXFoWltYXMgYXBpZSB0aW5rbG8gcGzEl3Ryb3MgZGFy?=
=?utf-8?B?YnVz?=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
Message-Id: <20170501133639.7FAE2329B@mail.manoteo.lt>
Code: Select all
MariaDB [mailscanner]> show create database mailscanner;
+-------------+----------------------------------------------------------------------------------------------------+
| Database | Create Database |
+-------------+----------------------------------------------------------------------------------------------------+
| mailscanner | CREATE DATABASE `mailscanner` /*!40100 DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci */ |
+-------------+----------------------------------------------------------------------------------------------------+
Code: Select all
...
ENGINE=InnoDB AUTO_INCREMENT=73506 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci
...
Thats all my tests. I that Subject line in database is stored correctly.
---
Ramas
Re: Font issue after upgrade to 3.0.1.9
will test and get back to you.
Re: Font issue after upgrade to 3.0.1.9
Verified. Problem is in viewmail.php. Debugging.
Re: Font issue after upgrade to 3.0.1.9
definitely a problem in viewmail.php.
raised a bug report in the mailscanner project for this:
https://github.com/mailwatch/MailWatch/issues/773
It should be a simple fix.
raised a bug report in the mailscanner project for this:
https://github.com/mailwatch/MailWatch/issues/773
It should be a simple fix.