Problem after upgrade to exim-4.94-1.el7 on CentOS 7 Topic is solved

[compiz]

Or simply run the
yum update

see what packages have updates and IF there is a newer version of exim.
And then run

yum update --exclude=exim

this will updated everything else except exim, when they finally fix just return to the plain old
yum update

[RodolfoSouza]

Thanks, I made the change, I will wait until tomorrow to see if it resolves.

I don't think so maybe its initiated from somewhere else.

To ensure that you stay on exim 4.93 as long as there will be no other solution I recommend to exclude exim from receiving updates.

Run the following:

vi /etc/yum.repos.d/epel.repo
Insert exclude=exim within the [epel] part right under gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7

This ensures that whenever yum update is executed it will exclude to update exim.

Important: Please do not forget to remove the exclude when this issue has been resolved. Otherwise it will threaten your system by not updating exim with future versions and security bugfixes.

[servtelecom]

Could you let me know, in this same forum post, when it is already fixed and you can update exim without any problems?
I have stopped the updates until exim cannot be updated and I would like to resume them as soon as possible
Thank's

[avargas]

Hello,

In my case it happened in a new Proxmox container - LXC, it was implemented from scratch this Saturday, June 20, 2020 and the same error happened, that is, it happens not only when updating the exim but also when creating new vestacp servers.

I fixed it as mentioned above in the post by user peters

wget https://ca1.dynanode.net/exim-4.93-3.el7.x86_64.rpm
rpm -Uvh --oldpackage exim-4.93-3.el7.x86_64.rpm

Are there any solutions currently that do not go back from exim package to the previous one?

Thank you.

[peters]

There is no change to choose a exim version as epel only provides exim 4.94 by now. Also new installations are affected as its installed from epel. I think it will take some weeks before we can expect a new hopefully patched version from epel. However as in exim 4.94 this is a security feature that the exim devs implemented there are chances that new exim versions won't work together with VestaCP.

As VestaCP seems to be a death project and forks are already available with MyVestaCP and HestiaCP we all may think about migrate to a different solution.

[edica]

I already tested Hestia. It's a shame that it still doesn't work on CentOS.

There is no change to choose a exim version as epel only provides exim 4.94 by now. Also new installations are affected as its installed from epel. I think it will take some weeks before we can expect a new hopefully patched version from epel. However as in exim 4.94 this is a security feature that the exim devs implemented there are chances that new exim versions won't work together with VestaCP.

As VestaCP seems to be a death project and forks are already available with MyVestaCP and HestiaCP we all may think about migrate to a different solution.

[peters]

You may join the discussion here: viewtopic.php?f=10&t=19905

In my personal opinion I totally agree with MyVestaCP initiator dpeca as its one of the major problems in Vesta that its a real pain to maintain Debian and Redhat based distribution support and so many bugs and features remain unsolved.

Instead of complaining, anyone is free to start a fork for a CentOS based CP but there seems no demand as there are alternatives like Hestia and MyVestaCP are in place, even if they run on Debian/Ubuntu.

[layanto]

Is it possible to create vestaCP backup from CentOS and restore on Ubuntu HestiaCP?

[layanto]

Is it possible to create vestaCP backup from CentOS and restore on Ubuntu HestiaCP or myVestaCP?

[ScIT]

Is it possible to create vestaCP backup from CentOS and restore on Ubuntu HestiaCP or myVestaCP?

Yes, you should be able to restore vesta backups (doesnt matter if centos/rhel or anything else) in Hestia. Just use the usual v-restore-user cli command, have a look in the docs: https://docs.hestiacp.com/admin_docs/us ... new-server

I already tested Hestia. It's a shame that it still doesn't work on CentOS.

We currently don't have enough man power to also support CentOS/RHEL, if you would like to help us out, we are open for any pull request and testings that would gain additional OS support. Infact that we do not have enough time to support all the systems doesnt mean that we don't want it :).