> On 09/07/2020 01:29 la.jolie@paquerette wrote:
>
>
> Hello,
>
> Still trying to make roundcube / Dovecot works with Keycloak.
>
> Dovecot can't seem to validate the access_token that Roundcube gave.
Dovecot always does GET request when it does tokeninfo call. If you want to do
introspec
> On 08/07/2020 22:24 Justina Colmena ~biz wrote:
>
>
> On July 8, 2020 11:01:20 AM AKDT, Alexander Dalloz wrote:
> >Am 08.07.2020 um 20:28 schrieb Kishore Potnuru:
> >> Thank you for the reply.
> >>
> >> As per our current infrastructure, I can go maximum of the redhat 7.7
> >> version. No
Hello,
Still trying to make roundcube / Dovecot works with Keycloak.
Dovecot can't seem to validate the access_token that Roundcube gave.
-
Jul 08 20:48:05 auth: Debug: http-client[1]: request [Req1: GET
https://my.keycloak.host/auth/realms/test_saml/protocol/openid-connect/tokeneyJhbGciOiJFU
>> IBM is too big, too blue, and too politically correct. Something is a
little bit off.
I would pick IBM over Microsoft or Google any time. Totally fan of
OpenPOWER initiative and power8/9 cpu's. I hope your wrong and IBM -
RedHat is going to be a great combination.
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 RH
>>The other side of the question is, Why is the software always so
"vulnerable" and "broken" in the first >>place as to be unsuitable for
Long Term Support?
>>
>>If the software code worked when it was released some number of years
ago, then why doesn't it still work >>the same way today as i
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 redha
On 08.07.20 20:28, Kishore Potnuru wrote:
>
> I have another question. I understand redhat 6.10 will go out of
> support in november 2020. But this is a test environment. Am i able to
> install dovecot 2.3 version on redhat 6.10? For the Live support, I
> will be doing it on redhat 7.7 version.
>
>>> 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 hav
On 08 Jul 2020, at 13:39, Marc Roos 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?
--
'And I suppose you know what sound is made
> On 8. Jul 2020, at 21.28, Kishore Potnuru wrote:
>
> Thank you for the reply.
>
> As per our current infrastructure, I can go maximum of the redhat 7.7
> version. Not more than that. Am I able to install or upgrade to dovecot 2.3
> version in redhat 7.7?
>
> I have another question. I un
> with broken or vulnerable software is there really a benefit?
LTS distributions back port necessary patches
On 08 Jul 2020, at 12:28, Kishore Potnuru wrote:
> As per our current infrastructure, I can go maximum of the redhat 7.7 version.
If you have artificial constraints that limit your software to only what is
available for old Extended Support systems them when that old software is not
working, yo
On July 8, 2020 11:01:20 AM AKDT, Alexander Dalloz wrote:
>Am 08.07.2020 um 20:28 schrieb Kishore Potnuru:
>> Thank you for the reply.
>>
>> As per our current infrastructure, I can go maximum of the redhat 7.7
>> version. Not more than that. Am I able to install or upgrade to
>dovecot 2.3
>>
Am 08.07.2020 um 20:28 schrieb Kishore Potnuru:
Thank you for the reply.
As per our current infrastructure, I can go maximum of the redhat 7.7
version. Not more than that. Am I able to install or upgrade to dovecot 2.3
version in redhat 7.7?
Believe me, there is no technical reason why you can
Thank you for the reply.
As per our current infrastructure, I can go maximum of the redhat 7.7
version. Not more than that. Am I able to install or upgrade to dovecot 2.3
version in redhat 7.7?
I have another question. I understand redhat 6.10 will go out of support in
november 2020. But this is
Am 08.07.2020 um 11:53 schrieb Kishore Potnuru:
Hi All,
I request your help on this.
I have 2 dovecot test servers (IMAP protocol) installed with the following
configuration.
=
[root@devap01 ~]# cat /etc/redhat-*
Red Hat Enterprise Linux Server release 6.10 (Santiago)
[root@devap01
Hi All,
Can you please help me in understanding this:
1. At present my RHEL server is 6.10 version. Am I able to install dovecot
2.2 or 2.3 version?
2. Am i able to upgrade directly from 2.0 to 2.3? or I should go
periodically from 2.0 to 2.1, then 2.1 to 2.2, then 2.2 to 2.3?
3. could you pl
Thank you for your reply.
1. Am i able to upgrade directly from 2.0 to 2.3? or I should go
periodically from 2.0 to 2.1, then 2.1 to 2.2, then 2.2 to 2.3?
2. could you please suggest me steps to pick the correct package to upgrade
in the above version (2.1, 2.2, 2.3)?
3. which location i need
Hi All,
I request your help on this.
I have 2 dovecot test servers (IMAP protocol) installed 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 ~]# po
On Wed, Jul 08, 2020 at 12:05:55PM +1000, Mark Constable wrote:
> I spent a week trying every cypher combination I could find via Google
> for Dovecot but with the phone going off the hook from complaints by
> customers not being able to pick up their mail. We had to respond with
> some solution so
21 matches
Mail list logo
