Maybe you are rerouting a public mailadress like firstname.lastname@example.org 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 email@example.com. As there is no user firstname.lastname@example.org 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).
@burgessja yes, that is pretty much the expected way unless there would be official builds from us. The good thing about go is that you could compile it on a different system (or in a container) and just copy the resulting binary to your target system.
If you log into the Zimbra admin, and go to Configure->Domains-><your domain>
You will see the 3 settings.
Public service hostname
Public service protocol
Public service port
These are what z-push picks up from the user session when it first connects - as in a multi-server environment it is important to connect to the actual MTA that hosts the user’s account. It overrides whatever you have set in your ZIMBRA_URL with a url constructed from these values.
It sounds like you may have changed the zimbra proxy settings during your “move” which can cause this issue.
The reason that the folder list gets populated is that is is also returned in the payload from the initial login request. The reason no other data gets populated is that a connection cannot be made to the overridden ZIMBRA_URL (as described above)
with your Links I was able to understand the Searchfilter.
The Solution was to change my ldap.cfg at line ldap_emailaliases_attribute = kopanoAliases toldap_emailaliases_attribute = otherMailbox like described in the postfix configuartion for ADS. The tag “kopanoAliases” only works with LDAP not with ADS.
PS: since you have a subscription for Kopano One the recommended approach to get support is to directly open a ticket with the Kopano helpdesk. This place is just a forum for the community and not an official support channel.
@worms By looking around, kopano-cli is actually a python file… just had to install an older version of kopano-core somewhere to get the file on my current install…
For now it works… until the next update where Kopano dev will remove the ability to loggin as a user with the python lib :)
I hope this will not happens… otherwise, see you next year for probably my last good bye :’(
I have exactly the same issue besides time shift is just one hour. My timezone is Europe/Berlin.
I can’t confirm that this problem is caused by IMAP.
Server is a vm on proxmox host
Kopano-webapp is running on a Univention Corporate Server (member) together with kopano-core and z-push app on it.
System clock is configured to timezone Europe/Berlin (localtime)
RTC is running on UTC
ntp is running for synchronisation
timezone is configured to Europe/Berlin in php.ini (apache, cgi, cli) and webapp/config.php
What I checked/tested is:
reset RTC to use localtime
checked postfix timezone
most importantly when sending a mail within webapp to yourself the problem also exists. A raw-file logged at dagent and picture:
Received: from ucs-mbr01c.intranet.example.com (127.0.0.1:33308)
by ucs-mbr01c (kopano-dagent) with LMTP;
Fri, 19 Feb 2021 22:11:42 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
by ucs-mbr01c.intranet.example.com (Postfix) with ESMTP id E601F10006C
for <email@example.com>; Fri, 19 Feb 2021 22:11:41 +0100 (CET)
X-Virus-Scanned: by amavisd-new-2.10.1 (20141025) (Debian) at
X-Spam-Status: No, score=-0.899 tagged_above=-1000 required=5
tests=[ALL_TRUSTED=-1, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1]
Received: from ucs-mbr01c.intranet.example.com ([127.0.0.1])
by localhost (ucs-mbr01c.intranet.example.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 8hKFIPptgGxK for <firstname.lastname@example.org>;
Fri, 19 Feb 2021 22:11:40 +0100 (CET)
Received: from ucs-mbr01c (localhost [127.0.0.1])
by ucs-mbr01c.intranet.example.com (Postfix) with ESMTP id 7CAC4100069
for <email@example.com>; Fri, 19 Feb 2021 22:11:40 +0100 (CET)
Received: by ucs-mbr01c (kopano-spooler) with MAPI; Fri, 19 Feb 2021 22:11:39
Subject: Mail sent at 22:11
From: "Max Mustermann" <firstname.lastname@example.org>
Date: Fri, 19 Feb 2021 21:11:39 +0000
Content-Type: text/html; charset=utf-8
X-Priority: 3 (Normal)
X-Mailer: Kopano 8.7.1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://ww=
<meta name=3D"Generator" content=3D"Kopano WebApp v188.8.131.529+111.1">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8=
<title>Mail sent at 22:11</title>
<!-- begin sanitized html --><p style=3D"padding: 0; margin: 0;"><span st=
yle=3D"font-size: 10pt; font-family: tahoma, arial, helvetica, sans-serif=
<!-- end sanitized html -->
I am running out of ideas where to look, what else to check and why webapp is not using my configured timezone.