Rspamd masked after update [SOLVED]

I moved your issue to a new thread as the thread you posted to was about manually configuring Postfix blacklists and not about Rspamd.

The ISPConfig updater cannot mask Rspamd, so this must have been reverted to a manual configuration you made on your system.

 

The primary issue I see with the solution is that the error message and the proposed solution do not align. Rspamd does not use port 10024; it's an Amavis port. And you can not have fixed Amavis by unmasking Rspamd. Essentially, the error indicates that a message in the queue was forwarded to Amavis, which was unreachable, and you resolved the issue by unmasking Rspamd. It's great that you were able to fix it like this, but most likely this will not be solution for others, as there must have been other things going on on that system which are either not covered in the error description or not covered in the solution.

What might be is this: The system was changed from Amavis to Rspamd? Maybe these messages had been sitting in the queue since then, and nobody noticed them. Now the requeing of the message started a new re-delivery, which happened through Rspamd as the Rspamd config is now in place in postfix instead of the amavis config.

 

No, Amavis is worse and we do not support it anymore for recent installations.

 

Then your system must be heavily modified to use different ports, as port 10024 is only used by Amavis on ISPConfig systems.

ISPConfig Server with Rspamd:

Code:

root@server1:~# netstat -ntap | grep rspamd
tcp        0      0 127.0.0.1:11334         0.0.0.0:*               LISTEN      195396/rspamd: main
tcp        0      0 127.0.0.1:11332         0.0.0.0:*               LISTEN      195396/rspamd: main
tcp        0      0 127.0.0.1:11333         0.0.0.0:*               LISTEN      195396/rspamd: main
tcp6       0      0 ::1:11333               :::*                    LISTEN      195396/rspamd: main
tcp6       0      0 ::1:11332               :::*                    LISTEN      195396/rspamd: main
tcp6       0      0 ::1:11334               :::*                    LISTEN      195396/rspamd: main

No service running on port 10024 on a ISPConfig Rspamd server:

Code:

root@server1:~# netstat -ntap | grep 10024
root@server1:~#

If you search for port 10024 in ISPConfig config file templates, you can find it here:

https://git.ispconfig.org/ispconfig...tpl/amavisd_user_config.master?ref_type=heads

In the amavisd config file template.

So not sure what you did with your system config, but its definitely non standard and uses non-standard ports for services.

 

If it works fine now and your sysadmin is happy with it, you should consider keeping it. Please note that standard solutions for problems discussed in this forum may no longer apply to your system if it uses a highly customized setup.