ISPConfig 3 issueshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues2024-03-28T23:05:40Zhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5851updater not ask for master root password unless needed2024-03-28T23:05:40ZJesse Norellupdater not ask for master root password unless neededWhen updating a slave server, the updater always prompts for the master's mysql root credentials, even when not needed.
We should first query the master using dbmaster connection info for the current server.dbversion - if there is an sq...When updating a slave server, the updater always prompts for the master's mysql root credentials, even when not needed.
We should first query the master using dbmaster connection info for the current server.dbversion - if there is an sql update available, the credentials will be needed. If there is not an sql update, the credentials should only be asked for if answering yes to `Reconfigure Permissions in master database?`.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6672Update fails on passwordless mysql root user connection test2024-03-28T23:05:37ZHelmoUpdate fails on passwordless mysql root user connection testWhen updating a Debian 12 system where the mysql root user does not have a password it fails.
```
>> Update
Operating System: Debian 12.0 (Bookworm) or compatible
This application will update ISPConfig 3 on your server.
Shall the scr...When updating a Debian 12 system where the mysql root user does not have a password it fails.
```
>> Update
Operating System: Debian 12.0 (Bookworm) or compatible
This application will update ISPConfig 3 on your server.
Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) [yes]: no
Checking MariaDB version 10.11.6 .. OK
Checking ISPConfig database .. Enter password:
mysqlcheck: Got error: 1698: Access denied for user 'root'@'localhost' when trying to connect
OK
ERROR 1698 (28000): Access denied for user 'root'@'localhost'
Unable to call mysql command line with credentials from mysql_clientdb.conf
```
This happens on [update.php line 326](https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/047dddb9b88e02e9027e0fadecdefb3d00305864/install/update.php#L326) where a port number is used for mysql cli while not needed in this case.
[A few lines earlier](https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/047dddb9b88e02e9027e0fadecdefb3d00305864/install/update.php#L258) we have a `mysqli_connect` test that does not specify a port number, thus letting php use the socket by default when connecting to localhost.
Maybe the answer is that only a root account with password is supported as [the perfect server setup suggests to use](https://www.howtoforge.com/perfect-server-debian-12-buster-apache-bind-dovecot-ispconfig-3-2/).
But I prefer the passwordless way, which has now been the Debian default for some years.
Commenting the whole section that does the mysql cli test solves it for now. But it might be nice to only specify the port number when required.
And since no port number is included in the `mysqli_connect` test it might be OK to also drop it here.
The same port number change would probably be useful in more places, atleast in [checkDbHealth](https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/047dddb9b88e02e9027e0fadecdefb3d00305864/install/lib/update.lib.php#L106).
The port code was added in #4932, and relates a bit to #5851https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6604Enhance ssh keys textarea with Javascript2024-03-27T14:27:09ZHelmoEnhance ssh keys textarea with JavascriptWith multiple (or long) ssh public keys the textarea to enter them for SSH/SFTP account is not ideal.
What about a Javascript enhancement?
![image.png](/uploads/3810a8d251c01cfa6d740a19686f3d59/image.png)
![image.png](/uploads/e0571a5...With multiple (or long) ssh public keys the textarea to enter them for SSH/SFTP account is not ideal.
What about a Javascript enhancement?
![image.png](/uploads/3810a8d251c01cfa6d740a19686f3d59/image.png)
![image.png](/uploads/e0571a587a15e081bad5852b39130c83/image.png)
Patches to improve e.g. the styling are very welcome ;)https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6617Show DKIM status when editing mail_domain2024-03-26T09:51:12ZHelmoShow DKIM status when editing mail_domainSimilar to #6539 I would like to show the user what the DKIM dns status is. E.g. if the dns record is resolving OK.
This should also help to detect copy/paste errors when using external DNS.
The OK state:
![image](/uploads/4554cceb7f7f...Similar to #6539 I would like to show the user what the DKIM dns status is. E.g. if the dns record is resolving OK.
This should also help to detect copy/paste errors when using external DNS.
The OK state:
![image](/uploads/4554cceb7f7f5c02aa2da8360fc9db0f/image.png)
For a not added to DNS state:
![image](/uploads/adebce3ce00ab90f362f5109eb80a095/image.png)
For a failure scenario:
![image](/uploads/442b3b21d636873ca3541c9ceae19c4e/image.png)
This icon might be a bit too subtle? Thoughts?HelmoHelmohttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6670DKIM for locally submitted mail - set content_filter = amavis:[127.0.0.1]:100262024-03-22T17:48:08ZMatus UhlarDKIM for locally submitted mail - set content_filter = amavis:[127.0.0.1]:10026With amavis, the default value of content_filter set by ISPConfig is:
content_filter = amavis:[127.0.0.1]:10024
Port 10024 is used for incoming mail, not outgoing, and DKIM signing is available on port 10026 in amavis config:
$interfa...With amavis, the default value of content_filter set by ISPConfig is:
content_filter = amavis:[127.0.0.1]:10024
Port 10024 is used for incoming mail, not outgoing, and DKIM signing is available on port 10026 in amavis config:
$interface_policy{'10026'} = 'ORIGINATING';
$policy_bank{'ORIGINATING'} = {
originating => 1,
};
This results in all mail submitted locally:
- cron jobs
- ISPConfig when "Use SMTP to send system mails" is unset
- other applications calling /usr/sbin/sendmail (standard way to submit mail)
is sent without DKIM signature.
Since ALL mail received via SMTP has content_filter overridden by FILTER directives called from smtpd_sender_restrictions:
smtpd_sender_restrictions = check_sender_access regexp:/etc/postfix/tag_as_originating.re, permit_mynetworks, check_sender_access proxy:mysql:/etc/postfix/mysql-virtual_sender.cf, permit_sasl_authenticated, reject_non_fqdn_sender, reject_unlisted_sender, check_sender_access regexp:/etc/postfix/tag_as_foreign.re
where the last rule sets:
/^/ FILTER lmtp:[127.0.0.1]:10024
I believe setting content_filter to port 10026 by default should be safe.
Please set default port for content_filter do 10026 instead.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6507SOAP API: client_update removes additional templates2024-03-19T21:57:17ZAlex von FiresplashSOAP API: client_update removes additional templates## Summary
In ISPConfig 3.2.9p1 (likely also in previous versions) a call to the client_update API causes the client to lose all it's assigned additional templates.
## Steps to reproduce
1. create aclient with a master template
2. assig...## Summary
In ISPConfig 3.2.9p1 (likely also in previous versions) a call to the client_update API causes the client to lose all it's assigned additional templates.
## Steps to reproduce
1. create aclient with a master template
2. assign one or more additional templates
3. call client_update on the client using the SOAP API
demo code causing the issue
```php
$context = stream_context_create(array(
'ssl' => array(
'verify_peer' => true,
'verify_peer_name' => true,
)
));
$ispc = new SoapClient(null, array('location' => ISPC_API_LOCATION,
'uri' => ISPC_API_URI,
'trace' => 1,
'exceptions' => 1,
'stream_context' => $context));
if($session_id = $ispc->login(ISPC_API_USER, ISPC_API_PWD)) {
echo 'Login successful. Session ID:'.$session_id.'<br />';
}
$client = $ispc->client_get_by_customer_no($session_id, '12345');
if ($client) {
$changes = array();
$changes['contact_name'] = 'NewName';
$result = $ispc->client_update($session_id, $client['client_id'], $client['parent_client_id'], $changes);
}
```
## Correct behaviour
The templates should be kept
## Environment
Server OS + version: Debian 11 \
ISPConfig version: 3.2.9p13.2.12HelmoHelmohttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6548Overview of which sites use a PHP version2024-03-18T20:23:38ZHelmoOverview of which sites use a PHP versionThe usage counter in server_php_list.php from server_php_list.php !991 helps to see how many sistes use the version but not which sites. And I did not find an easy way to look this up.
Adding an extra column to the sites list was my fir...The usage counter in server_php_list.php from server_php_list.php !991 helps to see how many sistes use the version but not which sites. And I did not find an easy way to look this up.
Adding an extra column to the sites list was my first though as that would allow filtering on php version. But I see two objections, first not all sites have the setting(either using mod php or no php at all), and second it would compete for space in an already filled table.
I suggest adding a simple list on the Additional PHP Versions edit form. Additional styling is very welcome ;)
![image](/uploads/7bb2df46c731a2cd1f6afb78f7ab3b62/image.png)HelmoHelmohttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5525Show assigned PHP in Websites list2024-03-18T20:23:35ZPascal HerbertShow assigned PHP in Websites listan optional column assigned PHP in the list of all websites would be useful.
so you could easy check if it is ok to remove eg. php 7.0an optional column assigned PHP in the list of all websites would be useful.
so you could easy check if it is ok to remove eg. php 7.0https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6541Mailman 32024-03-15T15:29:18ZTill BrehmMailman 3While we currently do not plan to implement Mailman 3 support in ISPConfig, I'll open this issue here as a place to gather information for possible future implementation.While we currently do not plan to implement Mailman 3 support in ISPConfig, I'll open this issue here as a place to gather information for possible future implementation.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6665security.txt2024-03-15T12:15:01ZSteffan Noordsecurity.txtRequest to adopt security.txt to the panel
idee is to I add a default security.txt to the .well-known folders of all domains, and clients can eddit it in the panel
https://www.rfc-editor.org/rfc/rfc9116Request to adopt security.txt to the panel
idee is to I add a default security.txt to the .well-known folders of all domains, and clients can eddit it in the panel
https://www.rfc-editor.org/rfc/rfc9116https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6501website PHP version select should also apply for CLI2024-03-14T07:11:07Zlaulauwebsite PHP version select should also apply for CLI## Summary
choosen PHP version is correcly applied for website, but not for CLI things (cron, SSH)
## Steps to reproduce
1. create a website
2. select a PHP version different from system default
3. login via SSH
4. php --version
## Cor...## Summary
choosen PHP version is correcly applied for website, but not for CLI things (cron, SSH)
## Steps to reproduce
1. create a website
2. select a PHP version different from system default
3. login via SSH
4. php --version
## Correct behaviour
should use same PHP version as the website we are using
## Environment
Server OS + version: 18.04
ISPConfig version: 3.2.7p1
## Proposed fix
set an alias, or a symlink for the shell users related to the website ?https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/5374Store last access information for mail users2024-03-13T17:14:18ZHelmoStore last access information for mail usersIn one legacy system I have a daily cronjob that gathers all imap/pop3/smtp logins and updates a last_access date in the user table.
I'm missing that in ISPconfig and would suggest adding something like that.
I've started hacking this t...In one legacy system I have a daily cronjob that gathers all imap/pop3/smtp logins and updates a last_access date in the user table.
I'm missing that in ISPconfig and would suggest adding something like that.
I've started hacking this together and with the patch below it's shown as a tooltip in the mail user listing.
I'm open to any suggestions on how to properly implement this here.
The cron script, run just before log rotation (e.g. as /etc/cron.daily/ispconfig_log_parser):
```bash
#!/bin/bash
# Parse the mailserver's logs to update the last_access date for all mail accounts.
NOW=`date +%Y-%m-%d`
#NOW=$1
# Filter imap/pop/smtp logins
# prefix cat with 'ssh <slaveserver>' when mail is on a slave server (use command="cat /var/log/mail.log" in the authorized_keys file to restrict access).
cat /var/log/mail.log \
| perl -n -e "if (\$_ =~ s/(.*) dovecot: (imap|pop3)-login: Login: user=\<([\w\.@-]+)\>.*/\$3/ or \$_ =~ s/(.*) sasl_method=PLAIN, sasl_username=([\w\.@-]+)/\$2/) { print \$_}" \
| sort \
| uniq \
| perl -n -e "\$_ =~ s/([\w\.@-]+)/UPDATE mail_user SET last_access='$NOW' WHERE email='\$1';/; print \$_" \
| tee /tmp/mail_stat_access.sql \
| mysql dbispconfig
```
Adding a column:
```sql
ALTER TABLE `mail_user` ADD `last_access` DATE NULL after `disabledoveadm`;
```
The code:
```diff
diff --git a/interface/web/mail/list/mail_user.list.php b/interface/web/mail/list/mail_user.list.php
index 4513a516c..7f4253c82 100755
--- a/interface/web/mail/list/mail_user.list.php
+++ b/interface/web/mail/list/mail_user.list.php
@@ -124,5 +124,13 @@ $liste["item"][] = array( 'field' => "disablepop3",
'suffix' => "",
'width' => "",
'value' => array('n' => $app->lng('yes_txt'), 'y' => $app->lng('no_txt')));
+$liste["item"][] = array( 'field' => "last_access",
+ 'datatype' => "DATE",
+ 'formtype' => "TEXT",
+ 'op' => "=",
+ 'prefix' => "",
+ 'suffix' => "",
+ 'width' => "",
+ 'value' => "");
?>
diff --git a/interface/web/mail/templates/mail_user_list.htm b/interface/web/mail/templates/mail_user_list.htm
index 4e2fedd50..d73850923 100755
--- a/interface/web/mail/templates/mail_user_list.htm
+++ b/interface/web/mail/templates/mail_user_list.htm
@@ -59,7 +59,7 @@
<tbody>
<tmpl_loop name="records">
<tr>
- <td><a href="#" data-load-content="mail/mail_user_edit.php?id={tmpl_var name='id'}" data-toggle="tooltip" data-placement="bottom" title="{tmpl_var name='email'}">{tmpl_var name="email"}</a></td>
+ <td><a href="#" data-load-content="mail/mail_user_edit.php?id={tmpl_var name='id'}" data-toggle="tooltip" data-placement="bottom" title="Last access: {tmpl_var name='last_access'}">{tmpl_var name="email"}</a></td>
<tmpl_if name="enable_custom_login">
<td>
<a href="#" data-load-content="mail/mail_user_edit.php?id={tmpl_var name='id'}">{tmpl_var name="login"}</a>
```https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6630Remove Pagespeed support2024-03-12T17:40:11ZMichaelRemove Pagespeed supportThe Pagespeed project (Apache module as well as Nginx) has not been maintained since at least 30. June 2022 and the Git repositories have been archived.
I therefore suggest removing Pagespeed.
Maybe it is possible to "substitute" Pa...The Pagespeed project (Apache module as well as Nginx) has not been maintained since at least 30. June 2022 and the Git repositories have been archived.
I therefore suggest removing Pagespeed.
Maybe it is possible to "substitute" Pagespeed with Google's Lighthouse some day in the future which provides a similar set of features, except that the website owner has to manually make the adjustments to his website.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6663Menu item title link shall use target of the first item2024-03-08T10:11:08ZTill BrehmMenu item title link shall use target of the first itemhttps://forum.howtoforge.com/threads/menu-head-name-linking.92005/#post-454637https://forum.howtoforge.com/threads/menu-head-name-linking.92005/#post-4546373.2.12https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6662Add amazontrust.com CA2024-03-07T09:30:48ZTill BrehmAdd amazontrust.com CAAdd the CA amazontrust.com for CAA records.Add the CA amazontrust.com for CAA records.3.2.12https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6659Probable bug on roundcube default Content-Security-Policy2024-03-04T13:28:06ZLucaProbable bug on roundcube default Content-Security-PolicyWe see that if we use the webmail from the default URL of the server:
https://nameoftheserver:8081/webmail
basically no image are opened from the webmail.
Because rise a policy error for "Content-Security-Policy", like:
```
Content-Se...We see that if we use the webmail from the default URL of the server:
https://nameoftheserver:8081/webmail
basically no image are opened from the webmail.
Because rise a policy error for "Content-Security-Policy", like:
```
Content-Security-Policy: Download a resource from https://external-url/9/9d08eac.png it was blocked by the page settings (“img-src”).
```
In my opinion the configuration here:
```
-- /etc/apache2/sites-available/apps.vhost
Row: 31
# ISPConfig 3.1 currently requires unsafe-line for both scripts and styles, as well as unsafe-eval
Header set Content-Security-Policy "default-src 'self' 'unsafe-inline' 'unsafe-eval'; img-src 'self' data:; object-src 'none'"
```
should be a little bit more relaxed like:
```
# ISPConfig 3.1 currently requires unsafe-line for both scripts and styles, as well as unsafe-eval
Header set Content-Security-Policy "'self' 'unsafe-inline' 'unsafe-eval'; object-src 'none'"
```
otherwise basically the webmail from the default url is useless for html mail. And this is a problem, because we are trying to keep our installation as standard as possible.
We known that we can use a different host to access webmail (like webmail.domain.com or something like that) but imho that should be fixed also on the main host above.
Tell me you thoughts about.
Thank's.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6603Warnings due to the use of PHP 8.2 in server.php logs2024-03-01T07:45:03ZMladen B.Warnings due to the use of PHP 8.2 in server.php logs<!-- Before creating a bug report, please:
- Read the contribution guidelines: https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/develop/CONTRIBUTING.md
- Do not ask support questions here. If you are unsure if your problem is a bug,...<!-- Before creating a bug report, please:
- Read the contribution guidelines: https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/develop/CONTRIBUTING.md
- Do not ask support questions here. If you are unsure if your problem is a bug, post a thread on the forum: https://www.howtoforge.com/community/#ispconfig-3.23
- Make sure to remove any content from the description that you did not add. For example, if there are no related log entries, remove the whole "Related log entries" part.
-->
## Summary
Hi,
I'm getting the following errors in `/var/log/ispconfig/cron.log`:
```
Sun Nov 12 10:20:01 AM CET 2023 PHP Warning: Undefined array key "db_flags" in /usr/local/ispconfig/server/lib/classes/db_mysql.inc.php on line 671
Sun Nov 12 10:20:03 AM CET 2023 PHP Warning: Undefined array key 1 in /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_mem_usage.inc.php on line 79
Sun Nov 12 10:20:03 AM CET 2023 PHP Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_mem_usage.inc.php on line 79
Sun Nov 12 10:21:01 AM CET 2023 finished server.php.
```
I've looked into `server/lib/classes/db_mysql.inc.php`, line 671:
```
$clientdb_flags = ($conf['db_flags'] !== NULL) ? $conf['db_flags'] : NULL;
```
which looks like the cause for the emitting of the 1st warning above, since I don't see 'db_flags' nowhere in any config file(s) defined, under `/usr/local/ispconfig`. It seems there should be an error control operator for suppressing errors/warnings (@) on that line, if we wanted to ignore the warning or the check should be written in a different way, to avoid having warning emitted in the first place (e.g. using `array_key_exists()` or so). I haven't created any PR for this since I'm not sure which way you guys want this to be solved (if at all).
The 2nd warning seems to have the same traits as the 1st one.
The 3rd warning is just an obsoletion warning, which could have slipped under your radar, I guess.
Btw, thanks again for creating this great software :) :beers:
Cheers.
## Steps to reproduce
1. Open the log at /var/log/ispconfig/cron.log
2. Inspect the log
## Correct behaviour
There should be no errors/warnings in the log.
## Environment
Server OS + version: **Debian GNU/Linux 12 (bookworm)** / ISPConfig version: **3.2.11p1**
Software version of the related software:
```
Apache/2.4.57
PHP 8.2.7
```
## Related log entries
```
Sun Nov 12 10:20:01 AM CET 2023 PHP Warning: Undefined array key "db_flags" in /usr/local/ispconfig/server/lib/classes/db_mysql.inc.php on line 671
Sun Nov 12 10:20:03 AM CET 2023 PHP Warning: Undefined array key 1 in /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_mem_usage.inc.php on line 79
Sun Nov 12 10:20:03 AM CET 2023 PHP Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /usr/local/ispconfig/server/lib/classes/cron.d/100-monitor_mem_usage.inc.php on line 79
Sun Nov 12 10:21:01 AM CET 2023 finished server.php.
```3.2.12https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6653Disable message function does not work2024-02-26T11:31:55ZHairyDisable message function does not work## Summary
ISPConfig ALMOST allows you to disable showing the message function, effectively disabling support messages.
Navigation to the setting:
System->Main config->Misc->Show message function in help module
After you disable showing...## Summary
ISPConfig ALMOST allows you to disable showing the message function, effectively disabling support messages.
Navigation to the setting:
System->Main config->Misc->Show message function in help module
After you disable showing the message function, ISPConfig still shows the message function to resellers and clients.
When the admin navigates to the Help tab,
In the right view the ISPConfig version is shown.
In the left navigation pane there is no longer an option for message functions.
When the reseller or client navigates to the Help tab,
In the right view the message function is still shown.
In the left navigation pane there is no longer an option for message functions.
## Proposed fix
I can fix this by showing the ISPConfig version in the default admin, reseller and client views by editing the files:
help/version.php
help/lib/module.conf.php
## Secondary issue
This brings us to a secondary issue.
A previous developer considered the ISPConfig version top secret information that should be kept secret from everyone except the admin.
If anyone can give a rational explanation why the version number should be kept top secret from everyone, please let me know so I can change my fix.
## Related log entries
issue-fix-message-function-disablinghttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6655Detect and add new IP addresses to ISPConfig2024-02-26T11:14:52ZHairyDetect and add new IP addresses to ISPConfig## Summary
On the very first and only the very first install of ISPConfig, the installer will detect and add the IP addresses of the server.
After installing ISPConfig, I have added additional IP addresses to the server.
After recently u...## Summary
On the very first and only the very first install of ISPConfig, the installer will detect and add the IP addresses of the server.
After installing ISPConfig, I have added additional IP addresses to the server.
After recently updating ISPConfig to the latest version, my new IP addresses were not added to ISPConfig.
ISPConfig should be able to scan for new IP addresses and add them to ISPConfig.
This single feature should be available from at least three places.
Additionally, I think you should be asked whether you want to scan for server IP addresses to add when installing and updating ISPConfig.
Currently, the installer forces you to add the new IP addresses whether you want to or not.
First, the feature should be fixed in the file /install/install.php, directly above the Restarting services section.
Second, the feature should be added to the file /install/update.php, directly above the Restarting services section.
Third, the feature should be added to the ISPConfig admin interface, under System->Server IP Addresses, with a new button labeled "Detect and Add New IPs."
## Proposed fix
I think I can fix this by changing or implementing the following code in the /install/install.php and /install/update.php files:
```
// Detect and add server IP addresses to ISPconfig
$detect_ips_answer = $inst->simple_query('Detect and add server IPs to ISPConfig?', array('yes', 'no'), 'no','detect_ips');
if($detect_ips_answer == 'yes') {
swriteln('Detecting IP addresses');
$inst->detect_ips();
}
```
I think the field server_ip.ip_address should be changed to unique to prevent duplicate entries.
Perhaps in time, I can offer more information for the button in the admin interface.
Maybe someone else can push a commit for the button before I can get to it.
## Environment
ISPConfig 3.2.11p2
Debian 11
## Related log entries
issue-fix-detect-ips-on-install
issue-add-detect-ips-on-update
issue-add-detect-ips-sysadmin-buttonhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6654Rspamd R_DUMMY Symbol is missing on some systems2024-02-26T09:21:45ZTill BrehmRspamd R_DUMMY Symbol is missing on some systemshttps://forum.howtoforge.com/threads/rspamd-whitelist.84552/
https://forum.howtoforge.com/threads/spamfilter-blacklist-does-not-work.91946/https://forum.howtoforge.com/threads/rspamd-whitelist.84552/
https://forum.howtoforge.com/threads/spamfilter-blacklist-does-not-work.91946/3.2.12