Thats weird. Other services should have service units as well.

thanks for the info, @markb

@jengelh said in Update Issue II:

@fbartels said in Update Issue II:

we lowered the version number the next day, but those builds were online for a day or so.

We did? Where?

fbartels is probably the right person for this question.
You should know him.
closed

Finaly with 8.5 it works well :)

but I see every line twice - something i can change to only have single line entries ?
this does not realy hurt but would be interesting why it is as it is :)

0_1518306996421_825da0c4-8c91-44ce-bfb4-2d7b67be9e59-grafik.png

rg
Christian

Hej Felix.

Thank you

Hi @fbartels,

thanks for the pointer. the solution with kopano-backup backup works fine!

Hi!

I just found the problem:
Most of my users are using “german” folder names. “Gelöschte Objekte” seems to break the line:
print ‘Deleted %s item(s) for user ‘%s’ in folder ‘%s’’ % (count, user.name, folder.name)

If I just remove the “folder-info”, the scripts can run:

print ‘Deleted %s item(s) for user ‘%s’ in folder Wastebin’ % (count, user.name)

Stril

@jj458 said in [centos7] installation dependency problem: missing libjsoncpp.so.19()(64bit):

Thank you for solving.
core-8.5.81.224_0+29-RHEL_7-x86_64 is installed successfully in my Centos7 system.

-Joachim

I initially had looked at the jsoncpp commits. Using git log -p to show all of them, I looked at the last occurrence of “StreamWriterBuilder”, and that turned up in 5fbfe3cdb948a32706ad88635563a41a54819f83, which, when fed to git describe --contains 5fbfe3, gives “1.4.0~20”, so 1.4.0 is the first tag to have SWB.

Checking this again just now, I notice that the SCM history is bonkers – “0.8.0” is a child of “1.4.0”. Which means I cannot request “jsoncpp >= 0.8.0”, because that would satisfy 1.0.0 too, and 1.0.0 is known not to have SWB. What a mess!

Thanks @fbartels
I tried this now and it’s working again

Hi @hawkan ,

thanks for reporting this. It seems this is caused by a faulty vmime built (a few more details in https://jira.kopano.io/browse/KC-1027). This will be fixed with the next packages upload.

Thank you very much!

The script did not report any errors. It turned out that one of the mailboxes lost the mails due to an user error.

Basically - the mails were there all the time, but the folder was collapsed [sigh!]

Tnx for fast help, webserver restart solved my problem.

Hi @schmidt ,

The default path for kopano-backup is ..

@bmwfan said in Unable to bind to port 236:

How can i identify in the webapp which mails belongs to the not available attachments?

By using search? From the properties table you will learn details such as subject, recipients/sender, body etc.

Hi @marcus-bauch ,

not with the default configuration of Kopano. When adding signatures with e.g. altermime I could imagine that this should be scriptable.

No, both works with the community packages as well.

@canerican the latest one is core-8.5.81.197_0

Hi Felix,

big thanks a lot for quick assistence during weekend. I’ve just successfully reinstalled the kopano-archiver package.

Best regards

Andreas