Unable to send emails, error within postfix container: sni.map.db can't be found

I have (or had) a working setup of mailcow. Since 2 weeks ago I’m unable to send emails. Mails arrive, but not depart.

From logs of postfix container:

The service tries to find sni.map.db file and fails.

So far I’ve tried:

• Force renewal
  docs.mailcow.email

  Advanced SSL - mailcow: dockerized documentation

  None

  
  ,
• Reset TLS certificates
  docs.mailcow.email

  Reset TLS certificates - mailcow: dockerized documentation

  None

  
  ,
• checked and changed to/from root user permissions as per this discussion
  mailcow communityDiscussion

  SMTP SNI problems

  F Feja111

  I had 0Byte free disk space. Than i had executed: “docker image prune” It had given me 57Gigs of storage back. 🙂 But now, i can recieve mails and send mails via the SOGo panel but not sending mails via smtp: warning: TLS library problem: error:1422E0EA:SSL routines:final_server_name:callback

  

  16 2 Aug 5, 2023
  , also tried to create files sni.map.db and sni.map,
• added ADDITIONAL_SAN and played with recommendations mentioned here on github
  GitHub

  Postfix / Thunderbird SNI SSL domain ? · Issue #3690 · mailcow/mailcow-dockerized

  Prior to placing the issue, please check following: (fill out each checkbox with an X once done) I understand, that not following or deleting the below instructions, will result in immediate closin...

  

The mailcow.conf was like this:

SKIP_LETS_ENCRYPT=n
ENABLE_SSL_SNI=n
ADDITIONAL_SAN=

then I’ve tried to change it, assigning ENABLE_SSL_SNI=y, ADDITIONAL_SAN=mail.*,smtp.*,imap.*, SKIP_LETS_ENCRYPT=y in different combinations (yes, no, etc), but no luck.

Also updated the mailcow with update.sh script, stopped and restarted containers, even upgraded debian to bullseye from previous one, still not working.

Could someone please help me with it?