HTML mail is displayed correct a few times and than it is displayed as text only message



  • Hello again,
    we have a mail which we received from a customer. It was correct displayed an then forwarded to an employee. The employee was able to edit the mail and added some comments in different colors. After that he sent the mail to 2 other employees. One could read everything correct colored but the other got no html mail displayed but a text only message without any formatting and colors. Today the other employee, which was first able to see the colors, opened the mail and it was displayed text only. :-(
    If you export the mail and open it in another mail client the colors are displayed.
    Html looks like:

    0_1541668781019_0deb64b7-a253-40bb-94bc-d1471b63a2ae-grafik.png

    Text looks like:

    0_1541668842503_15f29642-0b89-4480-b102-f04dcd355e47-grafik.png

    This issue occured on core 8.6.81.475, now we have 8.7.80.27.
    Webapp was 3.4.23.1788 and is now 3.4.24.1909.
    Deskapp is 1.9.7.


  • Kopano

    Hi @sturzhelmut ,

    that sounds like you are using Kopano in a business context. Maybe relying on the community build and community support isn’t the best idea, then. Have a look at https://kopano.com/support-info/ and https://kopano.com/pricing/ for our support options.



  • @fbartels Hello,
    yes you are right. We are using Kopano for business purposes. But that is the only test that works. We have some outlook users and they don’t want to loose their toy. I migrated some users to test Kopano (no outlook users) and i had no problems. I migrated some of my outlook users and i have nothing but trouble. So before buying something i wanted to test if the future users are able and willing to use Kopano.
    As i wrote in another post, i use SLES12 for Kopano at the moment. Because i am running some servers with different versions of SLES over many years I am familiar with that OS. To change OS is only the second choice.
    BUT: Since 1 or 2 months the nigthly builds for SLES 12 suffer from varius unresolved dependencies, especially for python3. So the question is if you are able/willing to resolve the dependencies for python3-bsddb3 for example or not. SLES 12 does not provide a stable version and i guess they won’t change that. So if you use more and more python3 it is not usefull to support a second version that works only with python2. That means SLES12 is supported no longer and dies!
    OPTION 2: I change my kopano server to SLES 15. Python3 should be no problem.
    BUT: SLES15 is at the moment not officially supported. Will it be official supported with next release?
    SLES15 comes with 389ds directory server. This is not supported by kopano at the moment. I use ldap for my users. Maybe i will get the kopano schema working with 389ds. But that is not supported, so questions or problems are not answered by the kopano support. :-)
    Could you please explain what plans you have for the SLES branch. It is urgent!!!
    If there is no answer i can not establish kopano and we have to search for another solution. That would be a pity.


  • Kopano

    You won’t have these dependency issues with the official release packages.

    The problem with SLES 15 is that there are no install images for LXC available for this distribution, and this is what we use for out test platform. Hence we could not yet start QA for SLES 15. Given the fact that SLES just makes a very small portion of our customers it simply wasn’t very high on the list until now.



  • OK. That makes sense. OPTION 2 is not an option at the moment. No problem.
    But what is with SLES12. Which version of kopano is actually provided within your commercial repositories?
    Do you provide the missing packages for python3 in future releases? As i understand python3 is a part of kopano which is becoming more and more important. But SLES12 does not provide some of your used python3 packages. How is this solved?
    Or is SLES12 developed without python3 and is missing some features in the future?
    Sorry for asking that persistant. It is no criticism, but i have to present a roadmap for my boss and calculate the hours for implementation.
    If you say there are no limitations in development of kopano for SLES12 in the next 12 months, i will ask no further questions about this theme. But it is allways a bad choice to present a new calculation after 2 or 3 months. After 12 months or more the old calculation is forgotten. :-))


  • Kopano

    @sturzhelmut said in HTML mail is displayed correct a few times and than it is displayed as text only message:

    Which version of kopano is actually provided within your commercial repositories?

    What you have been running until now are nightly snapshots of the master branch of our git repo. Before each nightly release there is only an automated testset to check if the current build is “good enough”. We branch our releases of the master branch and then do extensive testing to make sure Kopano runs just as well on all platforms that we officially support. Due to the branching the official releases are always older than the versions from the development system.

    @sturzhelmut said in HTML mail is displayed correct a few times and than it is displayed as text only message:

    Do you provide the missing packages for python3 in future releases?

    No, the goal is to adapt the packaging to still use the bundled python2 in SLES 12.

    @sturzhelmut said in HTML mail is displayed correct a few times and than it is displayed as text only message:

    Or is SLES12 developed without python3 and is missing some features in the future?

    Yes, for (optional) components that really require python3 this means that these components will not be available for SLES 12. For the moment this only concerns our rest api. (the same amounts for the too old python version in RHEL btw).


Log in to reply