There are many changes needs to be done to revert. I would rather suggest to reset your mailserver. Try connecting to cloud.cyberpanel.net and use the Email debugger function there. If its not showing for you, you can create support ticket and request access for email debugger and the team will enable it for you.
@usmannasir Can you update this tutorial to include AlmaLinux centos command seem not working for sieve plugin install
Spamassassin is deleting the spam, it doesn’t arrive in the inbox. I wish it arrived, because it could be fake. And I wanted to use sieve to send them to the spam box.
I recently installed cyberpanel and sent that standard message to test spamassasin and it got deleted: XJSC4JDBQADN1.NSBN32IDNENGTUBE-STANDARD-ANTI-UBE-TEST-EMAILC.34X
How do I get this message to the inbox?
The “” journalctl -f | grep postfix “” shows the following:
“”" Feb 10 19:07:04 cloud postfix/smtpd[2252]: connect from sonic316-55.consmr.mail.gq1.yahoo.com[98.137.69.31]
Feb 10 19:07:05 cloud postfix/smtpd[2252]: 8797A1C146E: client=sonic316-55.consmr.mail.gq1.yahoo.com[98.137.69.31]
Feb 10 19:07:05 cloud postfix/smtpd[2252]: warning: connect to /var/log/policyServerSocket: No such file or directory
Feb 10 19:07:06 cloud postfix/smtpd[2252]: warning: connect to /var/log/policyServerSocket: No such file or directory
Feb 10 19:07:06 cloud postfix/smtpd[2252]: warning: problem talking to server /var/log/policyServerSocket: No such file or directory
Feb 10 19:07:06 cloud postfix/cleanup[2256]: 8797A1C146E: hold: header Received: from sonic316-55.consmr.mail.gq1.yahoo.com (sonic316-55.consmr.mail.gq1.yahoo.com [98.137.69.31])??by hostspot.tech (Postfix) with ESMTPS id 8797A1C146E??for [email protected]; Thu, 10 from sonic316-55.consmr.mail.gq1.yahoo.com[98.137.69.31]; from=[email protected] to=[email protected] proto=ESMTP helo=<sonic316-55.consmr.mail.gq1.yahoo.com>
Feb 10 19:07:06 cloud postfix/cleanup[2256]: 8797A1C146E: message-id=[email protected]
Feb 10 19:07:06 cloud postfix/smtpd[2252]: disconnect from sonic316-55.consmr.mail.gq1.yahoo.com[98.137.69.31] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 “”“”
Adjust the spam level settings under spamassasin to make the required level of security
1 Like
I increased the required_hits and required_score values. The default is 5. I put 10, then 20, 1000… and it didn’t work!
Have you gone through this article? This may help
Hi, what is required hits vs required score?
Mails remain working after implementing this article.
Filtering options are now showing up.
Problem is filter created in rainloop login of any particular email account but that filter rule gets applied globally to all Email accounts of all domains running on server.
This is a bug. Please suggest the fix.
Thank you.
1 Like
I just tried my method again, and now it’s not working on a clean install.
I also tried this method and the same result Any suggestions @die2mrw007
Got any advice on the issue i posted over? @usmannasir @die2mrw007
I run CyberPanel using Almalinux 8, and I’ve tried every dovecot.conf I can find.
Every dovecot.conf file fails except the default without a sieve.
I have also tried on 2.3.3-dev, same issue there.
I am clueless on what I can do to get it working.
Operating System: AlmaLinux 8.6 (Sky Tiger)
CPE OS Name: cpe:/o:almalinux:almalinux:8::baseos
Kernel: Linux 4.18.0-372.16.1.el8_6.x86_64
daemon started -- version 3.7.2, configuration /etc/postfix
dovecot --version: 2.3.19.1 (9b53102964)
You guys…
Do you even read the log? Anyway just tell us the WHOLE fatal error on line 80
NO CROPPING! SEND THE WHOLE FATAL ERROR on line 80.
I didn’t ask for the file, I ask what is the full error that dovecot gave, because that’s all that matters.
That is the full error.
There’s no cutoff that I could do.
What? I see it, right it’s in the log, dovecot is saying : Fatal: Error in configuration file blabla line 80 … length
What is the full error, we can’t just debug this on “…length”, you cropped that screenshot.
I took the time to send a screenshot of it, I don’t want the config, or that you think it’s right, just the full error message that dovecot printed out. It’s logged somewhere anyway, nothing else matters, dovecot will never start if it has a Fatal Error
I just ran this dovocot error log checker.
doveadm log find
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 80: Unknown setting: managesieve_max_line_length
good, progress.
So I don’t know, install dovecot-pigeonhole? Not sure where managesieve belongs to.
Tried this, and get an error.
Not sure why it’s in conflict.
Summary
## Install dovecot-pigeonhole on AlmaLinux 8 Using dnf
Update yum database with `dnf` using the following command.
sudo dnf makecache --refresh
Copy
After updating yum database, We can install `dovecot-pigeonhole` using `dnf` by running the following command:
sudo dnf -y install dovecot-pigeonhole
Copy
## Install dovecot-pigeonhole on AlmaLinux 8 Using yum
Update yum database with `yum` using the following command.
sudo yum makecache --refresh
Copy
After updating yum database, We can install `dovecot-pigeonhole` using `yum` by running the following command:
sudo yum -y install dovecot-pigeonhole
Did not run the uninstaller.
Copy
## How To Uninstall dovecot-pigeonhole on AlmaLinux 8
To uninstall only the `dovecot-pigeonhole` package we can use the following command:
sudo dnf remove dovecot-pigeonhole
that makes sense because dovecot comes with it and those sieve are version specific to dovecot
So remove that line? Does it continue complaining? I’d be surprised that almalinux dovecot is completely broken. what does journalctl -f | grep dovecot says? Any issue loading libraries?