I was able to test in 8.7 as well and this still exists in Kopano Core 8.7.

This issue was still present when testing in KC 10. It was lessened when testing in Kopano Core 8.7.25. In 8.7, the attendees only receive a cancellation message for the series as a whole and one for each “altered” event. In 10 and 11, the attendee would receive several duplicate messages for both the series as a whole and for each altered event.

gentlemen,
the forum-language is English.

locate kopano-cleanup.py /usr/share/python-kopano/kopano-cleanup.py

use either:
cd /usr/share/python-kopano/ && python3 ./kopano-cleanup.py [args]
or:
python3 /usr/share/python-kopano/kopano-cleanup.py [args]

Remember crontab -e works on the current user’s crontab
Depending on your setup, a crontab -e -uotheruser might be useful.
++umgfoin.

I’m not sure about the receiving part however Sending is:

Kopano Spooler -> Postfix -> SMTP External Mailserver

The reason why you need to insert Postfix in the middle is due to the Kopano spooler not supporting authentication to the remote server, it has been discussed here in the forum in the past.

@odix67
missing folders issue is resolved, was my fault, using another IMAP client, the missing folders show up, tip from kopano support to refresh the folders in the subscription setting of thunderbird resolves the problem also in thunderbird.

but the other issue, regarding garbage after moving a message via IMAP, still remains

The basic issue here, is that development of something that differentiates a mail program from another one is massively expensive, and how exactly do you differentiate from one another?

yes, Kopano is good, but is it worth the license? Who knows.

The main loss was of course the Outlook backend… and since then, it has been downhill ever since.

Hence: that’s why we are here right now.

Hi @mkuemmerle

Great
i am appreciate and thank you

@bee-support
just found out, thers are no private message possbible.
Here my cleansed files.
Did you put as well postfix into the sasl group

saslauthd.conf:

# meine config für sasl # Servers ldap_servers: ldap://localhost:389/ # Identity ldap_bind_dn: <bind-user> ldap_password: <password>x ldap_auth_method: bind # Search ldap_search_base: <search-base>

saslauthd-postfix:

# # Settings for saslauthd daemon # Please read /usr/share/doc/sasl2-bin/README.Debian for details. # # Should saslauthd run automatically on startup? (default: no) START=yes # Description of this saslauthd instance. Recommended. # (suggestion: SASL Authentication Daemon) DESC="SASL Authentication Daemon for Postfix" # Short name of this saslauthd instance. Strongly recommended. # (suggestion: saslauthd) NAME="saslauthd" # Which authentication mechanisms should saslauthd use? (default: pam) # # Available options in this Debian package: # getpwent -- use the getpwent() library function # kerberos5 -- use Kerberos 5 # pam -- use PAM # rimap -- use a remote IMAP server # shadow -- use the local shadow password file # sasldb -- use the local sasldb database file # ldap -- use LDAP (configuration is in /etc/saslauthd.conf) # # Only one option may be used at a time. See the saslauthd man page # for more information. # # Example: MECHANISMS="pam" MECHANISMS="ldap" # Additional options for this mechanism. (default: none) # See the saslauthd man page for information about mech-specific options. MECH_OPTIONS="" # How many saslauthd processes should we run? (default: 5) # A value of 0 will fork a new process for each connection. THREADS=10 # Other options (default: -c -m /var/run/saslauthd) # Note: You MUST specify the -m option or saslauthd won't run! # # WARNING: DO NOT SPECIFY THE -d OPTION. # The -d option will cause saslauthd to run in the foreground instead of as # a daemon. This will PREVENT YOUR SYSTEM FROM BOOTING PROPERLY. If you wish # to run saslauthd in debug mode, please run it by hand to be safe. # # See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information. # See the saslauthd man page and the output of 'saslauthd -h' for general # information about these options. # # Example for chroot Postfix users: "-c -m /var/spool/postfix/var/run/saslauthd" # Example for non-chroot Postfix users: "-c -m /var/run/saslauthd" # # To know if your Postfix is running chroot, check /etc/postfix/master.cf. # If it has the line "smtp inet n - y - - smtpd" or "smtp inet n - - - - smtpd" # then your Postfix is running in a chroot. # If it has the line "smtp inet n - n - - smtpd" then your Postfix is NOT # running in a chroot. #OPTIONS="-c -m /var/run/saslauthd" OPTIONS="-c -m /var/spool/postfix/var/run/saslauthd"

main.cf:

# damit steht Postfix offen im Netz (Einschalter inet_interfaces = all #inet_interfaces = loopback-only inet_protocols = all #switch on local bind only (to avoid sneding) #smtp_bind_address = localhost [...] # Hier kommen alle Einstellungen, damit mein Benutzer überprüfut wird #hiermit fangen wir an, nur bestimmte Luete (uns) den Server benutzen zu lassne smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noplaintext, noanonymous smtpd_sasl_tls_security_options = noanonymous smtpd_sasl_path = smtpd # security level encrypt funktioniert nicht wegen z-push und wbapp smtpd_tls_security_level = may smtp_tls_note_starttls_offer = yes [...] smtpd_tls_auth_only = yes #smtp_tls_security_level = encrypt smtp_tls_security_level = may smtp_tls_mandatory_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1 #smtp_tls_mandatory_protocols = >=TLSv1.2 smtp_tls_mandatory_ciphers = high [...] smtpd_relay_restrictions = permit_sasl_authenticated permit_mynetworks defer_unauth_destination [...] # Wir liefern Alles an Kopano über den lmtp über file socket #virtual_transport = lmtp:127.0.0.1:2003 #mailbox_transport = lmtp:127.0.0.1:2003 virtual_transport = lmtp:[::1]:2003 mailbox_transport = lmtp:[::1]:2003 #helo restriction, smtpd_helo_restrictions = permit_mynetworks permit_sasl_authenticated reject_invalid_hostname reject_non_fqdn_hostname reject_unauth_destination reject_non_fqdn_sender reject_non_fqdn_recipient reject_unknown_recipient_domain reject_invalid_hostname reject_rbl_client zen.spamhaus.org reject_unauth_pipelining permit smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated reject_unauth_destination # SPF has to be AFTER "reject_unauth_destination check_sender_access hash:/etc/postfix/sender_check check_policy_service unix:private/policyd-spf check_policy_service inet:localhost:10023 # check_policy_service inet:localhost:12346 #Spammer ablehnen disable_vrfy_command = yes smtpd_helo_required = yes smtpd_delay_reject = yes smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) biff = no [...]

master.cf

# # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master" or # on-line: http://www.postfix.org/master.5.html). # # Do not forget to execute "postfix reload" after editing this file. # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (no) (never) (100) # ========================================================================== smtp inet n - y - - smtpd #smtp inet n - y - 1 postscreen #smtpd pass - - y - - smtpd #dnsblog unix - - y - 0 dnsblog #tlsproxy unix - - y - 0 tlsproxy submission inet n - y - - smtpd -o syslog_name=postfix/submission # -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_tls_auth_only=yes # -o smtpd_reject_unlisted_recipient=no # -o smtpd_client_restrictions=$mua_client_restrictions # -o smtpd_helo_restrictions=$mua_helo_restrictions # -o smtpd_sender_restrictions=$mua_sender_restrictions # -o smtpd_recipient_restrictions= # -o smtpd_relay_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING smtps inet n - y - - smtpd -o syslog_name=postfix/smtps -o smtpd_tls_wrappermode=yes -o smtpd_sasl_security_options=noplaintext -o smtpd_sasl_auth_enable=yes -o smtpd_reject_unlisted_recipient=no # -o smtpd_client_restrictions=$mua_client_restrictions # -o smtpd_helo_restrictions=$mua_helo_restrictions # -o smtpd_sender_restrictions=$mua_sender_restrictions # -o smtpd_recipient_restrictions= # -o smtpd_relay_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #628 inet n - y - - qmqpd pickup unix n - y 60 1 pickup cleanup unix n - y - 0 cleanup qmgr unix n - n 300 1 qmgr #qmgr unix n - n 300 1 oqmgr tlsmgr unix - - y 1000? 1 tlsmgr rewrite unix - - y - - trivial-rewrite bounce unix - - y - 0 bounce defer unix - - y - 0 bounce trace unix - - y - 0 bounce verify unix - - y - 1 verify flush unix n - y 1000? 0 flush proxymap unix - - n - - proxymap proxywrite unix - - n - 1 proxymap smtp unix - - y - - smtp relay unix - - y - - smtp -o syslog_name=postfix/$service_name # -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 showq unix n - y - - showq error unix - - y - - error retry unix - - y - - error discard unix - - y - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - y - - lmtp anvil unix - - y - 1 anvil scache unix - - y - 1 scache postlog unix-dgram n - n - 1 postlogd # # ==================================================================== # Interfaces to non-Postfix software. Be sure to examine the manual # pages of the non-Postfix software to find out what options it wants. # # Many of the following services use the Postfix pipe(8) delivery # agent. See the pipe(8) man page for information about ${recipient} # and other message envelope options. # ==================================================================== # # maildrop. See the Postfix MAILDROP_README file for details. # Also specify in main.cf: maildrop_destination_recipient_limit=1 # maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient} # # ==================================================================== # # Recent Cyrus versions can use the existing "lmtp" master.cf entry. # # Specify in cyrus.conf: # lmtp cmd="lmtpd -a" listen="localhost:lmtp" proto=tcp4 # # Specify in main.cf one or more of the following: # mailbox_transport = lmtp:inet:localhost # virtual_transport = lmtp:inet:localhost # # ==================================================================== # # Cyrus 2.1.5 (Amos Gouaux) # Also specify in main.cf: cyrus_destination_recipient_limit=1 # #cyrus unix - n n - - pipe # user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user} # # ==================================================================== # Old example of delivery via Cyrus. # #old-cyrus unix - n n - - pipe # flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user} # # ==================================================================== # # See the Postfix UUCP_README file for configuration details. # uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) # # Other external delivery methods. # ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=bsmtp argv=/usr/lib/bsmtp/bsmtp -t$nexthop -f$sender $recipient scalemail-backend unix - n n - 2 pipe flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store ${nexthop} ${user} ${extension} mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} policyd-spf unix - n n - 0 spawn user=policyd-spf argv=/usr/bin/policyd-spf

smtp.conf:

pwcheck_method: saslauthd mech_list: plain login ldap_servers: ldap://localhost:389/ ldap_search_base: <search-base> ldap_timeout: 10 ldap_filter: sAMAccountName=%U ldap_bind_dn: <bind-user> ldap_password: <bind-password> ldap_deref: never ldap_restart: yes ldap_scope: sub ldap_use_sasl: no ldap_start_tls: no ldap_version: 3 ldap_auth_method: bind

cheers

@mapo
Hi.

Thank you for this great script! That saved me a lot of work :).

However, I have two questions:

How does the restore work?
This call doesn’t work with message “please specify path to backup data”: kopano-backup --index /var/backups/kopano_backup/users/[username] | grep [subject] The SQLdump has 0 bytes. I don’t think that’s possible. I use Kopano on a Univention-Host. Do User/Passwords for the database still have to be defined somewhere?
Or does the script need to be run as a specific user (not root).

Thank you!

Best wishes,
Philipp

@umgfoin

nothing besides the “K-1281: create /var/lib/kopano/attachments/18/d1/dd3d8a947a6e: File exists” message. I did not enable debugging.

I did check the permissions, they were all right. Files were created so those must have been correct. For some reasons the files were 0 bytes large for some reason.

Anyway, the problem was solved by installing a new Kopano instance and transferring all mails with impasync,

cheers,

BC

After a long time I was able to fix it with a simple command:

rm -r /var/lib/kopano/search

Hi @Ray-Ellison
this looks like a damaged rule in the users store.

I suggest to check the rules with wepapp.

regards
Mathias