It only happens in chrome, in firefox it comes out normal

As per latest Firefox 111.0.1 this problem exists in Firefox too. Tested on Windows 10,11,Fedora37,Ubuntu22.04 with Edge,Firefox,Chrome,Chromium,Opera. This blank page drives me nuts..

P.s.: Outlook / Thunderbird printing is not affected.

Also SoGo Version 5.8.0 (@sogo-build.alinto.int 202303022257)

Problem is the use of the "page" css property, which Firefox supports only from version 110 (https://developer.mozilla.org/en-US/docs/Web/CSS/page). SOGo obviously uses this property to separate the emails in a useful way. From my point of view, the corresponding div (<div class="WordSection1">) should not be used to split the body of the email, but the entire email.

We have helped ourselves in this way https://www.sogo.nu/support/faq/how-to-change-the-color-theme.html and add the following CSS:
@media print {
.sg-block-print div.SOGoHTMLMail-CSS-Delimiter.mailer_htmlcontent div[class^="WordSection"] {
page: auto !important;
}
}

Hope it helps or Alinto improves the print. ;-)

Thanks @Rob, for the suggestion. We initially wanted to adopt it to relieve the SoGo team, but then realised that the change would not have survived the next update. As we also have to live with the nightly builds due to other changes (e.g. 0005490), we would have to make the change again with every update.

As per latest Firefox 115.4.0 this problem still exists (on Windows 10/11), we would be very grateful if the SoGo team could either
a) incorporate @Rob's suggestions into their standard CSS and then deliver them again with every update
or
b) create the possibility to add their own additions to the standard CSS in an update-proof manner.

Thank you and best regards,

the Bahnkonzept team form Dresden/Germany

Hi all,

Can you provide an eml of the problem ?

Sebastien

Hello,

the eml of an mail which shows the problem was sent to you?
A guess (if allowed): the problem seems to occur more often with HTML mails from Outlook.

Thank you and best regards,

the Bahnkonzept team from Dresden/Germany

Problem reproduced, added suggested fix in commit : https://github.com/Alinto/sogo/commit/e39c1044364d68df49ea6142072928d0b0e4c1eb (NB 20230312)

Sebastien