Now the service appears to be running. Do you think the queued messages should start appearing now? Code: # apt install rspamd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libhyperscan5 The following NEW packages will be installed: libhyperscan5 rspamd 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 6832 kB of archives. After this operation, 31.1 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 https://rspamd.com/apt-stable jammy/main amd64 rspamd amd64 3.8.4-1~93fa4f6dc~jammy [4346 kB] Get:2 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 libhyperscan5 amd64 5.4.0-2 [2485 kB] Fetched 6832 kB in 1s (9874 kB/s) Preconfiguring packages ... Selecting previously unselected package libhyperscan5. (Reading database ... 148265 files and directories currently installed.) Preparing to unpack .../libhyperscan5_5.4.0-2_amd64.deb ... Unpacking libhyperscan5 (5.4.0-2) ... Selecting previously unselected package rspamd. Preparing to unpack .../rspamd_3.8.4-1~93fa4f6dc~jammy_amd64.deb ... Unpacking rspamd (3.8.4-1~93fa4f6dc~jammy) ... Setting up libhyperscan5 (5.4.0-2) ... Setting up rspamd (3.8.4-1~93fa4f6dc~jammy) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for libc-bin (2.35-0ubuntu3.8) ... Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. # service rspamd status ● rspamd.service - rapid spam filtering system Loaded: loaded (/lib/systemd/system/rspamd.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2024-06-29 21:49:17 CEST; 19s ago Docs: https://rspamd.com/doc/ Main PID: 44592 (rspamd) Tasks: 1 (limit: 4557) Memory: 68.5M CPU: 5.832s CGroup: /system.slice/rspamd.service └─44592 /usr/bin/rspamd -c /etc/rspamd/rspamd.conf -f Jun 29 21:49:17 myhostname systemd[1]: Started rapid spam filtering system. Jun 29 21:49:17 myhostname rspamd[44592]: 2024-06-29 21:49:17 #44592(main) <7179e5>; main; main: rspamd 3.8.4 is loading configuration, build id: release #
you can try to run: postqueue -f to flush the mailqueue, this makes postfix retry the delivery immediately. If it does not work, try to run: ispconfig_update.sh --force and let the ISPConfig updater reconfigure services.
That doesn't seem to have worked. The queue persists after flush, ISPConfig force-update, and another flush. Code: # postqueue -p -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- […] -- 2564 Kbytes in 45 Requests. # postqueue -f # ispconfig_update.sh --force -------------------------------------------------------------------------------- _____ ___________ _____ __ _ |_ _/ ___| ___ \ / __ \ / _(_) | | \ `--.| |_/ / | / \/ ___ _ __ | |_ _ __ _ | | `--. \ __/ | | / _ \| '_ \| _| |/ _` | _| |_/\__/ / | | \__/\ (_) | | | | | | | (_| | \___/\____/\_| \____/\___/|_| |_|_| |_|\__, | __/ | |___/ -------------------------------------------------------------------------------- >> Update Please choose the update method. For production systems select 'stable'. WARNING: The update from GIT is only for development systems and may break your current setup. Do not use the GIT version on servers that host any live websites! Note: On Multiserver systems, enable maintenance mode and update your master server first. Then update all slave servers, and disable maintenance mode when all servers are updated. Select update method (stable,nightly,git-develop) [stable]: Downloading ISPConfig update. Unpacking ISPConfig update. -------------------------------------------------------------------------------- _____ ___________ _____ __ _ ____ |_ _/ ___| ___ \ / __ \ / _(_) /__ \ | | \ `--.| |_/ / | / \/ ___ _ __ | |_ _ __ _ _/ / | | `--. \ __/ | | / _ \| '_ \| _| |/ _` | |_ | _| |_/\__/ / | | \__/\ (_) | | | | | | | (_| | ___\ \ \___/\____/\_| \____/\___/|_| |_|_| |_|\__, | \____/ __/ | |___/ -------------------------------------------------------------------------------- >> Update Operating System: Ubuntu 22.04.4 LTS (Jammy Jellyfish) This application will update ISPConfig 3 on your server. Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) [yes]: Creating backup of "/usr/local/ispconfig" directory... Creating backup of "/etc" directory... Creating backup of "/root/.acme.sh" directory... Checking MariaDB version 10.6.18 .. OK Checking ISPConfig database .. OK Starting incremental database update. Loading SQL patch file: /tmp/update_runner.sh.jELisGzqQ0/install/sql/incremental/upd_dev_collection.sql Reconfigure Permissions in master database? (yes,no) [no]: Service 'dns_server' has been detected (currently disabled) do you want to enable and configure it? (yes,no) [no]: Reconfigure Services? (yes,no,selected) [yes]: Configuring Postfix Configuring Dovecot Configuring Mailman Configuring Spamassassin Configuring Rspamd Configuring Getmail Configuring Pureftpd Configuring Apache Configuring vlogger Configuring Apps vhost Configuring Jailkit Configuring AppArmor Configuring Ubuntu Firewall Configuring Database Updating ISPConfig ISPConfig Port [8080]: Create new ISPConfig SSL certificate (yes,no) [no]: Reconfigure Crontab? (yes,no) [yes]: Updating Crontab Restarting services ... Update finished. # postqueue -f ## postqueue -p -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- […] (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) [6 more like that] (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) [39 more like that] -- 2564 Kbytes in 45 Requests. #
Login to ISPConfig, go to System > server server config mail, switch spamfilter to amavisd, press save, switch spamfilter back to rspamd and press save. Wait until changes are written to disk (red dot stops blinking in upper navigation bar). Then run: postsuper -r ALL to requeue all emails.
That worked, all queued messages have been received. I want sincerely to thank both you and Th0m for your extensive expert help with this problem. I would never have been able to resolve it alone (which troubles me since e-mail is so important) and you did this even though it's a weekend. Again, I can't thank you both enough.
If one idea comes to mind how better ISPConfig might have operated in this situation, some notification of apparent queue problems, or of the selected content filter not responding, would have been helpful to see on the Server State page or elsewhere. It continued to show everything as "ok" while the problem was ongoing.
Well there are a lot of services that work together here and it can come to all sorts of issues. You should always montior your servers with some external monitoring solution anysways and set alerts for such things. Switching to rspamd instead of amavis is a good advice here too. rspamd works with the milter protocol, so even if rspamd is acting up and does not response postifx will handle the mail after the timeout is reached. Amavis is not working with this milter protocol and thus this functionallity is not available for it. So in my option you should switch to rspamd as the milter protocol and rspamd are much more relaiable in my expirience and you should implemente some kind of monitoring sensors on your own to be alerted when something is not working propperly.
Thanks to all. I has the same issue and following the instructions I was able to solve it. Code: # apt install rspamd # ispconfig_update.sh --force Login to ISPConfig, go to System > server server config mail, switch spamfilter to amavisd, press save, switch spamfilter back to rspamd and press save. Wait until changes are written to disk (red dot stops blinking in upper navigation bar). Then run: # postsuper -r ALL Wait 1 minute.
