Issue Bug with postfix hash->lmdb

[knaleffect]

Server operating system version

AlmaLinux 10.1

Plesk version and microupdate number

Plesk Obsidian v18.0.75

Hello!

It's a bug that keeps recurring in Postfix/Plesk. I'm getting the following error in my mail log, and because of this, no emails are being received: warning: hash:/var/spool/postfix/plesk/blacklists lookup error for

Hash is no longer supported or has been removed (I can't say exactly what happened). Now, for the third time in a week, I have to: Replace hash with lmdb in /etc/postfix/main.cf.

This is in the main.cf: smtpd_sender_restrictions =
check_sender_access hash:/var/spool/postfix/plesk/blacklists [..]

and should be replaced with: smtpd_sender_restrictions =
check_sender_access lmdb:/var/spool/postfix/plesk/blacklists [..]

After I changed it and restarted Postfix, it worked again.

Are there more users experiencing this issue and/or is this a known problem?

 

[Sebahat.hadzhi]

Hello, @knaleffect . Could you please confirm the Postfix version used on the server? Thank you in advance.

 

[knaleffect]

Hello, @knaleffect . Could you please confirm the Postfix version used on the server? Thank you in advance.

It is 3.8.5 (apparently it is an outdated version, but it is the version that was installed with Plesk last month - it is a fairly new server)

 

[Sebahat.hadzhi]

Thank you for the update. Our team found the root cause of the issue to be the Email Security extension. They are actively working on it and a fix will be released as soon as possible. Bug ID EXTPLESK-10084. Thank you for your patience in the meantime.

 

[knaleffect]

Thank you for the update. Our team found the root cause of the issue to be the Email Security extension. They are actively working on it and a fix will be released as soon as possible. Bug ID EXTPLESK-10084. Thank you for your patience in the meantime.

Thank you for your reply. I'll patiently await the update.

In the meantime, I'm wondering: This extension has caused several problems in recent months. How will Plesk prevent this in the future (e.g., by improving pre-release testing)?