Hi,
Our organisation has dependencies. There is a separate team/department who creates the servers for us. When they build a new RHEL system, the system will come up with various in-house softwares/tools. Those tools are not compatible as of now with RHEL8. So, our organisation is going with redhat 7.7 only as of today which is supported for all in-house tools also.
This is my current situation:
I have 2 test servers which are loaded with the following configuration.
============= [root@devap01 ~]# cat /etc/redhat-* Red Hat Enterprise Linux Server release 6.10 (Santiago)
[root@devap01 ~]# dovecot --version 2.0.9
[root@devap01 ~]# postconf | grep mail_version mail_version = 2.6.6
So, I would like to install the max possible dovecot version on the above servers for the testing purpose. I would like to implement the HA/Resilience with those 2 servers. I have shared storage and individual storage in this environment. But I am seeing some issues with both of them ( I explained details in my first email thread). please see if you can help.
- If it is successful, I will get two RHEL 7.7 servers to implement the same in LIVE environment for HA/Resilience.
First I am going with compatibility issues to resolve in my environment. Once that is resolved, I will go with HA/Resilience implementation.
Please let me know if you need any more details.
Thanks & Regards, Kishore Potnuru
On Wed, Jul 8, 2020 at 8:57 PM Marc Roos <M.Roos@f1-outsourcing.eu> wrote:
with broken or vulnerable software is there really a benefit?
LTS distributions back port necessary patches
Then the OP should be able to update to a dovecot that doesn't have the issue, right?
I have no idea what his issue is, and why he is stuck even in specific releases. I have been running dovecot on el6 and el7 for years and years without issues.
Am 08.07.2020 um 22:16 schrieb Kishore Potnuru:
Our organisation has dependencies. There is a separate team/department who creates the servers for us. When they build a new RHEL system, the system will come up with various in-house softwares/tools. Those tools are not compatible as of now with RHEL8. So, our organisation is going with redhat 7.7 only as of today which is supported for all in-house tools also.
Sir,
I was not talking about RHEL 8 at all. I was saying to use 7.8 or whatever will be current when you will make use of RHEL 7.
If you and your organisation is using RHEL 7 Update 7 then you are already running without current bug fixes - given you have no EUS contract - and that is a big no no.
Alexander
participants (2)
-
Alexander Dalloz
-
Kishore Potnuru