Resolved Amavis installed by Plesk Email Security fatal error

[TomBoB]

Server operating system version

Almalinux AlmaLinux 9.7

Plesk version and microupdate number

Plesk Obsidian 18.0.74 Update #3

Hi,
Server stopped processing emails. Error messages in the log files:

2026-01-06 10:08:15 warning
amavis [138253]
(138253-01) (!)Requesting process rundown after fatal error

2026-01-06 10:08:15 err
amavis [138253]
(138253-01) (!!)TROUBLE in process_request: connect_to_sql: unable to connect to any dataset at /usr/share/perl5/vendor_perl/Amavis/Out/SQL/Connection.pm line 255.

2026-01-06 10:08:15 warning
amavis [138253]
(138253-01) (!)connect_to_sql: unable to connect to DSN 'DBI:MariaDB:database=emailsecurity;mysql_socket=/var/lib/mysql/mysql.sock': Unknown attribute mysql_socket

Did open a support ticket as well. But as that can be slow to be responded to, and we can't leave clients without mails, maybe someone here knows the answer.
Will remove PES in the meantime.

EDIT: uninstall and reinstall of PES has been done.

 

[Rexikon]

go to: /etc/amavisd/email-security.conf
change from:

@lookup_sql_dsn =(
    ["DBI:MariaDB:database=emailsecurity;mysql_socket=/var/lib/mysql/mysql.sock", "xxxxx", "xxxxx"]
);

to:

@lookup_sql_dsn =(
    ["DBI:MariaDB:database=emailsecurity;host=127.0.0.1", "xxxx", "xxxxxx"]
);

 

[TomBoB]

go to: /etc/amavisd/email-security.conf
change from:

@lookup_sql_dsn =(
    ["DBI:MariaDB:database=emailsecurity;mysql_socket=/var/lib/mysql/mysql.sock", "xxxxx", "xxxxx"]
);

to:

@lookup_sql_dsn =(
    ["DBI:MariaDB:database=emailsecurity;host=127.0.0.1", "xxxx", "xxxxxx"]
);

Plesk support has just given me a slightly different workaround. I'll test both tonight when there is very little email traffic.

 

[Rexikon]

Plesk support has just given me a slightly different workaround. I'll test both tonight when there is very little email traffic.

can you share theirs workaround?

 

[Sebahat.hadzhi]

@Rexikon , the workaround proposed by our team can be found here:

• https://support.plesk.com/hc/en-us/...with-Plesk-Email-Security-extension-installed

Our devs are actively working on resolving the issue.

 

[webtrajo]

@Rexikon , the workaround proposed by our team can be found here:

• https://support.plesk.com/hc/en-us/...with-Plesk-Email-Security-extension-installed

Our devs are actively working on resolving the issue.

Hello,

I'm experiencing the same error on my system.
Unfortunately, the workaround isn't working for me!

I hope for a quick solution to this problem!

 

[Rexikon]

Hello,

I'm experiencing the same error on my system.
Unfortunately, the workaround isn't working for me!

I hope for a quick solution to this problem!

test my workaround mentioned above

 

[TomBoB]

@Rexikon , the workaround proposed by our team can be found here:

• https://support.plesk.com/hc/en-us/...with-Plesk-Email-Security-extension-installed

Our devs are actively working on resolving the issue.

Hi,
Have tested, and then implemented, the solution as provided by Plesk support.
Replaced the mysql_socket with mariadb_socket in specific locations in 2 separate files, and restarted amavis.
Did the trick and mail is flowing nicely again.
Thanks!
EDIT: had removed the PES extension completely. Reloaded it to test, and it worked after the 2 adjustments.

 

[webtrajo]

I have just seen that PLESK has already made an update available.

https://support.plesk.com/hc/en-us/articles/37469672034327-Unable-to-send-or-receive-email-with-Plesk-Email-Security-extension-installed

After the update, emails are working again for me as well.

 

[first4it]

I haven't changed the config files but referenced by TomBoB but I have installed the latest Plesk E-Mail Security extension (version 1.5.23-7922) and my amavisd service will still not start. I can't work out what is wrong, it stopped working on the 5th Jan, the day Plesk released their update. I'm fed up of their updates breaking my server.

All my mail is showing as 'deferred' and clients are climbing the walls. There are two points (a) What broke it! and (b) I need it running again. We used to gather data years ago to investigate issues but get everything running so service was not affected. Anyone help me to do this?

 

[knaleffect]

I haven't changed the config files but referenced by TomBoB but I have installed the latest Plesk E-Mail Security extension (version 1.5.23-7922) and my amavisd service will still not start. I can't work out what is wrong, it stopped working on the 5th Jan, the day Plesk released their update. I'm fed up of their updates breaking my server.

All my mail is showing as 'deferred' and clients are climbing the walls. There are two points (a) What broke it! and (b) I need it running again. We used to gather data years ago to investigate issues but get everything running so service was not affected. Anyone help me to do this?

For me, it was ultimately the Perl MariaDB that was missing. What does the Action log -> Mail in Plesk tell you?

 

[first4it]

For me, it was ultimately the Perl MariaDB that was missing. What does the Action log -> Mail in Plesk tell you?

I can confirm that this was exactly the same for me. I am trying to work out how this happened, by what and when in order to update my customers.