Kolab 16: Problems after Update

[Lars Andersson]

Regarding the error reported by Roland Kolb and others. I'm not a subscriber to this mailing list but I'm evaluating Kolab 16 and think I know what has gone wrong.

In the new version of /usr/libexec/postfix/kolab_smtp_access_policy the policy_result table has a new column "data", but this has not been added in MySQL/MariaDB.

Dropping or renaming the tables policy_result and statistic will cause kolab_smtp_access_policy to recreate them and then it works. Since I'm not sure how these tables are used I cannot tell if this will cause any useful data to be lost, but I'm guessing not.

Modifying submission_policy in /etc/postfix/master.cf and adding "-l debug" will show the correct error message in /var/log/kolab/pykolab.log

pykolab.smtp_access_policy ERROR Unhandled exception caught: OperationalError('(OperationalError) (1054, "Unknown column \'policy_result.data\' in \'field list\'")',)

This could be the same as reported in https://issues.kolab.org/show_bug.cgi?id=5471



A second problem, with clamd not starting, reported by Gregor Adamczyk in "***UNCHECKED*** Tagging on all messages" could be because /etc/systemd/system/multi-user.target.wants/clamd at amavisd.service is not a link to /usr/lib/systemd/system/clamd\@.service but rather a script file trying to start clamd with the "--nofork" option that is no longer supported. Replace the script in /etc/systemd with a link to the correct script that should use the new "--foreground" option instead.


Kind regards
Lars Andersson