@coffee_is_life

You need to install python3-kopano that is in our core repo (or tar file)

As there are some mayor issues at the moment with the fastly CDN (https://status.fastly.com/) i have no idea which version is on github.com as i can’t acces it

But this is the latest version that has been rewritten a couple of weeks ago
https://stash.kopano.io/projects/KSC/repos/core-tools/browse/recreate-systemfolders

Thanks for the info, @longsleep

Is that also part of the 8.7.xx versions? Apparently, the machine I have encountered is using these packages…

Today occured problem. Webapp made 2 mails with 1 recepient and send it to postfix. I dont know what is it. And why.

Jun 1 08:25:18 srv-cl-mail-be1 postfix/smtpd[3709007]: 9E9C213EA71: client=localhost[127.0.0.1] Jun 1 08:25:18 srv-cl-mail-be1 postfix/cleanup[3696710]: 9E9C213EA71: message-id=<kcEE.b7se5azhQvO3WhQE7mQ3ZQ.ADM4gqZW1wE@srv-cl-mail-be1.voda.local> Jun 1 08:25:18 srv-cl-mail-be1 postfix/qmgr[1076776]: 9E9C213EA71: from=<KAM01@example.com>, size=55919, nrcpt=1 (queue active) Jun 1 08:25:19 srv-cl-mail-be1 postfix/smtpd[3709007]: 29F1F13EA74: client=localhost[127.0.0.1] Jun 1 08:25:19 srv-cl-mail-be1 postfix/cleanup[3696710]: 29F1F13EA74: message-id=<kcEE.b7se5azhQvO3WhQE7mQ3ZQ.gMnQgqZW1wE@srv-cl-mail-be1.voda.local> Jun 1 08:25:19 srv-cl-mail-be1 postfix/qmgr[1076776]: 29F1F13EA74: from=<KAM01@example.com>, size=55919, nrcpt=1 (queue active) Jun 1 08:25:20 srv-cl-mail-be1 postfix/lmtp[3705216]: 9E9C213EA71: to=<oleg@example.com>, relay=127.0.0.1[127.0.0.1]:2003, delay=2, delays=0.01/0/0.01/2, dsn=2.1.5, status=sent (250 2.1.5 oleg@example.com Ok) Jun 1 08:25:20 srv-cl-mail-be1 postfix/qmgr[1076776]: 9E9C213EA71: removed Jun 1 08:25:21 srv-cl-mail-be1 postfix/lmtp[3710929]: 29F1F13EA74: to=<oleg@example.com>, relay=127.0.0.1[127.0.0.1]:2003, delay=2.3, delays=0.01/0.01/0/2.3, dsn=2.1.5, status=sent (250 2.1.5 oleg@example.com Ok) Jun 1 08:25:21 srv-cl-mail-be1 postfix/qmgr[1076776]: 29F1F13EA74: removed

Hi @paulo-ricardo,

@paulo-ricardo said in ldap + tls not working:

Unfortunatelly I’ll be not possible test kopano-one. I started to install it and it requires that I uninstall mysql-server and apache2…8((( but this 2 are required for all my other applications

I am not sure if having other applications running on the same server is within the supported scenarios of Kopano One.

@paulo-ricardo said in ldap + tls not working:

As I am a advanced user can I try kopano groupware? Or it will be a waste of time?

Sure, you could also do a manual installation, afaik the license file should also give you access to the supported build repositories located at https://download.kopano.io/supported. If that is not the case I would recommend replying to one of the demo followup emails to receive an alternative evaluation key.

@divb that should work as well, but also requires the old mapi client and an installed Outlook. Plus it only gives you a pst file.

@mlued said in Kopano user and Active Directory:

The userscripts folder does not contain a “localize-folders” file:

Its a separate program, which is installed to /usr/sbin:

# kopano-localize-folders Usage: /usr/sbin/kopano-localize-folders -u <username> --lang <language>

For that duplicate entry error message I would recommend to get directly in touch with the Kopano support as probably a direct look on your system is required. In my test environment unhooking and recreating stores works just fine with 8.7.20.

Hi @fdefilippo,

the kopano-gateway does not support the concept of opening a mailbox from a user other than the one that logged in. The same question was already asked in https://forum.kopano.io/topic/2087/zarafa-and-imapsync-authuser-feature which also gives a way to still migrate imap boxes without knowing the individual user passwords.

Hi @otto1699,

@otto1699 said in Forwarding by Admin - kopano-rules not found:

is kopano-rules not in the community edition?

I dont think the tool you mentioned is part of the packaging at all. But please be aware that there is no “community edition” what you are referring to are our nightly development builds. For production builds we recommend to use our regular releases.

But back to your question.

The easiest way to set rules for other stores is through the shared rule feature of Kopano WebApp. This needs to be enabled at https://stash.kopano.io/projects/KW/repos/kopano-webapp/browse/config.php.dist?at=e8a9b47c5ab#143 and further explanation can be found at https://documentation.kopano.io/user_manual_webapp/settings.html#rules.

Personally however I would recommend to just add permissions on the mailbox of the sick user and have the replacement work directly in the store (you will likely also want to add sending on behalf for the user as well).

Moreover, pay attention: I made the wrong decision by upgrading a customer from zarafa 7.1 to Kopano. I used the community binary because I had to do the upgrade really fast at only one weekend and didn’t have a “new” Kopano subscription at the moment (but an old Zarafa one) and so no access to the supported Kopano repo. After some days we bought new Kopano subscription but since then, I always have problems with the support because I’m still running the “not-supported” version and they don’t help me with this binary. I have to downgrade to the pretty old stable version, without knowing if someone would help me in any case. And they cannot tell me if a downgrade would work well.

@item Hi, did you solve this problem? I have the same too.
Need to forward incoming maling list to some users. It has header:

Auto-Submitted: auto-generated

Suppose i’ve got:

[warning] Rule "1".": Not forwarding autoreplies

Bumbing this old thread.
This bug still exist in Kopano.

WebApp: 5.0.0.187+1976.1
Kopano Core: 11.0.1

@pixel I think when WebApp says the file is damaged that this must have a different reason. Since you have a subscription I would recommend to open a ticket with the Kopano support and share said file with them.

@fbartels I have reached out to the FSF for clarification.

@tiredofit I will continue working on a patch set to send the required download URL and so on via MAPI to clients. It is part of my work.

@longsleep The FSF will advise. It is not my idea to abolish anything. I am just tasked with getting kopano running on Alpine and, if possible, bringing it into Aports. If you want to have the discussion about abolishing AGPL software, talk to Ariadne of the Alpine Linux team.

Kind regards
Thermi

“MAPI error: interface not supported” is tracked at https://jira.kopano.io/browse/KC-1956

The error should not be logged (and is harmless). It “just” spams the log.

Also /api/gc/v1/me/messages/<message-id>?$select=internetMessageHeaders as suggested by the MS Graph documentation does only return an empty json set (just including the id and odata fields).

None of the following works:

/api/gc/v1/me/messages/<message-id>?$select=internetMessageHeaders /api/gc/v1/me/messages/<message-id>/?$select=internetMessageHeaders /api/gc/v1/me/messages/<message-id>/$select=internetMessageHeaders

How to get the headers of a mail and/or the full MIME representation via grapi. Please don’t tell me that this has not been implemented yet…

@fbartels AMAZING! Thanks!