Messages

1

Dovecot / Re: Mail server error after update to Dovecot 2.3.14-5

« on: March 16, 2021, 11:46:02 AM »

Me too. Seems to have a major update.
The conf system has been changed completely apart from other things I suppose.

The problem reported by a user cannot log in to roundcube and the following error:
Before the update:  Warning: autocreate plugin is deprecated, use mailbox { auto } setting instead
After update: Error: Plugin 'autocreate' not found from directory /usr/lib64/dovecot

As the base system has been updated I think the solution is to fix the config files.

UPDATE: It is working now again. The solution was to Rebuild the mail services completely.
1. Check the log in /var/log/dovecot.log for errors. This is where I got the info above.
2. Tried to rename the dovecot.conf.rpmnew and use it as a main config file. Did not work as the conf.d folder files were not properly set. Ended up with going back to the original file.
3. Complete email service rebuild. After this I got the files updated as well and everything seems to be working.

Please let me know if you have any questions.

2

DNS Manager / Record length is limited and causing problems

« on: June 03, 2018, 09:04:53 PM »

The TXT record to store a DKIM key is limited and cannot store the full record.
The record supposed to be:

v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1yduUhmHQsC65O1jG4q5N9hDLd7py0/rRqcffumlDOlX7XY70mFwDBbB5tUAPigjfjZSlMIKllKeC2wrZlNdm07UNI5+O1fP4kC6FTedEME/qFXtCwtlcvBFEOPimlDj5mRMKOtn4hFzxEoUG2fxE/KjHTAl7QQhr3euMMQVTlZu9dalY4O3/vSzSoa07Skx8ez07H+X6m+jpf9Dnh9YYNqpdLNDWxte9SnJ3ihW35DPKrAqwJ0wJHl9KCqW9sCD86xKxIY0136w6yGzZqO3d4CfL0zCcOJj4yoJFF4CoHgejGjaENtT84EJDpKoiiFcgt40Go3Z8JrAd0GzOWaiqQIDAQAB

But the stored record is only:
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1yduUhmHQsC65O1jG4q5N9hDLd7py0/rRqcffumlDOlX7XY70mFwDBbB5tUAPigjfjZSlMIKllKeC2wrZlNdm07UNI5+O1fP4kC6FTedEME/qFXtCwtlcvBFEOPimlDj5mRMKOtn4hFzxEoUG2fxE/KjHTAl7QQhr3euMMQVTlZu9dalY4O3/vSzSoa07Skx8

Seems to be a problem in the max allowed record size.

3

SSL / Re: FALSE ERROR: Apparently the DNS of your domain does not point to this server

« on: May 18, 2018, 05:24:17 PM »

+1

4

CentOS-WebPanel Bugs / Re: CPU 100% clamd

« on: March 04, 2018, 11:42:13 AM »

Hi,
I just share my experience and my possible solution on this problem:

CWPpro version: 0.9.8.528 on CentOS 7.4.1708 (Core)

Symptom:
Obviously the constant 100% CPU usage on clamd

Log in /var/log/messages
Mar  4 11:25:30 vps6 clamd: ERROR: LOCAL: Socket file /var/run/clamd.amavisd/clamd.sock is in use by another process.

But I also experienced database duplication as well. Deleting the one not in use or older did not solve the problem. Also I saw solutions removing the serviced scripts.

I found that there are two entries trying to start clamd and this must be somehow not right.

My solution is to clean up first and then activate the clamd/amavis in CentOS Web panel.
1. In CWP, mail Server Manager - Switch off the ClamAV/AMAVIS/Spamassassin and rebuild Mail server. This suppose to remove clamav. After this process you can still see the Clamd and Amavis entries on the Dashboard.
2. Check the installed packages with 'yum list installed' - amavisd-new and clamav still there. Remove them with 'yum remove'. I did remove only: amavisd-new, clamav, clamav-server, clamav-data.
3. Dashboard still shows ClamAV row. No sense. Remove /usr/lib/systemd/system/ clamd-scan.service clamd.service
4. Reloading Dashboard should not show clamd or amavis status etc.
5. Now in CWP switch ON ClamD/Amavis/Spamassassin support. This will install the related services and dependencies.

From now on the antivirus system works and clamd is back to normal. Tried in two servers.
The question is what stage the original clamav installed originally? Is it because an earlier CWP built?

I tried the SH script and did not help in my situation.
I hope it is a solution for some of you.