Thank you Damian and Indunil, it took a while for me to get to
production server, but now I switched from DBI:mysql to DBI:MariaDB and
it works.
Greetings!
Tomaž
On 2024-03-29 03:48, Indunil Jayasooriya wrote:
Damian, Yes, You and I discussed this in this list before.
Here's the URL.
Damian, Yes, You and I discussed this in this list before.
Here's the URL.
https://www.mail-archive.com/amavis-users@amavis.org/msg06624.html
I am happily running in production on Alma Linux 9
with perl-DBD-MariaDB-1.21-16.el9_0.x86_64 and mariadb.
in amavisd.conf file.
@lookup_sql_dsn = (
Is this temporary fix safe to use
I have not seen feedback on Gitlab or amavis-users that it lead to problems.
until a new version of perl-DBD-MySQL is released for RHEL9 (and AlmaLinux9 and
others)?
Unless some changed their mind, there won't be a fix in perl-DBD-MySQL.
Instead you can
On 2024-03-28 11:18, Damian wrote:
Probably this again: https://gitlab.com/amavis/amavis/-/issues/7
Thank you for a very quick answer!
I can confirm that we have the same situation.
Obviously we have version installed that doesn't address this problem:
perl-DBD-MySQL.x86_64 4.050-13.el9
Hi everybody,
I kindly ask for assistance.
Amavis doesn't get the right spam score values from policy table in
MySQL. When columns (spam_tag2_level, spam_tag3_level,
spam_kill_level) are unmodified and are NULL, the default values are
from Amavis config file. But when we modify the row
Hi everybody,
I kindly ask for assistance.
Amavis doesn't get the right spam score values from policy table in
MySQL. When columns (spam_tag2_level, spam_tag3_level, spam_kill_level)
are unmodified and are NULL, the default values are from Amavis config
file. But when we modify the row