HTML emails not displaying correctly after todays updates.

Mister2

I installed todays updates about an hour ago (using the GUI updater):-

`## This system : Grommunio.mydomain.com

Uptime : 2 days 14:20

Load : Last Minute: 0.15, Last 5 Minutes: 0.10, Last 15 Minutes: 0.09

IP Address : 192.168.50.36

Executed : /usr/sbin/grommunio-update check community

Start : Tue 2024-02-06 11:36:21 GMT

Operation : Check

[36m▶[0m Starting Check (zypper ref && zypper lu --allow-vendor-change)
Repository 'base' is up to date.
Repository 'debug' is up to date.
Repository 'debug-update' is up to date.
Retrieving repository 'grommunio' metadata [......done]
Building repository 'grommunio' cache [...done]
Retrieving repository 'repo-backports-update' metadata [..............done]
Building repository 'repo-backports-update' cache [....done]
Retrieving repository 'repo-sle-update' metadata [.....................................done]
Building repository 'repo-sle-update' cache [....done]
Repository 'update' is up to date.
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
S | Repository | Name | Current Version | Available Version | Arch
--+------------+--------------------+-----------------------------+----------------------------+-------
v | grommunio | grommunio-antispam | 3.8.1-lp155.2.1 | 3.8.1-lp155.3.1 | x86_64
v | grommunio | grommunio-cui | 1.0.263.dcebcfe-lp155.62.1 | 1.0.264.72a463a-lp155.64.1 | noarch
v | grommunio | gromox | 2.22.20.g2d2a29d-lp155.14.1 | 2.23.0.g3fa8b41-lp155.17.1 | x86_64
v | grommunio | gromox-debuginfo | 2.22.20.g2d2a29d-lp155.14.1 | 2.23.0.g3fa8b41-lp155.17.1 | x86_64
v | grommunio | gromox-debugsource | 2.22.20.g2d2a29d-lp155.14.1 | 2.23.0.g3fa8b41-lp155.17.1 | x86_64
[32m▶[0m Check completed successfully.
[36m▶[0m Updating postfix configuration with new maps if exist
[36m▶[0m Checking for pending service restart or reboot

End Check : Tue 2024-02-06 11:36:58 GMT`

Since the installation I am having issue with HTML email not formatting correctly in GR web and Mac Mail. Examples below:-

GR Web
Should look something like this (note picture is not same email as text below it):-

But instead I get this:-

`Quarantined email for user@domain.com

Hello,
Here is a summary of emails that were quarantined from your INBOX on
06-Feb-2024. These emails will be kept on the server for 30 days. To receive
any of these messages, click Restore.

                                                          Message Count

                        Total Emails Processed:                 18

[cid] Total Spam Messages: 6

                        Total Good Messages:                    12

                        Total Possible Spam:                    0

Displaying messages received after 06/02/24 00:09

       From                           Subject                Score Action

Carwow - sell my car There’s £959 sat on your driveway… 283 Restore
hello@t.carwow.co.uk
120/80 BP To reach 120/80 BP, follow these 340 Restore
fact@beginslim.best steps at home.
Customer feedback We have a surprise for Screwfix 388 Restore
services@ional.co.uk customers.
Kelly Walker This physically wipes 1% of your 400 Restore
helpdesk@bidmere.best memories every mo ...
Joanna Ryan 60-Second Ritual For 30 Minutes of 454 Restore
info@beerloss.best Pleasure
Unlock the Secret Just 10 Seconds a Day for Effortless 454 Restore
support@cellsir.best Weight Loss!
------=_NextPart_001_0006_39DAB01E.A60A5F4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset="utf-8"

<html>
<head>
<style type=3D"text/css">
=09P {
=09=09font-family: Tahoma, Arial, Verdana;
=09=09font-size: 11px;
=09=09color: black;
=09}
=09H1 {}
=09H2 {}
=09H3 {}
=09A {}
=09A:Visited {}
=09A:Active {}
=09A:Hover {}
=09BODY {
=09=09font-family: Tahoma, Arial, Verdana;
=09=09font-size: 11px;
=09=09color: black;
=09}
table {=20
=09font-family: Tahoma, Arial, Verdana;
=09font-size: 11px;
=09color: black;
=09}

</style>

</head>
<body>

<img src=3D"cid:part2.top.graph"><br>
<table width=3D"100%">
<tr bgcolor=3D"#2c5f7e">
<td align=3D"left">
<font color=3D"White" size=3D"+1">Quarantined email for caroline@the-seym=
ours.co.uk</font>
</td>
</tr>
</table>

Hello,<br>
Here is a summary of emails that were quarantined from your INBOX on 06-F=
eb-2024. These emails
will be kept on the server for 30 days. To receive any of these messages,=
click Restore.
<p>

<table border=3D"0" cellpadding=3D"0" cellspacing=3D"5" width=3D"100%">
<th> </th>
<th><u>Message Count</u></th>

<tr>
<td><b>Total Emails Processed:</b></td><td align=3D"center">18</td>
</tr>

<tr>
<td><b>Total Spam Messages:</b></td><td align=3D"center">6</td>
</tr>

<tr>
<td><b>Total Good Messages:</b></td><td align=3D"center">12</td>
</tr>

<tr>
<td><b>Total Possible Spam:</b></td><td align=3D"center">0</td>
</tr>
</table>

</td>
</tr>
</table>

</p>

<div>
Displaying messages received after <b>06/02/24 00:09</b>
</div>
<br>
<br>
<table width=3D"100%" border=3D"0" cellpadding=3D"0">
<th bgcolor=3D"#5A79A5"><font color=3D"White">From</font></th>
<th bgcolor=3D"#5A79A5"><font color=3D"White">Subject</font></th>
<th bgcolor=3D"#5A79A5"><font color=3D"White">Score</font></th>
<th bgcolor=3D"#5A79A5"><font color=3D"White">Action</font></th>

<tr bgcolor=3D"White">
<td>Carwow - sell my car <hello@t.carwow.co.uk></td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Duvu&f=3D00001_283_20240206_6168292.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXNl=
eW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">There’s £959 sat on y=
our driveway…</a> </td>
<td>283</td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Dures&f=3D00001_283_20240206_6168292.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXN=
leW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">Restore</a> </td>
</tr>
<tr bgcolor=3D"#DDDDDD">
<td>120/80 BP <fact@beginslim.best></td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Duvu&f=3D00001_340_20240206_6168253.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXNl=
eW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">To reach 120/80 BP, foll=
ow these steps at home.</a> </td>
<td>340</td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Dures&f=3D00001_340_20240206_6168253.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXN=
leW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">Restore</a> </td>
</tr>
<tr bgcolor=3D"White">
<td>Customer feedback <services@ional.co.uk></td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Duvu&f=3D00001_388_20240206_6168220.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXNl=
eW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">We have a surprise for Screwfix =
customers.</a> </td>
<td>388</td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Dures&f=3D00001_388_20240206_6168220.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXN=
leW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">Restore</a> </td>
</tr>
<tr bgcolor=3D"#DDDDDD">
<td> Kelly Walker <helpdesk@bidmere.best></td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Duvu&f=3D00001_400_20240206_6168262.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXNl=
eW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">This physically wipes 1% of =
your memories every mo ...</a> </td>
<td>400</td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Dures&f=3D00001_400_20240206_6168262.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXN=
leW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">Restore</a> </td>
</tr>
<tr bgcolor=3D"White">
<td> Joanna Ryan <info@beerloss.best></td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Duvu&f=3D00001_454_20240206_6168239.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXNl=
eW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">60-Second Ritual For 30 Minu=
tes of Pleasure</a> </td>
<td>454</td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Dures&f=3D00001_454_20240206_6168239.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXN=
leW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">Restore</a> </td>
</tr>
<tr bgcolor=3D"#DDDDDD">
<td>Unlock the Secret <support@cellsir.best></td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Duvu&f=3D00001_454_20240206_6168270.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXNl=
eW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">Just 10 Seconds a Day for Effort=
less Weight Loss!</a> </td>
<td>454</td>
<td><a href=3D"https://mta.domain.com/FrontController?operation=
=3Dures&f=3D00001_454_20240206_6168270.eml&ws=3D1&e=3DY2Fyb2xpbmVAdGhlLXN=
leW1vdXJzLmNvLnVr&p=3D%7EsUTDMGH&pid=3D1">Restore</a> </td>
</tr>

</table>

</body>
</html>
=0D=00------=_NextPart_001_0006_39DAB01E.A60A5F4--`

This is happening to ALL emails in Mac Mail, but only HTML emails in GR Web. If I revert to a snapshot before the updates were applied the issue does not exist.

EDIT: Apologies for the strange font sizes at the start all looked OK when creating post and this is what showed up when posted.

Mister2

Just been checking emails in both Mac Mail and Gr Web received before I installed the updates above, and they are all displaying correctly so something has gone wrong in the updates in how newly received HTML emails are being decoded/displayed.

Have these error in http log in Admin GUI/Monitoring

[2024-02-06 13:37:23.188217]: ews: no conversion for Message::Subject [2024-02-06 13:37:23.188957]: ews: no conversion for Message::Body [2024-02-06 13:37:23.425520]: ews: no conversion for Message::Subject [2024-02-06 13:37:23.425768]: ews: no conversion for Message::Body [2024-02-06 13:37:23.642698]: ews: no conversion for Message::Subject [2024-02-06 13:37:23.643089]: ews: no conversion for Message::Body

Plus lots more for each incoming email.

mjmabs

Have applied the same update on supported repositories instead and am now have the same issue as above with html formatted emails being treated as text. Add Android and Apple IOS devices to the list.

WalterH

mjmabs
Did you follow the correct update / downdate procedure?

zypper ref -f
zypper dup

mjmabs

WalterH

Been using the console / web admin procedure to check for updates, update, upgrade options for both servers. Just tried your commands and got back on both

mail:~ # zypper ref -f
Forcing raw metadata refresh
Retrieving repository 'base' metadata ....................................[done]
Forcing building of repository cache
Building repository 'base' cache .........................................[done]
Forcing raw metadata refresh
Retrieving repository 'debug' metadata ...................................[done]
Forcing building of repository cache
Building repository 'debug' cache ........................................[done]
Forcing raw metadata refresh
Retrieving repository 'debug-update' metadata ............................[done]
Forcing building of repository cache
Building repository 'debug-update' cache .................................[done]
Forcing raw metadata refresh
Retrieving repository 'grommunio' metadata ...............................[done]
Forcing building of repository cache
Building repository 'grommunio' cache ....................................[done]
Forcing raw metadata refresh
Retrieving repository 'repo-backports-update' metadata ...................[done]
Forcing building of repository cache
Building repository 'repo-backports-update' cache ........................[done]
Forcing raw metadata refresh
Retrieving repository 'repo-sle-update' metadata .........................[done]
Forcing building of repository cache
Building repository 'repo-sle-update' cache ..............................[done]
Forcing raw metadata refresh
Retrieving repository 'update' metadata ..................................[done]
Forcing building of repository cache
Building repository 'update' cache .......................................[done]
All repositories have been refreshed.
mail:~ # zypper dup
Loading repository data...
Warning: Repository 'debug-update' metadata expired since 2024-02-07 01:24:06 PST.
Warning: Repository 'update' metadata expired since 2024-02-07 01:23:56 PST.

Warning: Repository metadata expired: Check if 'autorefresh' is turned on
(zypper lr), otherwise manually refresh the repository (zypper ref). If this
does not solve the issue, it could be that you are using a broken mirror or
the server has actually discontinued to support the repository.

Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
Nothing to do.
mail:~ #

Mister2

WalterH Yesterday I used the Admin GUI update method, so have just booted my now (sort of) broken VM and run updates as you asked. Output of commands below:-

`Grommunio_Server:~ # zypper ref -f
Forcing raw metadata refresh
Retrieving repository 'base' metadata ....................................[done]
Forcing building of repository cache
Building repository 'base' cache .........................................[done]
Forcing raw metadata refresh
Retrieving repository 'debug' metadata ...................................[done]
Forcing building of repository cache
Building repository 'debug' cache ........................................[done]
Forcing raw metadata refresh
Retrieving repository 'debug-update' metadata ............................[done]
Forcing building of repository cache
Building repository 'debug-update' cache .................................[done]
Forcing raw metadata refresh
Retrieving repository 'grommunio' metadata ...............................[done]
Forcing building of repository cache
Building repository 'grommunio' cache ....................................[done]
Forcing raw metadata refresh
Retrieving repository 'repo-backports-update' metadata ...................[done]
Forcing building of repository cache
Building repository 'repo-backports-update' cache ........................[done]
Forcing raw metadata refresh
Retrieving repository 'repo-sle-update' metadata .........................[done]
Forcing building of repository cache
Building repository 'repo-sle-update' cache ..............................[done]
Forcing raw metadata refresh
Retrieving repository 'update' metadata ..................................[done]
Forcing building of repository cache
Building repository 'update' cache .......................................[done]
All repositories have been refreshed.

Grommunio_Server:~ # zypper dup
Loading repository data...
Warning: Repository 'debug-update' metadata expired since 2024-02-07 09:24:06 GMT.
Warning: Repository 'update' metadata expired since 2024-02-07 09:23:56 GMT.

Warning: Repository metadata expired: Check if 'autorefresh' is turned on
(zypper lr), otherwise manually refresh the repository (zypper ref). If this
does not solve the issue, it could be that you are using a broken mirror or
the server has actually discontinued to support the repository.

So no updates available this morning. Issue still present. Reboots also do not help. However, a repeat of an issue you ( @WalterH) reported 27/05/23 with expired repositories has re-occurred - see warnings in output above. @crpb reported last year that is OK to overlook these Warnings as they seem to go away after a day or so. My research suggests this is a standard warning with OpenSuse when a repository hasn't had any updates for 30 days or more.

I am using the Community repositories, so issue seems to exist in both Community and Supported repositories (see @mjmabs above).

Guess we wait for an update to fix this issue?

WalterH

You should see 3 files in: /etc/zypp/repos.d/

# ls -la /etc/zypp/repos.d/
total 16
drwxr-xr-x 1 root root 104 Feb  7 14:46 ./
drwxr-xr-x 1 root root 250 Nov 10 20:22 ../
-rw-r--r-- 1 root root 473 Dec 27 19:35 base.repo
-rw-r--r-- 1 root root 671 Dec 27 13:23 grommunio-base.repo
-rw-r--r-- 1 root root 286 Feb  2 07:59 grommunio.repo

If you have more repository files, move them to a save place ant try again.

A zypper lrschould show a similar output:

 # zypper lr
Repository priorities are without effect. All enabled repositories share the same priority.

#  | Alias                       | Name                        | Enabled | GPG Check | Refresh
---+-----------------------------+-----------------------------+---------+-----------+--------
 1 | base                        | base                        | Yes     | (r ) Yes  | Yes
 2 | debug                       | debug                       | Yes     | (r ) Yes  | No
 3 | debug-update                | debug-update                | Yes     | (r ) Yes  | No
 4 | grommunio                   | grommunio                   | Yes     | (r ) Yes  | Yes
 5 | repo-backports-debug-update | repo-backports-debug-update | No      | ----      | ----
 6 | repo-backports-update       | repo-backports-update       | Yes     | (r ) Yes  | Yes
 7 | repo-sle-debug-update       | repo-sle-debug-update       | No      | ----      | ----
 8 | repo-sle-update             | repo-sle-update             | Yes     | (r ) Yes  | Yes
 9 | update                      | update                      | Yes     | (r ) Yes  | Yes

Mister2

WalterH I checked the zypper lr earlier and have the same results as you posted above:-

zypper lr

Also ls -la /etc/zypp/repos.d/ produced similar output to yours above:-

WalterH

Mister2 Can you restest with:

zypper ref -f
zypper dup

On 3 systems, I do not see the metadataexpired message. I assume there was a repository update im progress.

Mister2

WalterH As requested:-

Grommunio_Server:~ # zypper ref -f
Forcing raw metadata refresh
Retrieving repository 'base' metadata ....................................[done]
Forcing building of repository cache
Building repository 'base' cache .........................................[done]
Forcing raw metadata refresh
Retrieving repository 'debug' metadata ...................................[done]
Forcing building of repository cache
Building repository 'debug' cache ........................................[done]
Forcing raw metadata refresh
Retrieving repository 'debug-update' metadata ............................[done]
Forcing building of repository cache
Building repository 'debug-update' cache .................................[done]
Forcing raw metadata refresh
Retrieving repository 'grommunio' metadata ...............................[done]
Forcing building of repository cache
Building repository 'grommunio' cache ....................................[done]
Forcing raw metadata refresh
Retrieving repository 'repo-backports-update' metadata ...................[done]
Forcing building of repository cache
Building repository 'repo-backports-update' cache ........................[done]
Forcing raw metadata refresh
Retrieving repository 'repo-sle-update' metadata .........................[done]
Forcing building of repository cache
Building repository 'repo-sle-update' cache ..............................[done]
Forcing raw metadata refresh
Retrieving repository 'update' metadata ..................................[done]
Forcing building of repository cache
Building repository 'update' cache .......................................[done]
All repositories have been refreshed.
Grommunio_Server:~ # zypper dup
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
Nothing to do.

Looks like the affected repositories mentioned earlier have been updated (ie no longer expired) since my earlier post at 12:11.

I still have the issue with html emails not displaying correctly in Mac mail and Gr web. As no updates have been posted today I assume this is still under investigation. I reverted my 'Live' server back to a VM snapshot taken prior to yesterday's update, so messages are properly displayed as HTML not plain TEXT.

mjmabs

@WalterH

Also did the same on the supported repositories and it corrected the issue with the repository out of date but didn't produce any update/patches to the mobile client (exchange style) html bug.

mjmabs

This has now expanded from mobile clients only affected to all incoming/outgoing attachments cannot be opened due to file is likely corrupted. When you attempt to open an xls file it is treated as a csv file instead.

Keeebs

Same issue here, but it's occurring on all external html formatted email sent. Email replied to will also appear the same way as it was on the original email sent/delivered before it was replied to. New html email received in Grommunio from others do not appear to have this problem. I do not see this occurring with email sent internally. It's occurring when email is sent externally. Sending client does not appear to change the result - I've tested the webclient and Outlook 365 for Windows.

dougi

Keeebs
Same issue here, but it's occurring on all external html formatted email sent.

The first customer asked me to send him his documents by post - this leads to additional costs and makes me very unhappy.

mjmabs

Just saw an update for the following packages and applied but no change to email issue

Example of Mobile Email

Thanks,
Michael Miller
VP of Operations
Assorted Business Services
------=_NextPart_000_0005_533A967A.BCDBF94
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset="utf-8"

<pre>

Thanks,
Michael Miller
VP of Operations
Assorted Business Services
</pre>
</body>
</html>------=_NextPart_000_0005_533A967A.BCDBF94--

Example of Gro Web Email
test

------=_NextPart_000_0005_56841F24.A30BE63
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset="utf-8"

<!DOCTYPE html><html>
<head>
<meta name="Generator" content="grommunio-web v3.6.18.12b5ccdd-lp155.16.5">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>test-web</title>
</head>
<body>
<p style="padding: 0; margin: 0;"><span style="font-size: 11pt; font-family: tahoma, arial, helvetica, sans-serif;">test<br /></span></p>
</body>
</html>------=_NextPart_000_0005_56841F24.A30BE63--

Mister2

@mwilliams As this issue now appears to be spreading and affecting both Community and Supported Users, can this ticket thread be changed to 'bug', as the issue occurred with the updates released on 6/2/24 and more users are reporting the same issue. I have only seen it on incoming emails, but then I send very few emails, and have reverted to a VM snapshot prior to the updates that appear to have introduced the problem.

Do you know if the DEV's are looking into this issue (also reported at the end of 'Endlosschleife beim Start des "Grommunio Console User Interface" nach Update' thread - after your Solved entry) as it seems to be happening to outbound emails as well.

mjmabs

If you are using an Microsoft Outlook client you can temporary overcome part of the problem by going to Options > Mail > Compose messages in this format: change HTML to Plain Text. This allows new messages, forward, or replies to go out without the extra data but would have no effect on incoming email.

@mwilliams @WalterH check Ticket #811692 also sent an email direct to dev@ about this is issue yesterday containing samples of issue.

mjmabs

Have not heard anything today but saw another update for python3-argcomplete and supportutils pop-up but again no fix for html issue.

mjmabs

If you have access to Supported Repositories and did preform the admin-cui update, go back in from the console and check "Select Software Repositories" to see if your supported credentials are selected/entered. As it turns out all 3 of my systems were set back to community support. Then from terminal run zypper ref -f and zypper dup it will pickup the supported files and after a reboot issue clears.

Support did confirm they are seeing the issue in the Community repositories and are working to identify issue.

Keeebs

Thanks for the update! I'm evaluating grommunio so I don't have support yet. It's making my evaluation liok bad though....