Some code was made. It is published in
https://stash.kopano.io/users/jengelhardt/repos/kc/browse?at=refs%2Fheads%2Fkc-1657
This is not in master yet, and if the Kopano community stance doesn’t improve, probably won’t ever.

Hi @ana-u,

@ana-u said in Possible Memmory leak:

version 8.7.1

this version is already quite old. can you upgrade to the latest version (customers in UCS can add credentials for our download repository from the app settings) and check if the error persists?

@marty Haven’t seen the message since disabling this feature.

The message was related to the other stores.

The fix to support build with Python 3.8 has been merged. See https://github.com/Kopano-dev/kopano-core/commit/00669f113dfb77909878cae06f0f6082c973f1b0 for details.

@boospy said in Can't import contacts with import_rfc.py:

Traceback (most recent call last):
File “/usr/local/bin/import_rfc.py”, line 14, in <module>
server = kopano.server(options, parse_args=True)
TypeError: ‘module’ object is not callable

This error statement TypeError: ‘module’ object is not callable is raised as you are being confused about the Class name and Module name. The problem is in the import line . You are importing a module, not a class. This happend because the module name and class name have the same name .

If you have a class MyClass in a file called MyClass.py , then you should write:

from MyClass import MyClass

Hi @t-wirmer,

you can see currently running queries when executing show full processlist; on the mysql console. Current session within kopano-server when calling kopano-stats --top.

ok, solved. Works like a charm now …

THX walterhof for help

it’s been solved.

By the way, it is nearly impossible to install it on RHEL 7 (with epel):

Does anybody know, if theese issues also happen in the commercial verison?
Or is there any roadmap when it is fixed in the community edition (I know that there is no priority a the moment)

this one

MariaDB [kopano]> SELECT * FROM objectproperty; +----------+-----------+---------------------+ | objectid | propname | value | +----------+-----------+---------------------+ | 1 | groupname | everyone | | 1 | ishidden | 0 | | 1 | modtime | 2020-01-15 20:53:03 | +----------+-----------+---------------------+

no, I would not think so. both operations should only read data and that should really not cause inconsistencies, Overall it sounds like you either have a faulty disk or maybe faulty ram?

Hi @ckruijntjens,

unfortunately when the there is no attachment to an email after a restore, it means that the attachment was not included in the backup.

Dear all,

I know, that the topic is old. But I’ve had a simular problem and the info from @robgnu with the /etc/postfix/transport.mysql solved my problem.

And if someone else has a simular problem as well, maybe this info can help.

First of all my system: I installed kopano on a debian-10. I also installed fetchmail. I created user with mailaddress from my internal domain name eg: user1@mydomain.local and user2@mydomain.local
and some user with external mailaddress eg: user3@mydomain.de and also user4@gmx.de

For the internal user it works but for the user with external mailaddress fetchmail couldn’t deliver mails.
I tried fetchmail with kopano-dagent and without but no success.
Then I tried the mentioned tipp with transport.mysql - and it works !
I have to enter the external mailaddress in my /etc/postfix/virtual - but then it works.
And for me, it works better than expected, then: if I send a mail from user1@mydomain.local to user4@gmx.de the mail stays intern.
That it what I wanted !

I just want to describe it, if it someone else can help.

Best regards