Subject
Other
Description
If you use the fts-xapian-plugin specified in the documentation https://docker-mailserver.github.io/docker-mailserver/edge/config/advanced/full-text-search/#xapian , then after updating dms to 12.0, it will stop working for you. On 11.3.1 I am not getting any errors. I found mention of a similar problem since 2022 in the repository of this plugin. This was not fixed, and after a while the error was closed by the initiator. I think it would be right to remove the recommendation of this plugin from the documentation concerning 12.0, latest and edge, because everything works on 11.3.1 (I checked on my amd64 configuration, Debian 11, Docker 23.0.2, build 569dd73, Docker Compose v2.17.2). Or you can specify a link in the documentation to your answer here to a similar error as an option for using this plugin.
What happened and when does this occur?
when start container:
[ DEBUG ] Configuring Amavis
[ DEBUG ] Spam emails will be moved to the Junk folder
sievec: Fatal: Couldn't load required plugin /usr/lib/dovecot/modules/lib21_fts_xapian_plugin.so: Module is for different ABI version 2.3.ABIv13(2.3.13) (we have 2.3.ABIv20(2.3.20))
chown: cannot access '/usr/lib/dovecot/sieve-global/after/spam_to_junk.svbin': No such file or directory
Subject
Other
Description
If you use the fts-xapian-plugin specified in the documentation https://docker-mailserver.github.io/docker-mailserver/edge/config/advanced/full-text-search/#xapian , then after updating dms to 12.0, it will stop working for you. On 11.3.1 I am not getting any errors. I found mention of a similar problem since 2022 in the repository of this plugin. This was not fixed, and after a while the error was closed by the initiator. I think it would be right to remove the recommendation of this plugin from the documentation concerning 12.0, latest and edge, because everything works on 11.3.1 (I checked on my amd64 configuration, Debian 11, Docker 23.0.2, build 569dd73, Docker Compose v2.17.2). Or you can specify a link in the documentation to your answer here to a similar error as an option for using this plugin.
What happened and when does this occur?
when start container: