Hi there,

thank you for moving my post to the right place, and sorry that I mixed it up. Does anyone have an idea what the reason of the mentioned log entries might be and if there is a solution to that?

Thanks in advance,
genesis74

@fbartels
FYI: the RewriteGALAddressesToSMTP dagent plugin does not seem to work anymore for KC 8.6.8

@Constin Give user2 access to the parent and make the parent visible only.

@mcostan Thanks, we’ll have a look.

@bhuisman
There is no cronjob or something like that running. Today 3 out of 10 of my problematic users had no signatures. If i restart my kopano server all 10 signatures are gone. May it correlates with the issue posted at the core section.
Whatever! I odered a subsription and if the issue is not away i will give some feedback.
Thank you.

@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).

@mcostan said:

I wonder if I am the only one experiencing this issue.

A colleague, reported comparable errors, recently.
He was sending simple text-mails via webapp - no attachments were involved.
I couldn’t reproduce it the day after with my account.

MAPIException: MAPI error in /usr/share/kopano-webapp/server/includes/core/class.operations.php:2732 Stack trace: #0 /usr/share/kopano-webapp/server/includes/core/class.operations.php(2732): mapi_message_submitmessage(Resource id #64) #1 /usr/share/kopano-webapp/server/includes/modules/class.createmailitemmodule.php(180): Operations->submitMessage(Resource id #53, x00x00x00x00xA7xCBxF20xF1xDECxFDx9AxC7x83..., Array, Array, Array, Array, false, false, false, false) #2 /usr/share/kopano-webapp/server/includes/modules/class.itemmodule.php(202): CreateMailItemModule->save(Resource id #53, x00x00x00x00xA7xCBxF20xF1xDECxFDx9AxC7x83..., x00x00x00x00xA7xCBxF20xF1xDECxFDx9AxC7x83..., Array) #3 /usr/share/kopano-webapp/server/includes/core/class.jsonrequest.php(57): ItemModule->execute() #4 /usr/share/kopano-webapp/kopano.php(139): JSONRequest->execute({"zarafa":{"cre...) #5 {main}

++umgfoin.

@mahescho That’s fixed in the upcoming 3.4.24
This already works in master

Sorry to hear that. You could also try to completely reset the WebApp settings.

kopano-tools-webapp_settings --user jdoe --remove

@eli
You can wait until someone adapt another wysiwyg editors like pell or summernote.
Some work for easy ingegration already done in Webapp 3.4.23.
Announcements: https://forum.kopano.io/topic/1835/webapp-3-4-23-final-available
https://forum.kopano.io/topic/1653/request-for-feedback-minimal-tinymce-implementation
Or You can integrate it by yourself.

Thank you!

@beme said in Mails not fully readble on iPad or iPhone:

Is it really so complicated to adapt the webapp to become usable on mobile devices

Sadly it is, the version of extjs used in WebApp does not allow this. We are working on some new web clients, that are fully responsive, though.

@taumeister

Hi

I think you may only be able to solve/get this by using thunderbird or another mailclient which has possibility for multible mailaccounts feature as webapp/deskapp are only able to have a single mailbox (and shared ones open)

as there is also an active sync addon for thunderbird, you’re also able to use notes,tasks and calendar with it

rg
christian

Hi @marty
thank yor for creating builds so fast. A real test run is not possible at the moment. The core components are still having unresolved dependencies and if i install your builds they suffer from that. If i ignore the missing dependencies everything works like “expected”.
There is already a ticket [KC-1304] for this bug.
I have to set up a new mail server in the near future. Before that i have to convince my boss Kopano is the right solution. At the moment just a few employees are working with the Kopano cummity packages on SLES12. The target system for the new mail server should be SLES15. Therefor i need a time line when stable/tested components will be available.

Blame QNAP. https://github.com/kisli/vmime/issues/173 . If you are not using the kopano.io builds, it comes down to your distribution if and when they update vmime.

Thank you, I will have a look

@ihon make sure to enable raw dumping of EML files in the dagent.

good to know - because I had no idea where else we can search

Hi @christian
You are correct this is a very old bug. I found ticket:
https://jira.kopano.io/browse/KW-18

Currently set to won’t do, but I’m checking if that’s still the case.