@flobian
The solution was a complete reboot of my CentOS7 machine
I dont know what happend or why, but since the reboot the error was gone.

Further i dont know if your error is comparable to what is mentioned above.
whats the exact error your kopano-search.log?

best regards,
coffee_is_life

@junglemarc if you manage your users with kopano-admin, then you would also manage send-as with kopano-admin.

@fbartels amazing. :)

+1

@cbnidk said in update of nightly builds:

hi
The nightly builds of core is from 14-08-2021, will this be update sometime

Claus

@cpzengel see

https://forum.kopano.io/topic/3810/upgrade-core-11-0-1-2-to-11-0-2-41-high-search-cpu-usage
it include a fix for it that forum link.

Same Problem here!!!
How to handle?

MariaDB [(none)]> SHOW PROCESSLIST;
±-----±-------------±----------±-------±--------±-----±-------------±-----------------------------------------------------------------------------------------------------±---------+
| Id | User | Host | db | Command | Time | State | Info | Progress |
±-----±-------------±----------±-------±--------±-----±-------------±-----------------------------------------------------------------------------------------------------±---------+
| 1072 | kopanoDbUser | localhost | kopano | Query | 5394 | Sending data | DELETE syncedmessages.* FROM syncedmessages LEFT JOIN syncs ON syncs.id = syncedmessages.sync_id WHE | 0.000 |
| 1366 | root | localhost | NULL | Query | 0 | init | SHOW PROCESSLIST | 0.000 |
±-----±-------------±----------±-------±--------±-----±-------------±-----------------------------------------------------------------------------------------------------±---------+

Hi @nfaction,

maybe I need to phrase it a bit differently:

to be able to send mails from the Kopano clients (WebApp, ActiveSync clients) nothing need to be changed in the configuration of kopano-spooler or the kopano_spooler container if you want to change configuration in the mail container, then I suggest to check their docs (you already linked to https://docker-mailserver.github.io/docker-mailserver/edge/config/security/understanding-the-ports/) and ask in their project if you encounter any issues sending mail for example through Thunderbird. In my eyes this is out of the scope of the kopano-docker project, but should be possible to achieve through configuration nonetheless. running a second instance of docker-mailserver is not necessary

PS: why did you delete your topic regarding the use of linuxserver.io swag?

Hey tiredofit,

so easy \o/…
Thanks for the hint.

SOLVED.
Icey

@morta No, its not needed to change anything in that line.

If mysql is installed i used it and it skips services not installed.
This way, if you change from mysql to mariadb ,you dont need to change you start upservices.

Hi @mpraunegger,

the simple solution to this would be creating a calendar in the public for this and have either each employee or hr add appointments for the birthdays to it. I have been told however in the past that these kind of calendars are difficult from a data privacy point, laws may differ where you are.

You will not get reminders for it however, since this only works for calendars in your own store.

@thctlo said in Ubuntu 20.04 depend problems:

the “debian” build folder

Since we are using OBS to build packages for all distributions its sadly not that easy. Thanks for the offer, though.

short update:

I found a nice script to modify WebApp attributes here:
https://forum.kopano.io/topic/567/php-script-to-manage-webapp-settings

Question: I there a list with all WebApp atributes to modify?

Hi @Morta,

@morta said in Kopano Core on Arch Linux:

So can someone from the team adjust the script?

The Archlinux packages are not an official or supported product of the Kopano team itself. Instead a volunteer in the Archlinux community is providing them. I have seen you are already in contact with @martimcfly, who is maintaining these.

@walterhof
i don’t why, but the backup job was finished after 4 hours. If it remains so, everything is fine again.
Best regards
Andre

‘lo’ means localhost - it’s probably binding and only accepting connections to 127.0.0.1 - You can verify by looking at the output of netstat -tunap and see what address :143 is bound to.