[SOLVED] Email filtering broken after update from 3.2.2 to 3.2.4

Hello,
I upgraded ISPConfig 3.2.1 to 3.2.4 and since I'm having problems with Postfix.
Several months ago, I had already switched the mail filtering system from amavis to rspamd and everything was working fine.
Since the update installed with the following command

Code:

ispconfig_update.sh

the mails are no longer delivered and I find this kind of error in the logs

Code:

May 4 17:17:09 smtp postfix / lmtp [11554]: 445B312E00B9: to = <[email protected]>, relay = none, delay = 0.33, delays = 0.33 / 0/0/0, dsn = 4.4.1 , status = deferred (connect to 127.0.0.1 [127.0.0.1]: 10024: Connection refused)

indicating a connection refusal on port 10024
As a reminder, port 10024 was used by amavis, so I temporarily restarted amavis...

Code:

 service amavis start

This unstuck the situation, but this is not normal at all since the system is configured to use rspamd !!!

After various searches, I modified the postfix config file to disable anything that might have a link with port 10024 or 10026, used by amavis. So I commented out the "filter_content" line and changed the "smtpd_sender_restrictions" parameter to suppress references to tag_as_*.re files

Code:

#content_filter = lmtp:[127.0.0.1]:10024
#smtpd_sender_restrictions = check_sender_access proxy:mysql:/etc/postfix/mysql-virtual_sender.cf,  check_sender_access regexp:/etc/postfix/tag_as_originating.re, permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_sender, reject_unlisted_sender, check_sender_access regexp:/etc/postfix/tag_as_foreign.re
smtpd_sender_restrictions = check_sender_access proxy:mysql:/etc/postfix/mysql-virtual_sender.cf, permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_sender, reject_unlisted_sender

From then on, the mails arrive and go without worries, but a second problem occurs: Postfix no longer understands forwarding emails. In ISPConfig, I have a transfer from [email protected] to [email protected], when I send an email to [email protected], I receive a non-distribution notice telling me that the address has [email protected] does not exist !
Querying the map with the postmap command works, however:

Code:

postmap -q [email protected] proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf
[email protected]

If I go back on the only 2 previous modifications, namely "filter_content" and "smtpd_sender_restrictions", everything works again but going through amavis !
After a whole day of worrying about this thing which does not respect any apparent logic, I leave it to you to have better ideas !
Thank you in advance.
Olivier

 

I have checked my conf-custom templates during the update. When the installer asks if we want to rename the conf-custom templates, I compare them to those of the installer and I adapt them before continuing the procedure.
But I don't have any custom templates for postfix.
During the last update, as always, I let the procedure reconfigure the services.
Is there any risk to change server configuration to amavis and change back to rspamd on this production server ?

Yes it is, you can see it on the following screenshot

 

A small relaunch... Is there any risk to change server configuration to amavis and change back to rspamd on this production server ?

 

IIRC when you switch back to amavis from rspamd, you need to tun

Code:

postconf -X 'non_smtpd_milters'

 

Well I just ran the installer again and let it reconfigure the services after renaming my conf-custom files. Sending and receiving Postfix / Dovecot is working fine.
I obviously had to reconfigure some files to find my customizations (different SSL certificates for Postfix and Dovecot, a single Rspamd Web interface for all my servers, systematic DKIM signing and antispam filtering header fields still present in the emails). I still have to redo the conf-custom files so that everything will not lost on the next update!