@fbartels sorry, must have missed that.
thanks a lot :)

@telecom2k3 its more a sign MS is heading towards, kopano went to activesync because of frequent changes in outlook mapi

And one other thing:
There is a FAQ on this topic in the Exim GitHub Wiki section (https://github.com/Exim/exim/wiki/Q5004) which explains use cases in accordance to RFC 2822.
I think the aforementioned fix by removing the header is the easiest way to protect “BCC” information.

Dovecot should not change headers.
As far as I can see, it is up to the IMAP client to decide, whether it shows the “BCC” information or not.
Outlook in my case hides unrelated BCC information, but I can see the full header if I want to.

Another and better way to go, would be to rewriting sendMessage() to send a copy of the mail to each “BCC” recipient, containing only themself as “BCC” recipient in the “BCC” header and the original mail to all “CC” and “TO” recipients without “BCC” information, which should be a fairly simple task.
There is also another bug - at least I think it is one - with sending a mail to “BCC” recipients only (no “TO”), because this does not work.

@bob4os 2.6.2 from the tagged git release.

@allcom said in Z-Push -> apache german Umlaute (öäü) are not displayed correctly:

Hello,
the problem was exclusively with Z-Push email’s suppject (body messages ok), contacts. (Version 2.6.1)
webapp was finaly ok.
The problem was the default apache configuration.
In the default configuration is LANG C

In z-push/backend/kopano/kopano.php is the default hard coded

setlocale(LC_CTYPE, "en_US.UTF-8");

With this setting is “öäü” with the exchange connection by iOS and Andriod is this “???”

The solution is the correct apache configuration with the correct LANG OS settings, or change the hard coded

Hello togheter, this solved my long not solved problem with nginx on ubuntu 18. change locale in:

/usr/share/z-push/backend/kopano/kopano.php

to

setlocale(LC_CTYPE, "de_DE.UTF-8");

my umlauts problem since beginning with kopano is now solved 🤗

There is a branch ZP-1571 which contains a fix already.
(Commit: https://stash.z-hub.io/projects/ZP/repos/z-push/commits/5df5573b4f6bda362ee80d94e07d7cbefbc2a1eb )

The usage of $interval->format("%a") in line 847 on a DateInterval is wrong, because this will never return a valid result.

It should be:
$message->reminder = $interval->format("%i") + $interval->format("%h") * 60 + $interval->format("%d") * 60 * 24;

Hi Manfred,

now it works. I switched off multi-tentancy, reinstalled z-push packages and used the Email-Adress as login username

cheers
Scheini72

Maybe you are rerouting a public mailadress like info@company.com to a public folder so that multiple users have access to that. AND maybe there was a mail delivered where the sender asked for read confirmation.
If so, there might be a user who opened that mail, had seen the request for read confirmation and clicked on “yes” or “send read confirmation”. Tadaaa the user is not allowed to send a read confirmation in behalf of info@company.com. As there is no user info@company.com or the user has not the permission.

Hint if you are using Outlook: In Outlook there is an option “always send read confirmation” or “never ask again”. If so, its happening automatically without the user beeing aware of that. (Took me some time to find that out in the past)

This is just an example. But public folders are a good way to start looking for. Could also be related to public calendars, opened mailboxes with only read permission (and not send as).

Hi @divb,

You asked a similar question at https://forum.kopano.io/topic/3485/check-to-ensure-z-push-is-working?_=1611962439431 already. On top of what was said there alter you could also check the last sync date of a device with z-push-admin.

@zwockel What version of Z-Push are you using and how did you install it originally?

Hi @pixel,

could you provide more information how you import addresses and what exactly do you mean by addresses? Contacts?

Did you check z-push.log?

Also Z-Push 2.4.5 is quite old, please upgrade to a more recent version (currently 2.6.0).

Manfred

1st of all i advice you to switch over to icinga2 ;-) - it has a fantasic gui and with the icinga director you can create checks by gui.
There is a very nice check call check_http, you can also use it with nagios
example:
https://linux.101hacks.com/unix/check-http/

Z-Push uses as far as I know basic http Authentication. So you can create a dummy user to verify the availability of the page.

it must be somethin like:
check_http -H https://yourservernamehere/Microsoft-Server-ActiveSync -a user:password -r “not supported”

Where can i find the ID in the settings of an IPhone ?

@christian said in Synchronise with Ubuntu (18.04) calendar:

https://myserver.com:8443/carddav/christian/

CardDAV is for contacts and not calendars and a standard that is not supported by kopano-ical (it would work with kdav however).

I just did a quick test with Gnome Calendar 3.36.2 and was able to configure a CalDAV calendar source. I configured the calendar url simply as “https://myserver:8443/caldav”.

To prevent the need to specify the ports you could simply proxy the /caldav endpoint in your webserver.

Today I tested the same on a Xiaomi A3 with Android 10 and the default Google Calendar app v2020.20.4-316065245 and everything works!

It looks like the issue just persists on some Android Phones with a proprietary Calendar App like Samsung or some Huawai devices.

I have a devices to reproduce the issue.
@fbartels: does Kopano like to follow this issue or do you think, only “old” Andorid devices are affected and it doesn’t have an impact for your paying customers?
Probably @boospy has more interessts to get it fixed as he has a Kopano Subscription.

Best regards
Matthi

We recreated permission structure (starting of the root) through kopano webapp, not only for the calender involved but also parent folders, this essentially solved it. (the perrmissions where the same, but a rewite seamed required), maybe left over as side effect of importing zarafa SQL dump.

Hi @deisenlord,

depending on what device sends, it’s possible that it really hard deletes the items. In order to check that, you would have to enable WBXML log for the user, wait for the sync with deletion and check the value of DeletesAsMoves tag. 0 means hard (or permanent) delete, 1 (which is default) indicates to move the item into Deleted Items folder first.

Manfred

i tried to import the file directly into Kopano after the second export (from the Google account). Same error.

The file has no error as far as I can judge. As I said, I could solve it via the detour.

As a side note and for further references by others: the script which should fix this is located at https://stash.kopano.io/projects/KSC/repos/core-tools/browse/fix-folder-class.

See also https://forum.kopano.io/topic/3098/folder-without-pr_container_class-how-to-fix