Messages

1

E-Mail / Amavis + SpamAssassin not tagging spam emails on server

« on: April 16, 2025, 05:23:49 PM »

Hello,

I'm facing an issue where Amavis is not tagging suspected SPAM messages correctly on one of my servers, even though everything appears to be configured identically to another server that is working fine.

I have two servers running: CWPpro version: 0.9.8.1201 on AlmaLinux 8.10 (Cerulean Leopard)

The configuration files are nearly identical across both:

main.cf and master.cf (Postfix)

amavisd.conf (Amavis)

local.cf (SpamAssassin)

Both servers are set with the correct hostname, local adjustments, and same SpamAssassin thresholds ($sa_tag_level_deflt = 0, $sa_tag2_level_deflt = 5, etc.).

On Server A (older one), everything works perfectly: Spam emails are tagged with:

*** SPAM ***
X-Virus-Scanned: amavis at xxxxx.com.br
X-Spam-Flag: YES
X-Spam-Score: 5.845
X-Spam-Level: *****
X-Spam-Status: Yes, score=5.845 tagged_above=2 required=5...
On Server B (newer one), no emails are tagged, and the X-Spam-* headers are completely missing, even though Amavis is correctly delivering mail and SpamAssassin appears to be running without error.

The only difference I notice is that Server B is constantly triggering LFD alerts like this:

lfd on server.xxxxx.com.br: Suspicious process running under user amavis

Code: [Select]

Time:    Wed Apr 16 12:07:34 2025 -0300
PID:     2075822 (Parent PID:1942762)
Account: amavis
Uptime:  128 seconds


Executable:

/usr/bin/perl


Command Line (often faked in exploits):

/usr/sbin/amavisd (ch1-avail)


Network connections by the process (if any):

tcp: 127.0.0.1:46506 -> 127.0.0.1:10025


Files open by the process (if any):

/dev/null
/dev/null
/dev/null

It seems Amavis is calling SpamAssassin and forwarding the message, but not tagging or modifying headers in any way. I also confirmed that log_level = 2 and SpamControl: init_child on SpamAssassin done appears in the logs.

If anyone has suggestions or insights into why the tagging is silently failing (even with identical config files and packages), I would really appreciate the help.

Thanks in advance!

2

CentOS 8 Problems / Delay in FTP file uploads

« on: February 02, 2024, 05:36:39 PM »

I'm experiencing an issue with delays in files uploaded via FTP. After sending files to the server via FTP, it takes about 10 to 30 seconds before I can refresh the browser and see the changes reflected in the file. This is quite frustrating when trying to test certain routines, as I have to wait for this "update," which slows down development. I don't believe it's a browser issue since I've tested it on Chrome and Edge. On my old server (Cpanel), I didn't have this problem. I'm using CWP 8 with the recommended high-performance configuration (NGINX + Varnish + Apache with PHP-FPM) running on AlmaLinux 8.9. Any solutions?

3

Installation / Re: CWP doesn't start after AutoSSL

« on: January 03, 2024, 02:27:15 PM »

Thank you very much. I reinstalled the server due to other errors that were occurring, and now everything is working correctly.

4

Installation / Re: CWP doesn't start after AutoSSL

« on: January 02, 2024, 08:38:16 PM »

/etc/pki/tls/certs/hostname.bundle  /etc/pki/tls/certs/hostname.csr
File hostname.bundle is empty


Almalinux 8.9 / CWP8

5

Installation / CWP doesn't start after AutoSSL

« on: December 30, 2023, 04:17:02 PM »

I installed CWP on my server without any issues. I was able to access it, adjusted the security settings, and when I applied AutoSSL to my domains and restarted the server, the CWP service no longer starts. Here are the error messages:

Code: [Select]

[root@server ~]# systemctl restart cwpsrv.service
Job for cwpsrv.service failed because the control process exited with error code.
See "systemctl status cwpsrv.service" and "journalctl -xe" for details.


Code: [Select]

[root@server ~]# systemctl status cwpsrv.service
● cwpsrv.service - CentOS Web Panel service (daemon)
   Loaded: loaded (/usr/lib/systemd/system/cwpsrv.service; enabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: exit-code) since Sat 2023-12-30 13:12:46 -03; 3s ago
  Process: 90930 ExecStartPre=/usr/local/cwpsrv/bin/cwpsrv -t (code=exited, status=1/FAILURE)


Code: [Select]

[root@server ~]# journalctl -xe
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- A unidade cwpsrv.service está sendo iniciada.
dez 30 13:15:29 server.phinfo.com.br cwpsrv[91184]: cwpsrv: [warn] he "ssl" directive is deprecated, use the "listen ... ssl" directive instead in /usr/local/cwpsrv/conf.d/api.conf:8
dez 30 13:15:29 server.phinfo.com.br cwpsrv[91184]: cwpsrv: [emerg] annot load certificate "/etc/pki/tls/certs/hostname.bundle": PEM_read_bio_X509_AUX() failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no>
dez 30 13:15:29 server.phinfo.com.br cwpsrv[91184]: cwpsrv:configuration file /usr/local/cwpsrv/conf/cwpsrv.conf test failed
dez 30 13:15:29 server.phinfo.com.br systemd[1]: cwpsrv.service: Control process exited, code=exited status=1
dez 30 13:15:29 server.phinfo.com.br systemd[1]: cwpsrv.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- The unit cwpsrv.service has entered the 'failed' state with result 'exit-code'.
dez 30 13:15:29 server.phinfo.com.br systemd[1]: Failed to start CentOS Web Panel service (daemon).
-- Subject: A unidade cwpsrv.service falhou
-- Defined-By: systemd
-- Support: https://access.redhat.com/support
--
-- A unidade cwpsrv.service falhou.
--
-- O resultado é failed.
dez 30 13:15:29 server.phinfo.com.br kernel: Firewall: *TCP_IN Blocked* IN=eno1 OUT= MAC=08:94:ef:4f:8d:7c:b4:8a:5f:50:68:50:08:00 SRC=80.82.70.133 DST=177.234.149.165 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=6970>