inactive autoresponder sends bounce WHM 132.0.14
Hello,
We are receiving seperate reports from clients that there contacts receive mail delivery errors. However the mails are correctly send and received and there is no mention in exim about any bounces.
According to the logs it has to do with autoresponder see error below:
-
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
pipe to |/usr/local/cpanel/bin/autorespond mail@domain.tld /home/domain.tld/.autorespond
generated by mail@domain.tld
local delivery failed
The following text was generated during the delivery attempt:
------ pipe to |/usr/local/cpanel/bin/autorespond mail@domain.tld /home/domain.tld/.autorespond
generated by mail@domain.tld------
/usr/local/cpanel/bin/autorespond: error while loading shared libraries: /usr/local/cpanel/3rdparty/perl/536/lib/x86_64-linux/auto/MIME/Base64/Base64.so: cannot open shared object file: No such file or directory
_
We have removed the autoresponders from the thus far affected clients and did a forced update. We are still waiting for confirmation of the clients that this mitigates it but due to the upcoming weekend we rather not wait on there answer before reporting this.
Curious if anyone else has had simular issues or if its an isolated case.
-
Hey there! I'm wondering if this is related to some other Perl drama we experienced recently. What happens if you run "/scripts/check_cpanel_pkgs" on the server - do you continue to see those errors from the autoresponder system?
0 -
Hi cPRex, We have run the command you suggested and we are now waiting on feedback of any client we know it happened to. However it being the weekend I have little hope they will respond before monday. I will update you as soon as we had any confirmations.
0 -
I have the same problem.
1 -
Same Problem here.
0 -
Update - we've had another user submit a ticket and confirm this is a problem with CageFS. If you're all running CloudLinux with CageFS enabled, it would be best to run the following command to rebuild CageFS on the server. So far, this has resolved the error for all other users that have reported the problem:
cagefsctl --reinit
0 -
Thanks for the update cPRex,
We have not heard any more clients after using /scripts/check_cpanel_pkgs
We will run the second command to be sure.0 -
Sounds like a plan to me!
0
Please sign in to leave a comment.
Comments
7 comments