No DKIM on outbound on Ubuntu 24.04 with 3.2dev20251223 or 3.3.0p3 ?

I migrated then upgraded an ISPconfig instance onto a new server running Ubuntu 24.04 LTS and have ran into an issue.
Although I have DKIM setup, for outbound email there is DKIM signing occurring.

I see that people are having issues with Rspamd and have switched to Amavis on Ubuntu 24.04.
1) How is that done for ISPConfig?
Note: I found a tutorial for "Replacing Amavisd with Rspamd in ISPConfig 3.1" but not the other way around from Rspamd --> Amavisd ?
2) I checked the postfix config for a content filter and both the 3.2dev and 3.3.0p3 versions do not seem to get this?

root@mail:~/ispconfig3_install/install# postconf -n | grep content_filter <<== nothing there!?
root@mail:~/ispconfig3_install/install#​

I've tried regenerating the DKIM's and checking the domains records and they are showing the correct SPF/DKIM/DMARC records (as well as checked using nsloekup).
3) Is there a way to tell ISPConfig installer to keep the database, client data, email, sites, dns in-tact but re-configure all the services as if a new install? I've tried the options as below, without success

Reconfigure Permissions in master database? (yes,no) [no]: yes
Reconfigure Services? (yes,no,selected) [yes]: yes
Configuring Postfix
Configuring Dovecot
Configuring Spamassassin
Configuring Rspamd
Configuring Getmail
Configuring BIND
Configuring Pureftpd
Configuring nginx
Configuring Apps vhost
Configuring Jailkit
Configuring Ubuntu Firewall
Configuring Database
Updating ISPConfig​

... but Postfix's content filter config is still missing?

Got any ideas or know a tutorial to switch to amavisd?

Thank you,

 

Thanks for the advise. I do want to use rspamd. I did however take a snapshot of my VPS then successfully dropped back to amavisd with the help of installing the amavisd-milter first then changing the option in ISPConfig. So now my outbound email is correctly being tagged with the DKIM header and outbound is working (and not being blocked).

I will try switch back to rspamd and see what happens now (from the ISPConfig portal).

Can I make a suggestion too about the download file. I have downloaded my original version prior to the upgrade, the nightly version which when installed shows 3.2dev20251223 and the stable version which shows 3.3.0p3? I checked the file timestamps of some of the zips files like update.php and install.php and I'm really confused by the timestamps all looking the same and within the zip files themselves I cannot find a simple Version = 3.x.x in the text files like README.md. It would really help to have the version shown in a text file in the zip file for easy confirmation of what zip file will install what version.

As I'm on the nightly with a lower version number, I will then also try to update to the 3.3.0p3 to get back to a 'standard' version.

 

Yeah, I have moved to 3.3.0p3 and also the switch back to rspamd made a lot of changes but everything started working fine after that. I think maybe a step in my migration might have missed something up, but maybe these threads steps will help someone else.
I also regenerated all eMail DKIM via clicking on 'Email' --> [clicked on each domain] --> DomainKeys Identified Mail DKIM --> 'Generate DKIM Private Key' and the relevent rspamd 60-dkim.conf private key files were updated accordingly.

Thank you for the pointer re the dev version's proper use. Case closed.
Note: I highly recommend using this when troubleshooting outbound email related issues (such as Google blocking emails), you just send an email to [email protected] and it will reply with a clickable report and their tools can help with email issues such as checking SPF, DMARC and DKIM.
https://mxtoolbox.com/deliverability & https://mxtoolbox.com/googleyahoo.aspx#header (they have a Microsoft policy checker also)