@gerald said in kopano-server crashes under load with build core-8.6.80.1350_0+212-Ubuntu_16.04-amd64:

May I bug you again about the daily builds @fbartels ?
No new builds since August 14th - 9 days ago…

An upgrade issue in packaging was blocking new releases.

The issue should be fixed and a new release will be available as soon as the release-pipeline is completed successfully. (Expect new packages within the hour.)

- Joost

Yes… I was able to start the kopano-server without any manual changes to the database
Thank you!

duplicate of https://forum.kopano.io/topic/1658/

WFM

> tar -tf core-8.6.81.24_0+4-RHEL_7_PHP_56-x86_64.tar.gz | grep python2- core-8.6.81.24_0+4-RHEL_7_PHP_56-x86_64/./python2-zarafa-8.6.81.24-4.1.x86_64.rpm core-8.6.81.24_0+4-RHEL_7_PHP_56-x86_64/./python2-kopano-8.6.81.24-4.1.x86_64.rpm core-8.6.81.24_0+4-RHEL_7_PHP_56-x86_64/./python2-mapi-8.6.81.24-4.1.x86_64.rpm

Well as Kopano4S (Synology) is based on Docker to use Debian images and init.d, so the consequences of Kopano to switch to systemd exclusively no longer shipping init scripts has significant impact. If you Google “systemd in docker container” you wil find out that this is far away from trivial task. I had Zarafa / Kopano in Docker Container running happily since 2016 shipped to a large community of Synology users. Now this is no longer shipped I have to use workarounds (currently use init files from 8.5 builds) . Please take this as feedback and xonside shipping init files at least to /usr/share/doc/…
-TosoBoso

I was able to reproduce it and made a ticket for it on https://jira.kopano.io/browse/KC-1243.

Wow, I did not even know there are examples for postfix to automatically resolve kopano users :-)

I’ve alway been using a manually editied textfile (compiled with postmap) which lists

name@domain.net name@domain.net
alias1@domain.net name@domain.net
(where name@domain.net is the “real” kopano email address)

And If i need mails to go to more than one person, i create
group@domain.net name1@domain.net,name2@domain.net,name3@domain.net

In my 8.6 no IMAP warnings

i finished now with the complex Manual way. The size is reduced from 79GB to 39GB. Its realy the half. Iam happy now.

Can anyone explain the @fbartels -way with “PR_EC_IMAP_* attributes” or the @mcostan -way with “python-kopano” in Detail?

Thanks

@tueftler17 I suppose you could achieve this in several ways, but a mailbox that can not be emailed to is not something you can do in Kopano.

So your approach with Postfix can work and is probably the best solution here, alternatively you could make a plugin for dagent or create a mail filter rule in the noreply mailbox that automatically deletes everything that comes in.

But as @tjoen mentions, if you are going to send email from that address you will not receive bounces (or you have to get those from the postfix log) - or you need to do some detection magic in your chosen approach.

Hi @tjoen ,

you would need to edit the first post, from there you should be able to edit the subject. alternatively there is a plugin installed here where you could mark your first post as a question and then select one of the replies as “the answer”

Just use kopano-admin, which, for years, has been showing digestible quota sizes already:

# kopano-admin --details foo ... Server version: 8.6.80 Mapped properties: 0x8C6D0102 48 bytes PR_GIVEN_NAME foo PR_SURNAME foo PR_EMS_AB_IS_MEMBER_OF_DL 1 values PR_EC_ENABLED_FEATURES imap; mobile; outlook; pop3; webapp PR_EC_DISABLED_FEATURES Current user store quota settings: Quota overrides: no Warning level: unlimited Soft level: unlimited Hard level: 1200.00 MB

Kopano itself will not modify LDAP; for this, an external tool needs to be used (and you likely already had one to add the user initially).

thx @jengelh @fbartels
it was the wrong package

The problem came from a corrupted backup via Sypexdumper.

Solution:

Create a backup wie mysqldump and get a backup.sql file. For example with this command:
mysqldump -u root -p zarafa > zarafabackup.sql

Move this file to your location my location was: /home/kopano/

For import into Kopano:
mysql -u root -p
CREATE DATABASE zarafa;
exit

Now you can start the import:
mysql --verbose -u kopanosql -p zarafa < /home/kopano/zarafabackup.sql

Yes it’s possible to migrate from ZCP 7.2.1-51838 to Kopano 8.6.80 - I have done it!

Thanks you can close this thread.

Hi @Coffee_is_life ,

since you have a subscription I would recommend getting in contact with our support on this.

thx @jengelh and I search and search …