I found the description for the movement.
https://documentation.kopano.io/kopanocore_administrator_manual/configure_kc_components.html#storing-attachments-outside-the-database

UPDATE: Easy fix - Kopano-Spooler was not started.

strace -e socket kopano-gateway -F

Hi @irreleph4nt ,

the delegation/sendas relations are managed based on GAB entries in Kopano. For this you either need another (in)active user the the gab or (if you are using ldap) a contact to apply these setting on.

If this is a single user system and you don’t care about explicit permissions to send as another email address you can also set the following in the spooler.cfc:

# Set this value to 'yes' to let the spooler always send emails with # delegates (other user than yourself in the From: header) # In installations before 6.20, this value was always 'yes'. # IMPORTANT: This feature overrides "send-as" functionality. #always_send_delegates = no

One thing though:

@irreleph4nt said in "Send as" based on postfix virtual mail inbox:

and from my iPhone

The instance that ultimately says “I want to send with x as the sender” is the used client. For WebApp and DeskApp you can choose this without problems (the same counts for a KOE enhanced Outlook btw), but mobile devices usually don’t have the possibility to choose the sending address.

@umgfoin For a production server I’d rather stay with repositories for maintainability, and since this is also about the supported Kopano version…

@fbartels I get your point about using scl to garantee RedHat support. No easy escape than :-(

AFAICT it will use ldap.conf for TLS parameters (like, for example, “TLS_REQCERT allow”).

The 8.5.9 final version has been re-uploaded into the tarball archives.

I had the same issue and solved it by copying the required configuration templates from the following directory: /usr/share/doc/kopano/example-config. Some of the files could just be copied using cp and other were compressed (those ending with .gz), so I had to use the gunzip command like this:
gunzip -c /usr/share/doc/kopano/example-config/server.cfg.gz | tee /etc/kopano/server.cfg

We don’t include them in our packaging, but a mirror of the files used in the last release can be found at https://build.opensuse.org/package/show/server:mail:kopano/kopano

maybe https://stash.kopano.io/projects/KC/repos/kopanocore/browse/swig/python/kopano/scripts/rfcdump.py helps. this is a general purpose script to im- and export various content types (but no notes).

Update: solved.

replace the “xxx” with 'xxx"

Hi Gerald,

as you said and also experienced: it seems that this has been broken. It worked fine with Zarafa Server, it does not work anymore on Kopano server.

As I explained detailled on my initial post, nothing has changed on the client side. It does make no sense for me, to have all the employees remove a shared calendar which they have attached within their Outlook client and in the following attach the whole mailbox into their Outlook. They do not need access mail, task, contact objects etc. they just need access to the shared calendar of Alice.

Hello,

i fond a solution by using kopano-backup delete user create user restore without “Gesendete Objekte” ;-)

Greets
Thomas

Yes, it was a helpful :) Thank’s a lot

Hi @General_Probe ,

the problem should indeed be resolved. It seems there was there a residual python2*.deb package (as evidence of the old version tag) in the directory where the archives are created from. I’ve now manually deleted it, so it should be gone from the next upload.

@John-Carter,

there is a script called kopano-rules.py (https://stash.kopano.io/projects/KSC/repos/core-tools/browse)

you can create a little script like

for e in $(kopano-admin -l | | tail -n+5 | head -n-1 |awk -F" " '{print $1}'| grep -v <paul's username>); do echo "create rule for $e" kopano-rules.py --user=$e --create "<rulename>" --conditions "contain-word-in-header:@test.eu" --actions "copy-to:Inbox,<paul's username>" if [ $? = 0 ]; then echo "success for $e" else echo "failed for $e" fi done

this should create a rule for every user (except paul) to copy an incomeing mail, containing the domain in the header, to pauls inbox

if someone knows a cleaner rule (like a working “received-from:*@test.eu”), please share :)

regards
coffee_is_life

Hi @Don ,

you should upgrade to a more recent version, this error was recently fixed.

[error ] SQL [00000004] Failed: Duplicate entry 'x-no-relay' for key 'gns', Query Size: 170, Query: "ALTER TABLE `names` ADD UNIQUE INDEX `gni` (`guid`(16), `nameid`), ADD UNIQUE INDEX `gns` (`guid`(16), `namestring`), DROP INDEX `guidnameid`, DROP INDEX `guidnamestring`" [error ] KDatabase::I_Update() query failed: "Duplicate entry 'x-no-relay' for key 'gns'", query: ALTER TABLE `names` ADD UNIQUE INDEX `gni` (`guid`(16), `nameid`), ADD UNIQUE INDEX `gns` (`guid`(16), `namestring`), DROP INDEX `guidnameid`, DROP INDEX `guidnamestring` [error ] K-1216: Cannot update to schema v69, because the "names" table contains unexpected rows. Certain prior versions of the server erroneously allowed these duplicates to be added (KC-1108). [error ] K-1220: To fix the excess rows, use `kopano-dbadm k-1216`. Consult the manpage and preferably make a backup first. [error ] K-1221: Alternatively, the server may be started with --ignore-da to forego the schema update. [warning] WARNING: Unable to upgrade database from version 8.5.9.2153316352.68 to 8.5.9.2153316352.70 [warning] You can force the server to start with --ignore-database-version-conflict [warning] Warning, you can lose data! If you don't know what you're doing, you shouldn't be using this option!

After the recent update the server stays offline.

The “kopano-dbadm k-1216” command seams to fix the problem for me.

Hello all,

I also have lots of [error] Autoresponder failed lines regularly appear in dagent.log
In my signature at the bottom you can see the versions I am running. But in my case it doesn’t seem to be related to the mentioned bug because it was already fixed. To ensure: when I run the command:
grep -R -i arithemtic /var/log/kopano
I get no results.

Then I raised the log level to debug in dagent.cfg and restarted that service. The error in detail:

Tue May 29 09:30:41 2018: [debug ] [ 9495] > RCPT TO:<kathy.long@mydoma.in> Tue May 29 09:30:41 2018: [debug ] [ 9495] Resolved command "RCPT TO:<kathy.long@mydoma.in>" to recipient address "kathy.long@mydoma.in" Tue May 29 09:30:41 2018: [notice ] [ 9495] Resolved recipient kathy.long@mydoma.in as user kathy Tue May 29 09:30:41 2018: [debug ] [ 9495] < 250 2.1.5 Ok Tue May 29 09:30:41 2018: [debug ] [ 9495] > DATA Tue May 29 09:30:41 2018: [debug ] [ 9495] < 354 2.1.5 Start mail input; end with <CRLF>.<CRLF> Tue May 29 09:30:41 2018: [debug ] [ 9495] PYTHONPATH = /usr/share/kopano-dagent/python Tue May 29 09:30:41 2018: [info ] [ 9495] * Loading plugins started Tue May 29 09:30:41 2018: [info ] [ 9495] ** Checking plugins in /var/lib/kopano/dagent/plugins Tue May 29 09:30:41 2018: [info ] [ 9495] * Loading plugins done Tue May 29 09:30:41 2018: [debug ] [ 9495] Initializing provider "Kopano Directory Service" Tue May 29 09:30:41 2018: [debug ] [ 9495] Initializing provider "Private Folders" Tue May 29 09:30:41 2018: [debug ] [ 9495] Initializing provider "Public Folders" Tue May 29 09:30:41 2018: [debug ] [ 9495] Initializing provider "Kopano Directory Service" Tue May 29 09:30:41 2018: [debug ] [ 9495] Initializing provider "Private Folders" Tue May 29 09:30:41 2018: [debug ] [ 9495] Initializing provider "Public Folders" Tue May 29 09:30:41 2018: [info ] [ 9495] Mail will be delivered in Inbox Tue May 29 09:30:41 2018: [debug ] [ 9495] Trying to parse alternative multipart 1 of mail body Tue May 29 09:30:41 2018: [debug ] [ 9495] HTML4 meta tag found: charset="text/html; charset=iso-8859-1" Tue May 29 09:30:41 2018: [debug ] [ 9495] HTML charset adjusted to "iso-8859-1" Tue May 29 09:30:41 2018: [debug ] [ 9495] renovate_encoding: reading data using charset "iso-8859-1" succeeded. Tue May 29 09:30:41 2018: [info ] [ 9495] * PostConverting processing started Tue May 29 09:30:41 2018: [info ] [ 9495] * PostConverting processing done Tue May 29 09:30:41 2018: [info ] [ 9495] * PreDelivery processing started Tue May 29 09:30:41 2018: [info ] [ 9495] * PreDelivery processing done Tue May 29 09:30:41 2018: [debug ] [ 9495] Initializing provider "Kopano Directory Service" Tue May 29 09:30:41 2018: [debug ] [ 9495] Initializing provider "Private Folders" Tue May 29 09:30:41 2018: [debug ] [ 9495] Initializing provider "Public Folders" Tue May 29 09:30:41 2018: [info ] [ 9495] * PreRuleProcess processing started Tue May 29 09:30:41 2018: [info ] [ 9495] * PreRuleProcess processing done Tue May 29 09:30:41 2018: [debug ] [ 9495] Processing rule Delegate Meetingrequest service for kathy Tue May 29 09:30:41 2018: [info ] [ 9495] Rule Delegate Meetingrequest service doesn't match: 0x8004010f Tue May 29 09:30:41 2018: [debug ] [ 9495] Processing rule Kategorien der E-Mails löschen (empfohlen) for kathy Tue May 29 09:30:41 2018: [info ] [ 9495] Rule Kategorien der E-Mails löschen (empfohlen) doesn't match: 0x8004010f Tue May 29 09:30:41 2018: [debug ] [ 9495] Target user has OOF active Tue May 29 09:30:41 2018: [info ] [ 9495] Starting autoresponder for out-of-office message Tue May 29 09:30:41 2018: [debug ] [ 9495] Running command: "/usr/sbin/kopano-autorespond" "kathy.long@mydoma.in" "peter.gens@partn.er" "Abwesend" "kathy" "/tmp/autorespond.qaQX2Q" Tue May 29 09:30:41 2018: [error ] [ 9495] Autoresponder failed Tue May 29 09:30:41 2018: [info ] [ 9495] * PostDelivery processing started Tue May 29 09:30:41 2018: [info ] [ 9495] * PostDelivery processing done Tue May 29 09:30:41 2018: [info ] [ 9495] * SendNewMailNotify processing started Tue May 29 09:30:41 2018: [info ] [ 9495] * SendNewMailNotify processing done Tue May 29 09:30:41 2018: [debug ] [ 9495] Send 'New Mail' notification Tue May 29 09:30:41 2018: [info ] [ 9495] Delivered message to "kathy", Subject: "Something", Message-Id: <08c01920b4244633aabb8a73ffa63b14@mx1-mta.partn.er>, size 47457 Tue May 29 09:30:41 2018: [info ] [ 9495] Finished processing message Tue May 29 09:30:41 2018: [debug ] [ 9495] < 250 2.1.5 kathy.long@mydoma.in Ok Tue May 29 09:30:41 2018: [debug ] [ 9495] > QUIT Tue May 29 09:30:41 2018: [debug ] [ 9495] < 221 2.0.0 Bye Tue May 29 09:30:41 2018: [info ] [ 9495] LMTP thread exiting

why do each processed message generate such an error message? any clues where to look at and how to fix it? In the debug log I posted you also see the status code … doesn’t match: 0x8004010f appear often. Is that anything to worry about?

thanks to everyone in advance.